Repository navigation
ci: plugin-build-action v8, releases refresh the store - #20
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
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.
Bumps the release workflow from plugin-build-action
@v5to@v8and passes the org secretSTORE_DISPATCH_TOKENasstore_dispatch_token.Why: v8's
build.ymlhas a finalrefresh-storejob that, after the release is published, runsaggregate.ymlin fizzyedit/plugins, so a release is listed in the store within minutes instead of at the next 6-hourly refresh. No other input changes between v5 and v8 (checked via the compare and README changelog);ci.ymlalready pinscheck.yml@v7, which is unchanged.Releases are not tagged by this PR.
🤖 Generated with Claude Code