1.3 KiB
Vendored
1.3 KiB
Vendored
Making a Malli release
- Make sure
CHANGELOG.mdmentions all relevant unreleased changes - Recommended: update dependencies
clj -M:outdated --upgrade- Gotchas:
- The script tries to upgrade :clojure-11 alias as well. This should not be done, as it is used to test the compatibility with clojure 11
- If shadow-cljs is updgraded, remember to update package.json as well
- Make a PR out of this to get the CI to run all the tests!
- Pick a new version number. Remember: we use BreakVer
- Set the version number
- Add a title to
CHANGELOG.md - Change the
<version>and<tag>fields inpom.xml
- Add a title to
- Push to
master - Create a release via the GitHub UI
- Use the version number as the tag name, eg.
0.22.33 - Copypaste the changelog from
CHANGELOG.mdto the text field
- Use the version number as the tag name, eg.
- Once the release is published, the
releaseGitHub Action will build a release and deploy it to Clojars.- See progress here: https://github.com/metosin/malli/actions/workflows/release.yml
- Check that the release is listed on clojars: https://clojars.org/metosin/malli
- Navigate to the cljdoc of the new release to trigger cljdoc build: https://cljdoc.org/versions/metosin/malli