Update release candidate to 0.2.0-rc-2023-12-05 #63
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
|
AFAIK there are only doc changes since the 11-10 RC, so I wasn't going to make us rev nearly package in order to rev this one (since nearly all depend on it) - instead we will just grab the doc changes when we go to 0.2.0. Is that OK? |
|
Another option is that we could cut an RC but not update everywhere. I'm worried folks will be confused by mismatched rc's. For example I started to update my own wit-deps and at first blindly bumped everything to 12-05. It's not the most ergonomic guessing which ones have a newer rc, but since we're pretty sure this is our last rc set, I'm OK with waiting for the 0.2.0 rev. |
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.
No description provided.