The runbook counts the images, instead of recording two of them - #100
Merged
Conversation
The images were a note about what one release happened to raise, not a step. There are five pins in three files and two are pinned twice, so a bump that changes one copy and not the other had nothing watching for it. postgres and the two .NET images were named nowhere at all.
RustFS and SeaweedFS were raised in three files and left at their old versions in the table that tells a reader which versions this is exercised against. The checklist item now says the table is a place to look.
The compose comment explained rc.4 above an image line saying rc.5, and two records read as standing claims about a pin that has moved.
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.
The image paragraph added with the 0.1.0 preparation said what that release happened to raise. It was a record, not a step: nothing told the next release to look, and it named two pins out of five.
This repository pins five images in three files, and two of them are pinned twice —
rustfsin both the development compose file and the test builder. A bump that changes one copy and not the other is exactly what a checklist item can catch and a paragraph cannot.postgres:18and the two .NET base images were named nowhere in that context at all. Both cases now say why they move the way they do: the PostgreSQL major is pinned deliberately because 18 moved the data directory, and the .NET images follow the target framework rather than moving on their own.Nothing else changes, and no pin moves here.