Repository navigation
chore: bump cics-crucible pin to v0.6.0 - #4755
Merged
Merged
Conversation
PINNED_REF v0.5.0 -> v0.6.0 (tests/crucible_pins.toml), runner ledger and coverage re-baselined, 17 committed ports re-proven at v0.6.0 with their evidence records re-rendered, and crucible_events.UNRELEASED removed (the pinned schema now has RETURN immediate/resp/resp2). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MQNoe4wPJgr7dbUvs3DG6D
squid-protocol
added this to the
Training Montage 🏋️ — Prepping to one-shot our 4th CICS to Java translation attempt milestone
squid-protocol
added
ci-cd
Contributor
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.
Moves the cics-crucible pin v0.5.0 -> v0.6.0 (tag cut at b794aa8b, release: https://github.com/squid-protocol/cics-crucible/releases/tag/v0.6.0).
v0.6.0 contents (format unchanged; additive SPEC: RETURN
immediatetrigger, optional immediate/resp/resp2 on RETURN events; no log corrected):hc-deedit-uctranst(#4728),pc-return-immediate(#4739),hc-resp-options(#4748), andgt-send-text-terminal(crucible #11, #4270; a fourth case that was also on main since v0.5.0).Ledger (tests/cics_crucible/baseline.json): 432 cells, 229 pass, 203 fail (was 170 ledgered). +33 cells, all expected failures on the 4 new cases, 11 scenarios x {java, java-ported, java-facade}:
java= skeleton runTask bodies (RECEIVE expected, nothing recorded); java-ported/java-facade = no port yet. engine-facts, forge-compile and cobol-stub pass on every new case (11/11 cobol-stub). No cell changed on any pre-existing case; none newly fails.crucible_refis now "v0.6.0 (b794aa8b)".Also: 17 committed ports re-proven at v0.6.0 (
crucible_port_provenance.py reprove, all scenarios pass), evidence records proven/rendered (no approvals touched),crucible_events.UNRELEASEDand its test special-case removed.cics_spec_statusrender: no change. Left alone:docs/language_status/evidence_report/*still say v0.5.0 (generated by the report job, not part of #4581's file set). Ran crucible/evidence/pr_check tests (193 pass),pr_gates --ratchets7/7,--fast5/5. The shared cics-crucible checkout was not moved; I used a scratch clone at v0.6.0 (runtests/tools/box/sync-pins.shto align the shared one after merge).Cross-repo: companion: cics-crucible tag v0.6.0 (RELEASING.md row for v0.6.0 still to add there).
🤖 Generated with Claude Code
https://claude.ai/code/session_01MQNoe4wPJgr7dbUvs3DG6D