Prepare citation metadata for v0.3.2 - #188
Merged
Merged
Conversation
The freeze workflow asserts `CITATION.cff` names the snapshot version, so this
has to land before the v0.3.2 evaluation freeze can pass preflight:
[[ "$(sed -n 's/^version: "\([^"\]*\)"/\1/p' CITATION.cff)" == "${SNAPSHOT_VERSION#v}" ]]
v0.3.2 is a patch under the policy in RELEASES.md. The real-project-v2 corpus,
its 72 cases, and their reviewed ground truth are all unchanged; what moves is
the analyzer pin and harness behaviour. That is explicitly not a corpus
expansion or a ground-truth redefinition.
`date-released` also moves to the intended release date. It had been left at
2026-08-18, which was v0.3.0's date rather than v0.3.1's.
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.
Prerequisite for the real-project-v2 re-freeze (#185). The freeze workflow
hard-asserts the citation version matches the snapshot version, so preflight
fails until this lands:
Why v0.3.2 and not v0.4.0
Patch, under the SemVer policy in
RELEASES.md:The real-project-v2 corpus, its 72 cases, and their reviewed ground truth are
unchanged. What moves is the Bifrost pin (v0.10.2 → v0.10.8) and harness
behaviour. Nothing is added to the scored corpus and no ground truth is
redefined, so a minor bump would overstate it.
Also fixed
date-releasedwas2026-08-18— v0.3.0's release date, not v0.3.1's(2026-08-26). It now carries the intended v0.3.2 date rather than propagating
that.
🤖 Generated with Claude Code