ci: derive VS Code extension version from release tag - #133
Conversation
|
Warning Rate limit exceeded
To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
This is just a workaround to not fail the publishing because we forgot to bump the package.json. Long-term a automated solution should be built |
75390ce to
b1f987c
Compare
The marketplace rejects re-publishing an existing version, so the release job was failing because package.json was pinned to 0.0.1. Rewrite the version from the git tag before packaging so each tagged release publishes a unique version.
b1f987c to
c7e872a
Compare
Summary
Publish to Marketplacestep becausepackage.jsonwas pinned to0.0.1, which already exists in the marketplace (failed run).v1.2.3→1.2.3) before packaging, so each tagged release publishes a unique version without needing a manualpackage.jsonbump per release.TODOcomment flagging that the committedpackage.jsonversion is intentionally stale; long-term we should keep it in sync (e.g. bump on the release PR) rather than derive it from the tag.Test plan
*.vsixis packaged with the tag version.Publish to Marketplacesucceeds for all sixvsce_targetmatrix entries.workflow_dispatchruns (no tag) still package successfully using the in-tree version.