fix(toolkit): set version 0.2.1 and private:true to prevent premature publish - #67
Merged
Merged
Conversation
… publish The release workflow's Changesets action publishes any package whose local version hasn't been published on npm, even without a changeset. This caused @ocpp-debugkit/toolkit@0.2.0 to be auto-published when PR #55 merged with only Phase 0 consolidation code. Fix: set version to 0.2.1 (next available) and private:true to prevent any auto-publishing. private:true will be removed in the release issue (#66) when all v0.2.0 features are complete and we're ready to publish.
|
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
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
The release workflow's Changesets action auto-published
@ocpp-debugkit/toolkit@0.2.0when PR #55 merged, even though no changeset was present. This is because Changesets publishes any package whose local version hasn't been published on npm yet.The published 0.2.0 contains only Phase 0 consolidation code (stubs for replay/react, no actual v0.2.0 features). It has been deprecated on npm (manually by maintainer). The premature
release-v0.2.0GitHub release and tag have been deleted.Fix
versionto0.2.1(next available version after the deprecated 0.2.0)private: trueto prevent any auto-publishing until all v0.2.0 features are completeprivate: truewill be removed in the release issue (release: v0.2.0 — publish, tag, deprecate old packages #66) when ready to publishVerification