docs: name the container image in AGENTS.md's releases - #208
Merged
Conversation
The Releases section's "release.yml then does everything" list ended at the crates.io publish and never named the ghcr.io image, so the contract read as exhaustive while omitting a shipped, publicly consumable artifact. Keeps the one non-obvious edge release.yml already encodes: `container` is a sibling of `publish`, not upstream of it, so a broken image build must not hold back the crates.io release of a tag whose binaries already shipped. Tag semantics and the manifest mechanics stay in the workflow. Closes #172
plusky
added
the
ai-assisted
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
1 participant
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.
Closes #172.
AGENTS.md said
release.yml"does everything:" and listed everything except thecontainer build.
grep -i 'ghcr\|container\|image' AGENTS.mdreturned nothing —the contract file agents are told to follow did not mention a shipped, publicly
consumable artifact.
Five lines naming
ghcr.io/plusky/bugwardenand the one non-obvious fact thejob graph encodes:
containeris a sibling ofpublish, not upstream ofit, so a broken image build must not hold back the crates.io release of a tag
whose binaries already shipped.
Verified against
release.yml, not the issue text — image name, the amd64/arm64matrix, and the
needs:graph (containerneeds[release, toolchain-drift],publishneeds[release]; neither depends on the other).Scope deliberately narrow per the issue's 2026-08-30 amendment: no tag
semantics, no manifest mechanics, no container section.
The pre-existing "and finally the crates.io publish" is left alone. It stays
true of the leg it enumerates, and the new bullet's "The same tag also
ships…" cures the exhaustiveness misreading that was the actual complaint.
Review: MERGE-SAFE, no findings.