Skip to content

feat: Updating to Graylog, and Datanode to 7.1.8 (#181) #8

feat: Updating to Graylog, and Datanode to 7.1.8 (#181)

feat: Updating to Graylog, and Datanode to 7.1.8 (#181) #8

name: release-please
on:
push:
branches:
- main
workflow_dispatch:
permissions:
contents: write
pull-requests: write
concurrency:
group: release-please-${{ github.ref }}
cancel-in-progress: false
jobs:
release-please:
runs-on: ubuntu-latest
steps:
- uses: googleapis/release-please-action@45996ed1f6d02564a971a2fa1b5860e934307cf7 # v5
id: release
with:
token: ${{ secrets.GITHUB_TOKEN }}
config-file: release-please-config.json
manifest-file: .release-please-manifest.json
target-branch: main
# PR-only mode: chart-releaser (release.yaml) still owns the tag, the
# release and the index entry. Both use the name graylog-X.Y.Z, so if
# release-please created the release first, chart-releaser would find
# it present and — running with skip_existing: true — silently decline
# to upload the chart package. Removed in the publishing cutover, when
# chart-releaser is retired.
skip-github-release: true
# No artifacthub.io/changes step here on purpose. The annotation is
# generated from CHANGELOG.md when the chart is packaged, not committed
# onto the release PR: a commit here would race release-please's own
# force-push of the branch, and it would make hand edits to the annotation
# depend on being the last change before the merge. See
# .github/scripts/artifacthub_changes.py.