Repository navigation
Conversation
Releases are created with GITHUB_TOKEN, so publish-claude-plugin's release: published trigger has not fired since v0.53.1. Dispatch it from release.yml, which GitHub allows for GITHUB_TOKEN.
Current Homebrew refuses to load casks from an untrusted tap, and brew info does not trust one on the way like brew install does, so the cask check now fails on every run. Trust the scratch tap in a throwaway trust store so the developer's own one is left alone.
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.
Summary
Follow-up to #1176, part of #970.
publish-claude-pluginhas not run for a release since v0.53.1, so gortexhq/claude-plugin was last synced from v0.24.0 (2026-05-14). It still has the old flat layout, the marketplace install from #1176 can't work yet, and plugin fixes since then (#911, #981, #1173) haven't reached users.The cause: v0.53.1 was published by a person, but v0.54.0 through v0.64.11 were created by
release.ymlwithGITHUB_TOKEN(authorgithub-actions[bot]). Events fromGITHUB_TOKENdon't start other workflows, so therelease: publishedtrigger never fired.workflow_dispatchis the documented exception.Changes
release.yml: a newpublish-claude-pluginjob (afterrelease) runsgh workflow run publish-claude-plugin.yml -f ref=<tag>, with job-levelactions: writeonly.publish-claude-plugin.yml: a header comment explaining the dispatch. No logic change; thereleasetrigger stays for releases published withoutGITHUB_TOKEN.scripts/validate-cask.sh: touchingrelease.ymlruns thehomebrew-caskcheck, which now fails on any change because current Homebrew refuses to load a cask from an untrusted tap (brew infodoes not trust it the waybrew install user/tap/xdoes). The script now trusts its scratch tap in a throwaway trust store (XDG_CONFIG_HOMEpointed at a temp dir), so a developer's own trust settings are left alone. Users installing from the tap are not affected.A publish failure shows in the dispatched run, not in the Release run. If a release is ever published by hand, two runs can start; the concurrency group serializes them and the second finds no changes.
Two things only you can do:
publish-claude-pluginwithrefset tomain(or the next tag) would publish the marketplace layout now instead of at the next release.CLAUDE_PLUGIN_TOKENhas expired, the dispatched run will fail the same way.Testing
actionlinton both workflows: no findings in the changed lines.shellcheckandbash -nonvalidate-cask.sh; thehomebrew-caskjob on this PR runs it against real Homebrew.Checklist
Meta["methods"]for interfaces (n/a)EdgeMemberOfedges to their containing type (n/a)