bb publishYou are a maintainer of this project.
Is invoked from the command line via:
bb publishIt validates:
local git
you are on master branch
do not have any uncommitted code
do not have any unpushed commits
changelog
Has an "Unreleased" section with content
Then locally:
bumps the version <release count> (our scheme is major.minor.<release count>)
Our version is stored in deps.edn under :aliases :neil :project :version
applies version to:
doc/01-user-guide.adoc
CHANGELOG.adoc
git commits: deps.edn doc/01-user-guide.adoc CHANGELOG.adoc
git tags with release tag v<version>
pushes commit
pushes tag
Then up on CI, the CI publish workflow is only triggered when it sees a release tag:
CI tests workflow is invoked
a release jar is published to clojars
a GitHub release is created
cljdoc is informed of the new release
you can run just the publish validations alone via bb pubcheck
|
Scripts:
bb.edn - tasks entry point
script/publish.clj - client side work
script/ci_publish.clj - ci side work
CI - We use GitHub Actions for this project
.github/workflows/tests.yml
.github/workflows/publish.yml
Clojars secrets are protected under the publish environment which is only referenced by publish.yml.
When publishing, you will see both the tests workflow triggered and the publish workflow triggered (which also invokes the tests workflow).
This extra running of the tests workflow is GitHub Actions responding to changes committed as part of the publishing work.
A bit annoying, but harmless.
Can you improve this documentation?Edit on GitHub
cljdoc builds & hosts documentation for Clojure/Script libraries
| Ctrl+k | Jump to recent docs |
| ← | Move to previous article |
| → | Move to next article |
| Ctrl+/ | Jump to the search field |