Repository navigation
fix: semver release - #235
Merged
Merged
Conversation
CodeByKarthik
approved these changes
Oct 7, 2026
|
🎉 This PR is included in version 1.2.4 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.
PR Description
Azure can't pull the amd64 image from the release because the labelling doesn't work with my "clever" workaround.
What's the remedy to a "clever" workaround?
Another workaround!
This time, what I've tried to do is add a step that runs the build for both architectures, writing to a cache for each architecture, then if that succeeds, running the release and triggering the publish-container workflow.
This now has a cache to pull from for each, so it can do that and hopefully add not too much time, while the download of the dependency that sometimes fails doesn't happen there.
Then the semver release is triggered for the published container.
I'm hoping the caching sorts the rate limiting issue I've encountered before. I had hoped to add multi-arch build to the
check-container-buildsworkflow, but docker build with only load if you have a single platform, which the part testing that it runs relies upon.✅ Added/updated tests?