Skip to content

Commit eac4a50

Browse files
Merge pull request #7 from Iterable/update-release-to-only-trigger-on-tag
Update release to only run on tags.
2 parents 4264299 + 35d6917 commit eac4a50

File tree

2 files changed

+12
-8
lines changed

2 files changed

+12
-8
lines changed

.github/workflows/release.yml

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,9 @@
11
name: Release
22
on:
33
push:
4-
branches: [main]
5-
tags: ["*"]
4+
tags:
5+
- 'v[0-9]+.[0-9]+.[0-9]+'
6+
workflow_dispatch:
67
jobs:
78
publish:
89
runs-on: ubuntu-20.04

RELEASING.md

Lines changed: 9 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,12 @@
11
# Releasing
22

3-
Releases are handled by [`sbt-ci-release`](https://github.com/olafurpg/sbt-ci-release) and [Github Actions](../.github/workflows/release.yml). Random versions are automatically deployed when changes are merged to main. To create a new semvar'ed version, do the following:
3+
Releases are handled by [`sbt-ci-release`](https://github.com/olafurpg/sbt-ci-release) and [Github Actions](../.github/workflows/release.yml). To release a new version do the following:
44

5-
```bash
6-
git tag -a v0.1.0
7-
# add notes about what changed
8-
git push origin v0.1.0
9-
```
5+
1. Go [here](https://github.com/Iterable/sbt-codeartifact/releases/new)
6+
2. In the `Choose a tag` dropdown, create a new tag with the following format `v[0-9]+.[0-9]+.[0-9]`. For example `v0.0.1` is a valid release number but `0.0.1` and `0.1` are not.
7+
3. Make sure the `Target` branch is set correctly.
8+
4. Select the correct `Previous tag`.
9+
5. Click the `Generate release notes` button.
10+
6. Click the `Publish release` button.
11+
12+
Once this is done it will trigger a github action that will publish this version to maven central.

0 commit comments

Comments
 (0)