Fix 1560/1561 release #410
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
This is a fixup release after accidentally tagging the PR merge as the release instead of the 4.3.1560 commit as the release.
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.
Accidentally tagged the PR merge instead of the head of the branch for releasing v4.3.1560. As a result, while everything was labeled v4.3.1560, the machinery calculated the build number including the PR merge and thus created a jar for v4.3.1561.
I deleted the v4.3.1560 release tag and release info as it had no corresponding jar, but I can't remove it from Clojars, so in the effort to ensure that semver will use incrementing numbers, I'm re-releasing with just a minor documentation fix and ensuring the release versions match the jar version on Clojars.