fix(ci): pin the docker reusable past the syntax fix - #85
Merged
Conversation
BryanFRD
enabled auto-merge (squash)
August 15, 2026 12:22
SonarQube — aucune nouvelle issueComparaison entre le projet bac à sable de cette PR et la branche par défaut : SonarQube Community n'analyse pas les PR, ce delta est calculé côté CI. Détail |
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.
The Dockerfile fix in #84 was only half the story: the shared build script itself did not parse, so
v0.24.1still failed withsyntax error: unexpected end of file. That is repaired in .github#257; this moves the pin onto it.Only
docker.ymlis repinned. The other reusables in this repo stay where they are — the same range carries a FerrFlow action bump that belongs to a deliberate decision about the release flow, not to unbreaking an image build.Once this lands, the release it cuts is the first version since 0.20.0 to actually produce a container.
0.21.0 through 0.24.0 stay imageless. Their tags contain the Dockerfile that trips hadolint on SC2155, so rebuilding them means rewriting released tags. They are superseded by the version this PR produces, and the chart's
appVersionshould simply never point at them.