ci: fix nightly OSP after wolfSSL v5.9.2 bump (rolling deb-tag fallback + resolve-ref retry)#418
Merged
Merged
Conversation
…ent; retry resolve-ref on rate limit
padelsbach
approved these changes
Jun 30, 2026
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
2 participants
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.
Nightly CI broke after wolfSSL released v5.9.2: version discovery started labeling the latest ref v5.9.2-stable, but build-wolfprovider.yml then tried to pull a per-version deb tag (:fips-v5.9.2-stable) that was never published to ghcr, so the pull 404'd and took down all 39 Wave 1 OSP suites. I added a pick_wolfssl_tag helper that falls back to the rolling :fips/:nonfips tag (which is that version) when no per-version snapshot exists, self-healing for every future bump, while still failing loudly rather than silently swapping versions on a transient registry error.