chore: pin Yarn registry to registry.yarnpkg.com#208
Merged
Conversation
Copilot
AI
changed the title
fix: resolve js-yaml and ajv vulnerabilities (Dependabot #73)
fix: pin js-yaml to 4.2.0 and ajv to 6.15.0 to resolve Dependabot #73
Jun 23, 2026
Copilot created this pull request from a session on behalf of
maximizeIT
June 23, 2026 07:22
View session
Copilot
AI
changed the title
fix: pin js-yaml to 4.2.0 and ajv to 6.15.0 to resolve Dependabot #73
Pin vulnerable transitive dependencies with Yarn resolutions
Jun 23, 2026
Co-authored-by: GitHub Copilot <copilot@noreply.github.com>
Copilot
AI
changed the title
Pin vulnerable transitive dependencies with Yarn resolutions
chore: pin Yarn registry to registry.yarnpkg.com
Jun 23, 2026
maximizeIT
approved these changes
Jun 23, 2026
marcelo-staffbase
approved these changes
Jun 23, 2026
This file contains hidden or 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
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.
yarn.lockwas generated in an environment where the npm registry defaulted toregistry.npmjs.org, producing inconsistent resolved URLs throughout the lockfile. Without a project-level.yarnrc, Yarn v1 inherits whatever registry the host environment has configured.Changes
.yarnrc— added withregistry "https://registry.yarnpkg.com"to enforce consistent registry resolution regardless of environmentyarn.lock— regenerated; all 553 resolved entries now point toregistry.yarnpkg.com