Release 3.0.0 #419
Closed
Release 3.0.0 #419
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
13 tasks
|
I'd like to include #420 in this release, but that means we need to invalidate the hashes here. |
|
Could you hold off a little bit? I've got another PR in the works that uses the hash of watched files as cache key. Should be with you later today. |
|
We can also release 2.5.1 to drop the warning and than we got no hurry to release 3.0. |
|
This would be 2.5.1: #421 |
|
That's just fine with me. |
|
This is obsolete now. |
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.
We just released 2.5.0 yesterday, but it strikes me that removing API surface is actually a major version bump. I'm opening a PR to handle the release to discuss a major release (wouldn't have bothered for a minor or point release)
Yes, we have back compat but we should still bump the major and keep the back compat until next major release.
Note that I didn't use the existing scripts, so a tag will need to be created after merge (or some other inclusion).
The sha256 for fetchurl should be correct, however.