Repository navigation
chore(devcontainer): devcontainer lock at devbase 2.1.1, kept moving by Dependabot - #423
Merged
Merged
Conversation
…keep it moving with Dependabot Move .devcontainer/devcontainer-lock.json from devbase 2.0.1 to 2.1.1. github-cli and node moved within their ranges in the same pass. Add a devcontainers entry to dependabot.yml so the lock moves with each devbase release. Refs RSRMID-3013
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.
Part of RSRMID-3013: every devbase frame commits
.devcontainer/devcontainer-lock.json, and Dependabot'sdevcontainersecosystem keeps it moving.devcontainersentry is added to.github/dependabot.ymlwhere it was missing. Without it nothing moves the lock, and the container silently stays on an old devbase.The lock was written with
pnpm dlx @devcontainers/cli upgrade --workspace-folder ., which needs no Docker. The workspace'sdevbase-policy-driftjob will fail on a missing, unmoved or stale lock once its own PR lands after this one.The commit releases nothing:
choreis a non-releasing type in this repository's release config.🤖 Generated with Claude Code