Skip to content

Automate publishing of tagged releases to Clojars #37

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 22, 2024
Merged

Automate publishing of tagged releases to Clojars #37

merged 1 commit into from
Mar 22, 2024

Conversation

stig
Copy link
Contributor

@stig stig commented Mar 22, 2024

So that we don't need to find credentials and remember how to release changes manually. Git tags are used to trigger publishing so that we don't re-publish over existing versions every time we merge to master. It also means that we're more likely to remember to tag and don't need to add any logic or credentials for the workflow to create tags.

An alternative would have been to use the build number as a patch version, but it's unwieldy for both for users and for us to maintain the versions in README.md and CHANGELOG.md.

I cribbed liberally from circleci/bond#52 for this.


Once this is merged I intend to use it to address #18 and #16

@stig stig requested a review from a team as a code owner March 22, 2024 13:17
@stig stig changed the base branch from master to remove-useless-caching March 22, 2024 13:19
Base automatically changed from remove-useless-caching to master March 22, 2024 13:30
@stig stig changed the base branch from master to collapse-jobs March 22, 2024 13:40
@stig stig changed the title Add job to publish tagged releases to Clojars Automate publishing of tagged releases to Clojars Mar 22, 2024
Base automatically changed from collapse-jobs to master March 22, 2024 14:01
@stig stig force-pushed the deploy branch 4 times, most recently from c429574 to 985b3ae Compare March 22, 2024 14:38
So that we don't need to find credentials and remember how to release
changes manually. Git tags are used to trigger publishing so that we
don't re-publish over existing versions every time we merge to master.
It also means that we're more likely to remember to tag and don't need
to add any logic or credentials for the workflow to create tags.

An alternative would have been to use the build number as a patch
version, but it's unwieldy for both for users and for us to maintain the
versions in `README.md` and `CHANGELOG.md`.

The `CLOJARS_USERNAME` and `CLOJARS_TOKEN` environment variables come
from a context. The project already has "build forks" and "pass
secrets to fork builds" disabled, which will prevent leaking these
credentials.
@stig stig merged commit f176c48 into master Mar 22, 2024
@stig stig deleted the deploy branch March 22, 2024 15:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants