Skip to content

Commit

Permalink
Add release automation and instructions (#12)
Browse files Browse the repository at this point in the history
  • Loading branch information
consideRatio authored Mar 15, 2024
1 parent 1941cf0 commit 9a729e9
Show file tree
Hide file tree
Showing 2 changed files with 34 additions and 0 deletions.
19 changes: 19 additions & 0 deletions .github/workflows/release_updates.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
# Automatically updates "vX" branches based on GitHub releases. To cut a new
# release, use the GitHub UI where you enter a tag name and release name of
# "vX.Y.Z". See https://github.com/jupyterhub/action-k3s-helm/releases.
name: Release updates

on:
release:
types: [published, edited]

jobs:
actions-tagger:
runs-on: windows-latest
permissions:
contents: write
steps:
# Action reference: https://github.com/Actions-R-Us/actions-tagger
- uses: Actions-R-Us/actions-tagger@v2
with:
token: "${{ github.token }}"
15 changes: 15 additions & 0 deletions RELEASE.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
# How to make a release

This action is published to the [GitHub Actions Marketplace](https://github.com/marketplace/actions/get-anaconda-package-version).

To make a release you need push rights to the [jacobtomlinson/gha-anaconda-package-version GitHub repository](https://github.com/jacobtomlinson/gha-anaconda-package-version).

## Steps to make a release

1. Create a new _GitHub release_ by clicking on `Draft a new release` at
https://github.com/jacobtomlinson/gha-anaconda-package-version/releases and
creating a new tag for `master`. Remember to prefix the tag with `v`, e.g.
`v1.0.5`

1. Check everything again, then click `Publish release`.
This will create a tag, and trigger a CI action to update tags like `v1`.

0 comments on commit 9a729e9

Please sign in to comment.