Marketplace 0.1.3 + deterministic dist guard#5
Merged
Conversation
- marketplace.json advertised 0.1.2 in both metadata.version and plugins[0].version, so existing installs saw no update available even though main ships plugin 0.1.3. Bumped both. - dist-check: pin bun 1.3.3 and exclude content-hashed dist/connect web assets from the staleness diff — the guard failed every run since 2026-06-09 on a connect-bundle filename rename, which is alarm fatigue, not staleness. It now guards exactly the five runtime bundles.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Two release-path fixes found by post-deploy verification: marketplace.json still advertised 0.1.2 (existing installs would never see the 0.1.3 update), and the dist-check workflow was red on every run since Jun 9 due to bun-version drift renaming the content-hashed dist/connect assets. Bumped the manifest, pinned bun 1.3.3, excluded dist/connect from the staleness diff (runtime bundles still fully guarded).