mirror of
https://github.com/MadsLorentzen/ai-job-search.git
synced 2026-09-17 00:26:26 +00:00
docs(releases): add CHANGELOG + release-based update guidance; sharpen real-path bar (#225)
Addresses #213 (how to keep up with a fast-moving upstream) and closes the verification loophole surfaced in the 2026-07-22 triage audit. - Add CHANGELOG.md (Keep a Changelog + semver), with v1.0.0 as the first tagged baseline and an Unreleased section for going forward. - SETUP.md section 8: recommend updating to a tagged release (a vetted, described checkpoint) over pulling raw master; fetch --tags and merge a tag. - README: add a "Staying up to date" pointer to Releases, the CHANGELOG, and check_upstream_updates.py. - CONTRIBUTING.md: sharpen "Claims get verified" - a test that distinguishes master from the fix is necessary but not sufficient; the failing input must be one the workflow actually produces, not one the test hand-builds. Fixes demonstrated only through a synthetic input the real code path never receives get declined even when their test is green. Note: the git tag / GitHub Release for v1.0.0 is intentionally left for the maintainer to cut. Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 4.8
parent
d88c023683
commit
905f6e0946
@@ -318,6 +318,10 @@ To wipe your profile data and start fresh:
|
||||
|
||||
`/reset` shows exactly what will be deleted and requires you to type `RESET` to confirm. Nothing is deleted until you do.
|
||||
|
||||
### Staying up to date
|
||||
|
||||
Upstream moves fast. Rather than pulling raw `master` and hoping, update your fork to a tagged [release](../../releases) - a vetted checkpoint described in [CHANGELOG.md](CHANGELOG.md). `python3 tools/check_upstream_updates.py` previews exactly which of your personalized files an update touches before you merge. Full walkthrough in [SETUP.md, section 8](SETUP.md#8-pulling-upstream-updates-into-your-fork).
|
||||
|
||||
## Tips for better results
|
||||
|
||||
### Profile depth matters
|
||||
|
||||
Reference in New Issue
Block a user