Repository navigation
CI: reusable Publish workflow - #3
Merged
Merged
Conversation
A job rerun does not pick up secrets added after the original run, so the Firefox job for v2.0.1 skipped even after AMO credentials were set. Store publishing now lives in publish.yml: release.yml calls it after a tag build, and it can be dispatched for any existing tag and any subset of stores. The WIF provider condition now also admits workflow_dispatch runs on main. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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.
Store publishing moves to publish.yml (called by release.yml, or run by hand for any tag). Needed because job reruns don't see secrets added later.
🤖 Generated with Claude Code