Add weekly auto-tag for CalVer releases#20
Merged
Merged
Conversation
Tuesday 08:00 UTC cron tags vYYYY.MM.DD if there are commits since the last release tag, then dispatches release.yml via `gh workflow run` (GITHUB_TOKEN-driven tag pushes don't trigger other workflows, by design). Same-day reruns get .N suffixes. workflow_dispatch with force=true skips the "commits since" check for manual re-runs. release.yml now accepts workflow_dispatch and gates the job to refs/tags/v* so accidental dispatches against main are no-ops without leaking partial artifacts. CHANGELOG [Unreleased] documents the new cadence.
wnstfy
enabled auto-merge (squash)
May 21, 2026 11:17
Contributor
Trivy misconfiguration findings (HIGH + CRITICAL)Findings below. Fix the issue or add an ignore entry to |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Tuesday 08:00 UTC cron tags `vYYYY.MM.DD` when commits exist since the last release, then dispatches `release.yml` to publish the signed artifacts.
Why this shape
`GITHUB_TOKEN`-driven tag pushes deliberately don't trigger other workflows (GitHub's anti-recursion rule), so a tag-push alone wouldn't fire `release.yml`. Two clean options:
This PR uses option 2 to avoid introducing another long-lived secret. `release.yml` gains `workflow_dispatch` and an `if: startsWith(github.ref, 'refs/tags/v')` gate so a manual dispatch from `main` is a no-op rather than producing broken artifacts.
Behaviour
Cadence sits after the Monday `weekly-audit` cron (06:00 UTC) and the Tuesday `scorecard` cron (07:20 UTC), so each weekly release reflects the latest CVE state and Scorecard run.
Test plan