chore(release): 0.5.0 - #19
Merged
Merged
Conversation
Scoring became CV-aware: a match score is owned by the CV that produced it, so changing CV re-opens every cached job instead of reusing a verdict reached for another profile. Minor rather than patch because the release adds a public command (`cache prune-scores`) and changes observable behavior and cost. Also restates the release-highlights inclusion rule. It read "from 0.5.0 onward each release is compared against the previous release", which said nothing about releases with nothing to compare, and implied every release belongs in the file. It now states when a release is listed, that the kind of change decides what is compared -- measured figures for performance work, changed behavior otherwise -- and that a release altering neither is left out. The 0.5.0 highlights therefore carry no performance figures, and the README Performance sections say so explicitly rather than letting 0.4.0's numbers read as current. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012DbPx4FbswofbGn41anE1q
sangowu
added a commit
that referenced
this pull request
Aug 7, 2026
Scoring became CV-aware: a match score is owned by the CV that produced it, so changing CV re-opens every cached job instead of reusing a verdict reached for another profile. Minor rather than patch because the release adds a public command (`cache prune-scores`) and changes observable behavior and cost. Also restates the release-highlights inclusion rule. It read "from 0.5.0 onward each release is compared against the previous release", which said nothing about releases with nothing to compare, and implied every release belongs in the file. It now states when a release is listed, that the kind of change decides what is compared -- measured figures for performance work, changed behavior otherwise -- and that a release altering neither is left out. The 0.5.0 highlights therefore carry no performance figures, and the README Performance sections say so explicitly rather than letting 0.4.0's numbers read as current. Claude-Session: https://claude.ai/code/session_012DbPx4FbswofbGn41anE1q Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
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.
发布 0.5.0,并按你的要求重写了 highlights 的收录规则。
为什么是 minor 而不是 patch
两条都不满足 patch 的"行为不变"承诺:
jobradar cache prune-scores收录规则改写
原文(三语):
问题在于它只说了"要对比",没说什么样的版本该收录,字面读下来像是每个版本都得进这个文件——包括纯重构和纯文档版本。改为:
三段逻辑:何时收录 → 对比什么(按改动性质分流) → 何时不收录。中西文同步改写,非直译。
0.5.0 的 highlights 没有性能数字
这批改动是正确性修复,没跑基准,也不该造数字(文件开头就写着"本文件不产生任何自己的数字")。所以 0.5.0 一节明确写成行为版本,并附成本说明:本版本增加而非减少评估量。
连带处理了一个会误导人的地方:三个 README 的 Performance 段落原本写"最新版本 0.4.0",若不动,读者会以为 0.4.0 仍是最新版。改为说明"最近一次性能改动来自 0.4.0,当前版本 0.5.0 改的是行为而非速度"。
CHANGELOG
[Unreleased]→## [0.5.0] — 2026-08-07,并新增### Validation条目f14e369→b47dfc0,沿用既有格式(两个 arm、held constant、数字、明确 verdict):assess可捞出的职位:0 → 205effective_score的分制:2 → 1highlights 里的每个数字都能追溯到这一条,符合文件自身的规则。
版本号
pyproject.toml0.4.0 → 0.5.0,uv lock已同步(避免重演 #14 那次不一致),jobradar --version实测输出v0.5.0。全量 241 passed。
🤖 Generated with Claude Code
https://claude.ai/code/session_012DbPx4FbswofbGn41anE1q