release: track the compiler version in every editor artifact - #32
Merged
Conversation
The v0.3.0 GitHub release carried `pyfun-0.2.0.vsix`, because the release job names the vsix from `editors/vscode/package.json` and the extension was only bumped "when it changed". That reads as a mistake even when it is not: a user whose extension says 0.2.0 while `pyfun --version` says 0.3.0 cannot tell whether that is fine or a broken install. So the versions now track the compiler unconditionally. Bumps the VS Code extension and the JetBrains plugin to 0.3.0, adds the CHANGELOG entries (0.2.0 was never recorded either), and rewrites RELEASING.md around "every versioned artifact tracks Cargo.toml" instead of per-artifact "only when it changed" tiers. Publishing stays gated on a registry having accepted the initial submission; bumping the in-repo number never is, so it stays true to the release even when a marketplace is not ready for it.
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.
The v0.3.0 GitHub release carried
pyfun-0.2.0.vsix— the release job names the vsix fromeditors/vscode/package.json, and the extension was only bumped "when it changed". That reads as a mistake even when it is not: a user whose extension says 0.2.0 whilepyfun --versionsays 0.3.0 has no way to tell whether that is fine or a broken install. Version numbers are cheap; that doubt is not.So every versioned artifact now tracks
Cargo.tomlunconditionally.editors/vscode/package.json→ 0.3.0, with CHANGELOG entries for 0.3.0 and 0.2.0 (that one was never recorded).editors/jetbrains/build.gradle.kts→ 0.3.0.RELEASING.mdrewritten: one "Every release" list that bumps all four files together, instead of per-artifact "only when it changed" tiers. It also records that the attached vsix is named frompackage.jsonrather than the tag, which is what made the drift invisible.Publishing stays gated on a registry having accepted the initial submission — bumping the number in the repo is never gated, so it stays true to the release even when a marketplace is not ready for it. The gate note now covers the JetBrains publish explicitly, since that plugin''s first submission is still in moderation per the ROADMAP ledger.
No compiler changes;
editors/vscode/client code is untouched.