chore(release): 0.8.0 - #391
Merged
Merged
Conversation
Minor, not patch: two verbs that answered now refuse, and one refusal path changed its exit code. Ships #355 and #371. Both are the same property in different places: a number taken off a part that is missing a piece, and a fault in this tool reported in the block that otherwise means the part's defect. Neither is fixed in the published 0.7.8. Callers affected: `measure` and `render` now exit 4 on a part whose depfile names a file that is not on disk, where they exited 0 with a number and four PNGs. A backend that raises now exits 4 rather than 0, with the payload still emitted in full.
…ibes Caught by the repo's own gate, which is the point of having it: three tests refused a version bump that left the normative documents claiming v0.7.8, and the SPEC-report/SPEC-diff samples still showing the old version in a payload a consumer copies. That is 2.5 -- a status claim is part of the gate -- enforced rather than asserted. Eleven references across nine files, plus the release date on AGENTS.md's status line.
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
1 participant
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.
Version bump only; everything here is already on
main.Minor, not patch. Two verbs that answered now refuse, and one refusal path changed
its exit code.
Ships
measureandrenderstill answer off a part whose data file is absent #355 --measureandrenderrefuse a part the engine built without a file itasked for. In 0.7.8
checkexits4on that part whilemeasureprints the volume ofa bare plate and
renderwrites four PNGs of it. The narrowing that keeps a%-edsubtree from being a false refusal is shared by all three verbs.
measureis emitted as a part fault, at exit 0, distinguishable only by prose #371 --refused_bysays whether a refusal was the part's doing or partspec's, anda tool fault exits
4instead of0.Both are the same property in different places: a number taken off a part that is missing
a piece, and a fault in this tool reported in the block that otherwise means the part's
defect.
Callers affected
measure/renderon a part with an absentimport()orsurface()target:0->4. That part was never measurable; the old numbers described something else.0->4, with the payload still emitted in full -- oneraising backend still costs one name and not the other thirteen. This is a state no
consumer has seen (exit 4 with a complete payload) and
docs/AGENT-CONTRACT.md§2.4now describes it.
refused_byis additive;refusedkeepsdict[str, str].just checkclean.