Repository navigation
Repair the tagged WordPress archive workflow - #7
Merged
Merged
Conversation
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.
Tagged Migration archive workflows failed at startup because the caller omitted permissions required by the pinned reusable workflow's optional attestation job. Match the existing Nginx Cache and Mailer Pro callers, keep attestations disabled, and exclude development tooling from the WordPress package.
The SQL and migration API are unchanged from v1.0.4. Prepared as v1.0.5 so the published signed v1.0.4 tag remains intact. Validation: GitHub actionlint and package/database CI; final tag archive and package inspection follow the merge.