maint: prep for next release #23
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
Move to 1.1.<release count> version scheme. Move to using neil to track version within `deps.edn`. I don't necessarily think this is better than the old `version.edn`, but it is consistent with what I've done on my other projects. Tweak changelog - move to [breaking] [minor breaking] attributes on release header scheme I've used on other projects - automatically add yyyy-mm-dd date to release header - describe commits for release link as "commit log" Add GitHub release creation to release workflow. Stick with release initiated through GitHub UI on release workflow. I still feel this is much simpler than a version tag triggered 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.
Move to 1.1. version scheme.
Move to using neil to track version within
deps.edn. I don't necessarily think this is better than the oldversion.edn, but it is consistent with what I've done on my other projects.Tweak changelog
Add GitHub release creation to release workflow.
Stick with release initiated through GitHub UI on release workflow. I still feel this is much simpler than a version tag triggered release.