Workspace versioning #644
Open
Workspace versioning #644
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
nobkd
force-pushed
the
workspace-versioning
branch
from
38f1a2b to
8affb54
Compare
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.
use workspace versioning (bun pm pack in a package creates an archive with the versions from the workspace
"nuemark": "workspace:^", -> "nuemark": "^0.7.0",because the workspace version of nuemark is on0.7.0), so no manual update is needed when releasing (you can also use~or*to use those version ranges)will prevent things like #638 to happen for future releases, without having to manually handle version ranges on new releases.
This of course will only work when you use
bun pm packto create the archive to upload / publish the new version withbun publish.Bumping versions is also possible with
bun pm version <increment>.additional changes: