chore: re-release the openai removal as 0.2.0 - #6
Merged
Merged
Conversation
0.1.0 was published and deleted by hand on Sep 23, before the automation existed; npm never allows reusing a deleted version number, so the burned 0.1.0 is skipped. Removes its never-published CHANGELOG section and re-attaches the same minor changeset, making 0.2.0 the next bump.
Merged
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.
Context:
0.1.0was published and deleted by hand on Sep 23, before the automation existed. npm never allows reusing a deleted version number, so the burned0.1.0is skipped and the same change re-attaches as a minor changeset — next automated bump is0.2.0.This PR:
## 0.1.0section fromCHANGELOG.md(describes a release that never went out)After merge: Version Packages PR (
0.1.0 → 0.2.0+src/version.tssync) → merge it → publish0.2.0with provenance → tagv0.2.0→ GitHub Release with the changelog section as body. (The release-run permissions fix is already proved working: the rerun's error was400on the burned number, not403OIDC.)