Conversation
chore: release v0.13.2
Zious11
added a commit
that referenced
this pull request
Jul 25, 2026
Release PR #440 9601d71 merged to main (human-merged). Tag v0.13.2 (lightweight). GH release 4 assets published 2026-07-25T00:36:46Z. Back-merge PR #441 TRUE-MERGE e8841d7 to develop (human-authorized gh pr merge --merge; ancestry PASS, no DRIFT-BACKMERGE- SQUASH recurrence). Ships wave-85: IEC-104 timed-command detection (TypeIDs 58-64) + SEC-001 ENIP unsafe elimination + gate-fix. Version 0.13.1→0.13.2. CR-004 CHANGELOG trim applied at release cut. STATE.md: release fields updated (released_version v0.13.2, released_at 2026-07-25, release_tag v0.13.2, release_commit 9601d71..., develop_head e8841d7..., cargo_version 0.13.2); EXACT RESUME POINT D-512; Phase Progress v0.13.2 RELEASED row added; Concurrent Cycles wave-085 develop head updated; CPS D-507 rolled off / D-512 on; D-512 Decisions Log entry; Session Resume Checkpoint D-512 replaces D-511; SIZE BUDGET banner corrected to ~315 lines (wc-l). cycles/wave-085/session-checkpoints.md: D-511 checkpoint archived. cycles/wave-085/burst-log.md: D-507 CPS archival + D-512 burst entry. Count-propagation sweep: no numeric BC/VP/story counts changed in this burst. Version string sweep: all v0.13.1 and 0ab6f52 hits are legitimate historical audit-trail entries (prior_released_version, frozen gate SHA, release row). No propagation gaps.
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.
Back-merge: v0.13.2 → develop
This PR merges the
v0.13.2release branch (main) back intodevelopto keep thetwo branches in sync after the release.
CRITICAL — Must be merged as a TRUE MERGE COMMIT
Do NOT use squash merge or rebase. This PR must be merged with Create a merge commit
so that
mainbecomes a proper ancestor ofdevelop.Merging as squash or rebase breaks the git ancestry chain (DRIFT-BACKMERGE-SQUASH-001),
preventing
git merge-base --is-ancestorfrom confirming that release commits arecontained in develop.
Merge method: "Create a merge commit" only.
Precedent
D-491 (v0.13.1) back-merge: PR #433 — same pattern, same constraint.
Commits merged from main
9601d711— Merge pull request chore: release v0.13.2 #440 from Zious11/release/0.13.2b33e45f9— chore: release v0.13.2