Bump master to 1.0 and mark as 'publish = false' #576
Closed
Conversation
This file contains 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
|
I'm a little bit hesitant to bump to 1.0 now. One of the reasons is we merged quite a few large PRs recently. I propose to increase the minor version now, and if it works well for a certain period of time, bump the version to 1.0. |
This seems to make sense, given that we can't really release 1.0 right away in any case. I'll file a PR for that. |
bors bot
added a commit
that referenced
this pull request
Oct 12, 2020
581: Prepare for the next release r=jeehoonkang a=taiki-e - crossbeam-channel 0.4.4 -> 0.5.0 - crossbeam-deque 0.7.3 -> 0.8.0 - crossbeam-epoch 0.8.2 -> 0.9.0 - crossbeam-queue 0.2.3 -> 0.3.0 - crossbeam-utils 0.7.2 -> 0.8.0 - crossbeam 0.7.3 -> 0.8.0 Replaces #576 Co-authored-by: Taiki Endo <[email protected]>
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.
The current master branch contains breaking changes, but in the past, we've accidentally published a crate from master several times (#537 (comment)), and I had to yank each time.
This patch prevents releases from being accidentally created from the master branch by marking all crates as 'publish = false'.
Also, this bumps the master branch's version number to 1.0 (that should be the next major version we release). (The actual 1.0 release is blocked on #503.)