Update development branch in sync with main branch #439
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
- add user links - host and link resources - wip translation of userguide
* docs: added introductory blogpost for AWS co-pilot * chore: renamed getting started blog
* changes to code snippet * final-changes-made
* Weekly Security Update - Updated Node LTS version - Updated accompanying NPM version - Updated node image in dockerfile - Updated readme to reflect changes * Update node version to reflect docker image version - Updated node version in plugin package.json - Updated node version api-server package.json - Updated node and npm to fixed versions in readme
This fixes the image breaking in production. While developing Uli locally, we use docker compose to mount our code directory into the image. Because of this we never realized that the docker image itself wasn't copying source code files. As a result when you look at the uli container in production cluster, it only has package.json in it.
We've tested the lexicon with the two partner organizations. The metadata fields may change in the future but not dramatically. For reference: - Annotation guideline (for meaning of each label): https://docs.google.com/document/d/18H4TlLFB2GXK054oMj1uXVJ2OCFW08Gi/edit - partner annotations here: https://docs.google.com/spreadsheets/d/15YrV8Q-5PTorHRo71ZBkdL0bePPaUNC9FTU41ET91V4/edit#gid=0 These are the fields that we need for now: | Field Name | Field Type | Possible Values | Optional?| | ------------- | ---------- |----------------- |------- | | Level of Severity | Single option | low, mid, high | No | | Casual | Binary | Yes, No | No | | Appropriated | Binary | Yes, No | No | | If, Appropriated is it by community or others? | Binary | Community, Others | yes | | What makes it problematic? | Text | | yes | | Category of Abuse | pick multiple | gendered, sexualized, religion, ethnicity , political affiliation, caste, class, body shaming, abelist, sexual identity, other | pick at least one, at most 4 | --------- Co-authored-by: Denny <[email protected]>
- Added setting up custom node version for build PR reviews
- Updated node version - Updated node docker image - Updated extension readme - Fixed npm critical severity vulnerability in plugin using audit fix - Updated testing script paths to default
* Weekly dependency update - Pinned new dependencies - Updated package versions with no breaking changes affecting us * - Updated package lock files * Add custom node version - Added setting up custom node version for build PR reviews * Weekly node and docker update - Updated node version - Updated node docker image - Updated extension readme - Fixed npm critical severity vulnerability in plugin using audit fix - Updated testing script paths to default - Resolved merge conflicts
- Verified breaking no breaking changes from commit logs - Updated eslint-config-prettier version in package.json - Updated package lock file
- Updated non-breaking plugin packages - Updated non-breaking api-server packages
|
| GitGuardian id | Secret | Commit | Filename | |
|---|---|---|---|---|
| - | Username Password | 59bd5a2 | browser-extension/docker-compose.yml | View secret |
| - | Username Password | 86063e3 | browser-extension/api-server/db/config/config.js | View secret |
| - | Username Password | 0c34ff1 | browser-extension/api-server/db/config/config.js | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secrets safely. Learn here the best practices.
- Revoke and rotate these secrets.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
Our GitHub checks need improvements? Share your feedbacks!
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.
developmentbranch up-to-date withmainbranch to create future PRs