mirror of
https://github.com/MadsLorentzen/ai-job-search.git
synced 2026-11-02 13:12:50 +00:00
Jakob Stender Guldberg
7f01d75251
* ci: publish a weekly SemVer release with GitHub-generated notes Every Monday at 06:00 UTC the workflow tags master and publishes a GitHub Release whose notes list the merged PR titles. tools/next_version.py picks the version from the commits since the last release: type!: or a BREAKING CHANGE footer is major, feat is minor, anything else is patch. A manual run can override it. Weeks without commits are skipped, a master commit whose CI did not pass is never released, and forks never run it. * docs: point contributors and forks at weekly GitHub Releases PR titles are now the release notes and their type sets the version, so CONTRIBUTING and the PR template say so. README and SETUP describe releases as weekly checkpoints that passed CI instead of pointing at CHANGELOG.md. * chore(changelog): freeze at 1.7.4 and fail PRs that still edit it Rolls [Unreleased] into [1.7.4] and rewrites the intro to point at GitHub Releases. The structure test becomes a content pin: stale PRs carry entries that git would merge cleanly into the frozen section, so any edit now fails CI with a pointer to the PR title. * fix(release): address review findings on the weekly release Write access moves to the job; the override rejects existing or older versions; next_version.py reports a missing tag instead of a traceback and drops the unused rev argument; tests pin the fork guard and SHA-pinned checkout. The frozen changelog drops the date written ahead of the release, describes its guard accurately, and the guard skips on forks. * chore(changelog): re-pin the frozen hash after rebasing onto master * ci(release): compute the version with commitizen via setup-uv instead of an in-repo script A week of only docs, chore or ci commits now ships nothing on its own, matching commitizen's conventional-commit bump rules; fix, refactor and perf bump patch.
20 lines
987 B
Markdown
20 lines
987 B
Markdown
<!-- Heads-up before you publish: if you built this in a personalized fork
|
|
(your profile data, your market's job portals, another AI runtime),
|
|
note that GitHub points new PRs at the UPSTREAM repo by default.
|
|
Those adaptations live in forks - see CONTRIBUTING.md - and get
|
|
discovered via the pinned "Community forks & adaptations" discussion (#78).
|
|
Check the "base repository" dropdown above before you continue. -->
|
|
<!-- The PR title becomes this change's line in the weekly release notes and
|
|
its type sets the version: feat = minor, type!: = major,
|
|
fix/refactor/perf = patch, docs/chore/ci alone = no release.
|
|
Don't edit CHANGELOG.md; it is frozen. -->
|
|
|
|
## What changed and why
|
|
|
|
## Failing case / reproduction (for fixes)
|
|
|
|
## Verification
|
|
<!-- What you ran, per CONTRIBUTING: python3 tools/lint_skills.py,
|
|
python3 tools/check_framework_version.py, bun test / bun run typecheck
|
|
in touched CLIs, python3 -m unittest discover -s tests -->
|