-
Notifications
You must be signed in to change notification settings - Fork 110
Description
Hoi and thanks for maintaining this helm chart! :)
I setup a demo at jessebot/mastodon-helm-chart on how to setup a release via github-pages using the helm/chart-releaser-action. I can submit a pull request with that if you'd like. In the demo I have on my fork of this repo, I'm also using the latest versions of the bitnami oci compliant helm charts, but I would remove that from a potential PR on this topic to keep it scoped properly.
The gist of the required changes would be:
- create
charts/mastodondirectory - move
templates/,values.yaml,dev-values.yaml,Chart.yaml, andChart.lockintocharts/mastodon - create a branch called
gh-pages - under ⚙️ Settings > Actions > Workflow Permissions select "Read and write permissions"
- create a workflow file in `.github/workflows/release.yaml` something like this:
name: Release Chart
concurrency: chart_releaser
on:
push:
branches:
- main
paths-ignore:
- '.github/**'
- '**/README.md'
- 'LICENSE'
jobs:
release:
runs-on: ubuntu-22.04
steps:
- name: Checkout
uses: actions/checkout@v3
- name: Fetch history
run: git fetch --prune --unshallow
- name: Configure Git
run: |
git config user.name "$GITHUB_ACTOR"
git config user.email "$GITHUB_ACTOR@users.noreply.github.com"
# See https://github.com/helm/chart-releaser-action/issues/6
- name: Set up Helm
uses: azure/setup-helm@v3.5
with:
version: v3.11.1
- name: Add dependency chart repos
run: |
helm dep update charts/mastodon
- name: Run chart-releaser
uses: helm/chart-releaser-action@v1.5.0
env:
CR_GENERATE_RELEASE_NOTES: true
CR_TOKEN: "${{ secrets.GITHUB_TOKEN }}"This is not dissimilar to what we're doing over in the community lead nextcloud/helm repo. The only caveat is that you still have to remember to manually bump the helm chart version each time in any commits you merge.
This isn't urgent or required for me right now, but it would be nice to have more official releases :)