chore(release): bump vscode-rivet/package.json to 0.4.3#201
Merged
Conversation
Missed in the v0.4.3 release bump (#200). Docs-check VersionConsistency invariant fails CI on the v0.4.3 tag because the VS Code extension package stayed at 0.4.2 while workspace moved to 0.4.3. Platform packages stay at 0.4.1 intentionally — release-npm.yml overwrites them at publish time via jq. Trace: skip
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
⚠️ Performance Alert ⚠️
Possible performance regression was detected for benchmark 'Rivet Criterion Benchmarks'.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold 1.20.
| Benchmark suite | Current: 1fdaa19 | Previous: f25e592 | Ratio |
|---|---|---|---|
store_insert/10000 |
14120664 ns/iter (± 718153) |
11035172 ns/iter (± 606594) |
1.28 |
This comment was automatically generated by workflow using github-action-benchmark.
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.
Summary
Missed in the v0.4.3 release bump (#200). Docs-check `VersionConsistency` invariant fails CI on the v0.4.3 tag because the VS Code extension package stayed at 0.4.2 while workspace moved to 0.4.3.
Platform packages stay at 0.4.1 intentionally — `release-npm.yml` overwrites them at publish time via jq.
Next step after merge
The v0.4.3 tag already points at the previous commit (which lacks this fix). Suggested recovery: after merge, move the v0.4.3 tag to the new main HEAD so the Release workflow re-runs against the fixed tree.
Test plan
Trace: skip
🤖 Generated with Claude Code