chore: Update yarn.lock after Dependabot dependency bumps #63
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.
Dependabot updated package.json files for 7 security-related dependencies but left yarn.lock out of sync. The lockfile needed regeneration to reflect the changes.
Changes
yarn.lockusing Yarn 4.3.1 viayarn install --mode update-lockfile@backstage/plugin-scaffolder-backend: 2.2.1 → 3.0.1@backstage/backend-defaults: 0.12.1 → 0.13.1@backstage/plugin-scaffolder-backend-module-gitlab: 0.9.6 → 0.10.0The lockfile diff shows 85 additions and 113 deletions, reflecting resolution changes from the dependency updates.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.