Bump 13 plugin SHA pins to upstream HEAD; pin figma and adobe-for-creativity#237
Merged
Conversation
…ativity figma and adobe-for-creativity had no source.sha at all -- they fetched whatever upstream HEAD happened to be at install time. Add a pin to their current default-branch HEAD. The remaining 13 entries had pins that lagged upstream; update them to current HEAD.
charmaine
approved these changes
May 19, 2026
bryan-anthropic
approved these changes
May 19, 2026
Contributor
bryan-anthropic
left a comment
There was a problem hiding this comment.
Reviewed. 13 SHA bumps + 2 newly-pinned (figma, adobe-for-creativity). 13 of 14 SHAs already independently scanned via -official PRs this week (#1904/#1911/#1912/#1914). ai-firstify is unique to this marketplace — spot-checked the diff: SHA-only change against techwolf-ai/ai-first-toolkit at path plugins/ai-firstify, no source-shape change. Charmaine pre-approved. Approving and merging.
auto-merge was automatically disabled
May 19, 2026 13:21
Pull request was closed
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.
Freshness sweep of external plugin SHA pins. Two of the 26 external entries had no
source.shaat all — they were fetching whatever upstream HEAD happened to be at install time, with no pin to roll back to. 13 more had pins that lagged upstream HEAD.Newly pinned (had no
source.sha):Bumped to upstream HEAD:
Each new SHA verified to be on the upstream default branch (compare API status
identical) and validated withclaude plugin validateagainst a checkout at the new SHA.Skipped:
mintlify(mintlify/mintlify-claude-plugin) — no.claude-plugin/plugin.jsonat any SHA, including the currently pinned one. The repo only ships.claude-plugin/marketplace.json. There's an open upstream PR to add the manifest.Note: this repo doesn't have the policy scan or plugin-validation CI checks that
claude-plugins-officialruns on each marketplace.json change. Most of these new SHAs (bigdata-com,miro,planetscale,sanity,zoominfo,zapier,cockroachdb,fastly-agent-toolkit,nimble,brightdata-plugin,postiz,figma,adobe-for-creativity,box) were independently scanned and cleared inclaude-plugins-officialPRs this week (#1904, #1911, #1912, #1914).ai-firstifyis unique to this marketplace and hasn't been through that scan — worth a closer look in review.