ci: add weekly tag + release workflow

[steebchen]

What

Adds a new scheduled GitHub Actions workflow (.github/workflows/weekly-release.yml) that creates a fresh tag + GitHub release every week.

• Runs on a cron schedule every Monday at 09:00 UTC (plus workflow_dispatch for manual runs).
• Computes the next version by taking the latest vX.Y.Z tag and bumping the minor (e.g. v1.4.0 → v1.5.0), defaulting to v0.1.0 if none exist.
• Creates the tag and a release on main with auto-generated notes via gh release create.

Why it triggers the existing docker publish

The existing images.yml workflow already builds and publishes the docker images on release: [published]. The key detail: the default GITHUB_TOKEN does not trigger downstream workflow events (GitHub's recursion guard). So this workflow uses the repo's existing custom PAT secrets.GH_TOKEN — the same token image-actions.yml uses with the comment "use custom token so actions get triggered on push" — to create the release. This ensures the release: published event fires and images.yml runs the docker image publish.

No application code changed; this is CI-only.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Automated weekly release process has been established. Releases will now be generated every Monday at 09:00 UTC, with manual triggering available.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 58406c77-7f46-40d7-be8e-62d333049cf2

📥 Commits

Reviewing files that changed from the base of the PR and between c07a40b and 1b7d921.

📒 Files selected for processing (1)

• .github/workflows/weekly-release.yml

---

Walkthrough

A new GitHub Actions workflow weekly-release is added. It triggers on a weekly Monday cron schedule and via manual dispatch, computes the next minor semver version from existing v*.*.* tags (defaulting to v0.0.0), and creates a GitHub release and tag targeting the main branch with auto-generated release notes.

Changes

Weekly Release Workflow

Layer / File(s)	Summary
Workflow triggers, permissions, and checkout .github/workflows/weekly-release.yml	Defines the weekly-release workflow triggered by a weekly cron (Mondays 09:00 UTC) and workflow_dispatch, grants contents: write permission, and checks out the repository with full git history (fetch-depth: 0) and no persisted credentials.
Version computation and release creation .github/workflows/weekly-release.yml	Scans existing v*.*.* tags to find the latest semver (defaulting to v0.0.0), increments the minor version, and runs gh release create with the computed tag targeting main and auto-generated release notes using a custom GH_TOKEN secret.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The PR title 'ci: add weekly tag + release workflow' accurately and concisely describes the main change: adding a new CI workflow for automated weekly tags and releases.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch weekly-release-tag-ci

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}