-
-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Development #494
Closed
Closed
Development #494
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Updated node version in github actions - Updated node and npm version in readme - Updated node docker image - Pinned node and npm version in plugin and api-server package.json - Updated node and npm version in plugin and api-server package.json
- Removed lmdb package from plugin - Updated package lock files
- Removed busboy package from api-server as it is not required - Auto-added and pinned 'process' package in plugin
- Changed ownership from root to node for recursive copy command
- Updated dom-to-image-more package version - Updated package lock file
- Updated i18next package in plugin - Update package lock file
- Updated react-i18next plugin package - Updated package lock file
- Updated parcel version - Updated puppeteer version
- Updated node version - Updated node docker image
- Updated styled-components to latest version supported by grommet
- Updated react with breaking changes - Updated react-dom with breaking changes
* Update axios - Updated axios version - Pinned auto-added buffer package required by parcel * - Rebuilt package lock file * Add Api axios tests - Added Api tests other than slur crowdsource
* Update axios - Updated axios version - Pinned auto-added buffer package required by parcel * - Recreated package lock file * Update non-breaking package versions - Updated plugin packages - Updated api-server packages
* Update axios - Updated axios version - Pinned auto-added buffer package required by parcel * - Recreated package lock file * - Updated axios api-server
* Update axios - Updated axios version - Pinned auto-added buffer package required by parcel * - Recreated package lock file * Updated uuid package version
* Update axios - Updated axios version - Pinned auto-added buffer package required by parcel * - Recreated package lock file * - Pinned uli-website packages * - Fixed URL issues in blog file * - Regenerated package lock file
* Update axios - Updated axios version - Pinned auto-added buffer package required by parcel * - Recreated package lock file * - Updated packages with non-breaking changes
- Updated packages in uli-website - Updated packages in uli plugin - Updated packages in uli api-server
- Updated react package - Updated react-dom package - Updated react-i18next package
…wdsourcing progress
* Update axios - Updated axios version - Pinned auto-added buffer package required by parcel # Conflicts: # browser-extension/plugin/package-lock.json # browser-extension/plugin/package.json * - Recreated package lock file # Conflicts: # browser-extension/plugin/package-lock.json * Update aws-sdk and multer-s3 - Updated AWS SDK for JS packages - Updated multer-s3 package - Migrated AWS code to use current package version * Update AWS SDK modules - Updated aws-sdk client-s3 - Updated aws-sdk client-sesv2
* refactor(plugin): add file to consolidate chrome/firefox APIs At 2-3 places in the codebase, we're checking if the browser is chrome or firefox, and hen using the corresponding APIs chrome.* or browser.* respectively. To reduce code repetition this adds a file browser-compat.js that exposes objects corresponding to various browser APIs such that they can be used by other functions in a browser agnostic way. --------- Co-authored-by: Aatman Vaidya <[email protected]>
chore: removing ogbv-ml-rest container
* fix: github action for deploy staging * fix: github action deploy prod
* Update node to current LTS - Updated node version in github actions - Updated node and npm version in readme - Updated node docker image - Pinned node and npm version in plugin and api-server package.json - Updated node and npm version in plugin and api-server package.json * Update about.mdx * Update README.md (#469) * Update README.md * feat: add malayalam traanslation for about and home page --------- Co-authored-by: tarunima <[email protected]> Co-authored-by: Denny George <[email protected]> Co-authored-by: Ajay <[email protected]>
* fix: error on save in slur replacment * fix: error on save in slur replacment * chore: removing localhost from manifest * chore: removing localhost from manifest
* Update package versions - Updated all packages to latest versions - Added .npmrc to allow required legacy-peer-deps with gatsby and react-dom - Added gatsby-node.mjs to handle gatsby-plugin-mdx update issues - Updated index.jsx with gatsby-codemods and manual slug field entry Co-authored-by: Aatman Vaidya <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
name: Bug report
about: Create a report to help us improve
title: ''
labels: bug
assignees: ''
Describe the PR
Write A clear and concise description of what changes you have made. Add links for any relevant issues as well.
Steps to test the PR
Write step by step instructions on how we can test your changes. This could involve running a script or doing something manually. Being descriptive here will help us test your PR quickly
Expected behavior
A clear and concise description of what is the expected behaviour.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the PR here.