Prepare parse-zoneinfo v0.3.1 #181
Merged
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
djc
approved these changes
Apr 24, 2024
|
Thank you! |
|
'chronotope/Release Manager' is not a crates.io owner of parze-zoneinfo, only 'djzin'. @djc is that something you can change? |
|
I sent an email to @djzin to see if they could give us access (you are in the CC). If not, we might persuade the crates.io maintainers to give us ownership, or we can publish under a new name. |
|
Well-written mail 👍. |
|
Published 🎉. |
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.
De we want to do a new release of parse-zoneinfo?
It is mostly doc improvements, and the comment parsing fix that will allow us to remove a workaround from chrono-tz-build.
#176 is needed to package a
LICENSEfile, and #174 may be nice as well.