feat(publish): add option to skip publish of a package#83
Closed
ruiaraujo012 wants to merge 1 commit intoTanStack:mainfrom
Closed
feat(publish): add option to skip publish of a package#83ruiaraujo012 wants to merge 1 commit intoTanStack:mainfrom
ruiaraujo012 wants to merge 1 commit intoTanStack:mainfrom
Conversation
Member
|
Hi @ruiaraujo012 , could you please write a description for this PR? |
☁️ Nx Cloud ReportCI is running/has finished running commands for commit 1c057e0. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution ✅ Successfully ran 1 targetSent with 💌 from NxCloud. |
Author
|
@lachlancollins Yes sorry, I updated the description now. |
Author
|
Any plan on merging this PR? |
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
2 participants
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.
In some cases, let's imagine a private project, I want to use semver for the releases (updates) and this package does that perfectly, but I just do not want to publish it to npm.
With this new option, we can choose the packages to publish to npm or not, so we can release new versions with semver but not publish it on npm.
I was talking with @crutchcorn on discord about this feature.