Merged
Conversation
tylerjereddy
commented
Feb 5, 2026
tylerjereddy
commented
Feb 5, 2026
69f1d33 to
0cb9995
Compare
* Don't merge until the `0.1.0` release notes updates have been merged and the `maintenance/0.1.x` branch has been pushed up (I'll probably self-merge this when the time is right). * This will be slightly more complex than usual because it follows our first-ever release (i.e., the release notes infrastructure itself hasn't even been merged, so this will require merge conflict resolution when the time comes...).
0cb9995 to
203c17b
Compare
Collaborator
Author
|
The This officially opens us up for development of version |
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.
Don't merge until the
0.1.0release notes updates have been merged and themaintenance/0.1.xbranch has been pushed up (I'll probably self-merge this when the time is right).This will be slightly more complex than usual because it follows our first-ever release (i.e., the release notes infrastructure itself hasn't even been merged, so this will require merge conflict resolution when the time comes...).