Repository navigation
release: StellarForge CLI 0.1.0 - #87
Merged
Merged
Conversation
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
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.
StellarForge CLI 0.1.0
Prepares the first public CLI release.
Release contents
Versioning
@stellarforge/clifrom0.0.0to0.1.0CHANGELOG.mdPublication gate
Merging this PR does not automatically publish until the repository variable
NPM_PUBLISH_ENABLED=trueand the npm Trusted Publisher /npm-releaseenvironment are configured.Before publication, the one-time npm namespace bootstrap described in
docs/contributing/release-process.mdmust be completed by an authenticated npm maintainer.No long-lived npm publishing token is required or expected.