Skip to content

Add semver management action#512

Open
rechner wants to merge 16 commits into
productionfrom
rechner/semver
Open

Add semver management action#512
rechner wants to merge 16 commits into
productionfrom
rechner/semver

Conversation

@rechner

@rechner rechner commented Apr 4, 2026

Copy link
Copy Markdown
Member

Semver release management and version injection

Summary

Adds automated semantic versioning via PR labels, injects version/SHA metadata into Docker builds, and integrates GlitchTip release tracking into the deploy workflow.

Changes

Semver automation

  • New pr-validate-release.yml action validates that PRs carry a release label (major release, minor release, patch release, or noop/documentation change) and include release notes
  • New tag-and-release.yml action bumps and tags the version on merge to production using pr-semver-bump

Version injection

  • Dockerfile now accepts APIS_VERSION and APIS_GIT_SHA build args (replaces the old SENTRY_RELEASE arg)
  • Makefile derives version from git describe --tags and short SHA, passes both into the Docker build, and tags images with git-<sha> in addition to the version tag
  • All settings files expose APIS_VERSION and APIS_GIT_SHA from environment
  • Footer template links to the commit SHA on GitHub and displays the semver version

GlitchTip integration

  • Deploy workflow now creates a GlitchTip release (with commit association) before building, and records a deployment after the SSH deploy step

Comment thread .github/workflows/pr-validate-release.yml Fixed
Comment thread .github/workflows/tag-and-release.yml Fixed
@sonarqubecloud

Copy link
Copy Markdown

rechner added 3 commits May 13, 2026 11:13
- Add template-injection ignore comments to glitchtip-cli release steps
- Add template-injection ignore comment to docker image build step
- Move DEPLOY_ENV to explicit environment variable in deploy step
- Use variable substitution in deploy command for consistency
- Suppress zizmor warnings for safe template usage from git describe
@rechner
rechner marked this pull request as ready for review May 13, 2026 18:54
- Pin actions/checkout to v6.0.2 with full commit hash for reproducibility
- Add persist-credentials: false to checkout steps for security
- Convert noop-labels from array to pipe-delimited string format in pr-validate-release and tag-and-release workflows
- Remove unnecessary advanced-security configuration from zizmor workflow
- Improve workflow security and consistency across CI/CD pipeline
@github-advanced-security

Copy link
Copy Markdown

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

@sonarqubecloud

Copy link
Copy Markdown

@sonarqubecloud

Copy link
Copy Markdown

@rechner

rechner commented Jun 23, 2026

Copy link
Copy Markdown
Member Author

Will need to rework after #569 is merged to be compatible with the new deploy setup

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants