test: discover clojure versions via convention#448
Merged
Conversation
`deps.edn` clojure aliases are now named with prefixes: - `:clojure-` for regular production releases, ex `:clojure-1.8` - `:clojure-pre-` for a pre-release, ex `:clojure-pre-1.12.5-alpha1` Unit tests on CI cover all defined clojure versions. Native image tests cover only the last production release and pre-releases (if any). Closes #446
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
1 participant
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.
deps.ednclojure aliases are now named with prefixes::clojure-for regular production releases, ex:clojure-1.8:clojure-pre-for a pre-release, ex:clojure-pre-1.12.5-alpha1Unit tests on CI cover all defined clojure versions.
Native image tests cover only the last production release and
pre-releases (if any).
Closes #446
We appreciate your contribution, please confirm (and leave in as part of your PR):
I have:
read and have followed Contributing Guidelines.
created a clear issue and have gotten agreement to proceed from the project maintainers (unnecessary for typo fixes).
added/updated tests to cover my change.
described my change in the Changelog (if user-facing).