Repository navigation
docs(devcontainer): Dependabot keeps devcontainer-lock.json current; only a major tag move is manual - #29
Merged
Conversation
…only a major tag move is manual The README, CLAUDE.md and the dependabot.yml comment claimed nothing but a hand re-resolve moves a committed devcontainer-lock.json and that Dependabot never would. That is wrong: the devcontainers ecosystem re-resolves the lock within the tag the frame names (a lock-only 1.3.0 to 1.5.0 move against devbase:1 in the PHP SDK, and 2.0.0 to 2.0.1 against devbase:2 here). What it does not do is change the tag, so :1 to :2 stays a deliberate manual step. Rewrite "Keeping consumers up to date", drop the advice to pin a precise version, fix the mixed :1/:2 references, and correct the dependabot.yml comment, which also said this repository commits no lock when it commits two. The manual re-resolve recipe now uses pnpm dlx and pnpm prettier:fix instead of npx. Refs: RSRMID-2978
KaiSchwarz-cnic
force-pushed
the
RSRMID-2978-dependabot-moves-the-lock
branch
from
October 28, 2026 15:36
ec5746d to
4801278
Compare
KaiSchwarz-cnic
enabled auto-merge (rebase)
October 28, 2026 15:37
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.
Corrects the documentation claim RSRMID-2978 found to be false. Dependabot's
devcontainersecosystem does re-resolvedevcontainer-lock.jsonbehind a moving major tag. Evidence: php-sdk #320 (1.3.0 → 1.5.0 againstdevbase:1) and this repository's own #16 and #24, all lock-only. What it never does is change the tag itself (:1→:2).devcontainersentry gets its lock moved; without one, nothing moves it. The snippet now includes thegroupsblock, and the "pin a precise version" advice is dropped.pnpm dlx @devcontainers/cli, nevernpx. Deleting the entry is the step that matters.dependabot.ymlcomment are corrected to match. The comment wrongly said this repository commits no lock.:1→:2wherever the current coordinate or consumer pin is described. Historical 1.x statements are kept.The gh-credential half of the ticket is superseded by RSRMID-3096 (devbase 2.1.0) and already documented. Docs only; releases nothing.
🤖 Generated with Claude Code