Skip to content

fix: improve release pipeline#11

Merged
krakenhavoc merged 1 commit into
mainfrom
fix/release-pipeline
May 19, 2026
Merged

fix: improve release pipeline#11
krakenhavoc merged 1 commit into
mainfrom
fix/release-pipeline

Conversation

@krakenhavoc

Copy link
Copy Markdown
Contributor

Summary

  • Restrict release trigger to semver tags only (v[0-9]+.[0-9]+.[0-9]+) so the major version tag update doesn't re-trigger the workflow
  • Auto-generate structured release notes with usage snippet, filtered changelog, and comparison link
  • Add .github/release.yaml for categorized changelog labels
  • Mark each release as latest via make_latest: true

Test plan

  • Push a test tag to verify the workflow triggers correctly
  • Verify major-version-only tags (e.g. v1) do not trigger the release workflow

@krakenhavoc
krakenhavoc merged commit 067a97d into main May 19, 2026
3 checks passed
@krakenhavoc
krakenhavoc deleted the fix/release-pipeline branch May 19, 2026 14:09
krakenhavoc added a commit that referenced this pull request May 26, 2026
PR #11 (merged 2026-05-19) improved the release pipeline; CI-internal
changes noted in CHANGELOG. Add CAA record advisory for March 2027
enforcement of RFC 8657 parameters (SC-098v2, passed 2026-05-13).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant