caoer115/ucc
1
0
Fork 0
Code Issues Pull requests 45 Projects Releases Packages Wiki Activity

release v4: cccd v1.12.156 (9dc3f100) — record, current.md, CHANGELOG § v4 #44

Open
caoer115 wants to merge 0 commits from agent/0f011458-release-v4 into main
pull from: agent/0f011458-release-v4
merge into: caoer115:main
Conversation 0 Commits - Files changed -
caoer115 commented 2026-10-17 09:03:16 +00:00
Owner
Copy link

The v4 release commit daa264d (tasks/release-v4.md § Steps 3), off main 4d7609b.

  • releases/v4.md: cut by rounds/lib/release-record.sh from the candidate stage ucc-round-9dc3f100 (built 2026-10-17T08:54:00Z on workstation-nyc-2 at ucc 4d7609b, cccd tag v1.12.156 9dc3f100, --cccd-prev 585c915d, cc-continuity b59aad3b; sha256 8739b3a5…), status released, paseo 0.11.2.
  • releases/current.md: § version v4, § pins from the record, § components by hand.
  • CHANGELOG.md § v4: the card's draft with its placeholders filled from the merged cards; its second paragraph is the release's own step for a v3 host, ucc update --trust (ruling A6).

Gates so far:

  • rounds/lib/release-check.sh passes the move from the forge's release (5ba1b10b) and from v3's release commit (4801f8fb): rc 0 both. Moved: UPDATE.md § sop and § tooling, releases/current.md § version and § pins, all carried by release v4.
  • rounds/lib/release-publish.sh: 8 objects at https://get-ucc.sui.pics/releases/ucc/v4/, each served and hashed to releases/v4.md, check rc 0. get-ucc's DEFAULT_RELEASE_PIN is untouched.

Not merged until the proof passes: two launches at this commit (ruling A20). r276 runs --public --public-branch release-candidate; r277 runs the same commit on a stage with N−1 v1.12.150. release moves only on the leader's line after both read GATE: pass.

The v4 release commit `daa264d` (tasks/release-v4.md § Steps 3), off main `4d7609b`. - `releases/v4.md`: cut by `rounds/lib/release-record.sh` from the candidate stage `ucc-round-9dc3f100` (built 2026-10-17T08:54:00Z on workstation-nyc-2 at ucc `4d7609b`, cccd tag v1.12.156 `9dc3f100`, `--cccd-prev 585c915d`, cc-continuity `b59aad3b`; sha256 `8739b3a5…`), status released, paseo 0.11.2. - `releases/current.md`: § version v4, § pins from the record, § components by hand. - `CHANGELOG.md § v4`: the card's draft with its placeholders filled from the merged cards; its second paragraph is the release's own step for a v3 host, `ucc update --trust` (ruling A6). Gates so far: - `rounds/lib/release-check.sh` passes the move from the forge's `release` (`5ba1b10b`) and from v3's release commit (`4801f8fb`): rc 0 both. Moved: UPDATE.md § sop and § tooling, releases/current.md § version and § pins, all carried by release v4. - `rounds/lib/release-publish.sh`: 8 objects at `https://get-ucc.sui.pics/releases/ucc/v4/`, each served and hashed to `releases/v4.md`, check rc 0. get-ucc's `DEFAULT_RELEASE_PIN` is untouched. Not merged until the proof passes: two launches at this commit (ruling A20). r276 runs `--public --public-branch release-candidate`; r277 runs the same commit on a stage with N−1 v1.12.150. `release` moves only on the leader's line after both read `GATE: pass`.
releases/v4.md cut by rounds/lib/release-record.sh from the candidate stage
ucc-round-9dc3f100 (built 2026-10-17T08:54:00Z on workstation-nyc-2 at ucc
4d7609b0, --cccd-prev 585c915d; sha256 8739b3a5…), status released, paseo
0.11.2; releases/current.md § version v4, § pins from the record, § components
by hand; CHANGELOG.md § v4 from tasks/release-v4.md § CHANGELOG § v4 — draft,
its placeholders filled from the merged cards.

The core's tag round r274 (13-16-ucc-rearchitecture results/rounds/r274.md)
read GATE: pass at 9dc3f100 with every tag-round stage. This commit is proven by
the two launches ruling A20 sets — --public from release-candidate, and the same
commit on a stage whose N-1 is v1.12.150 — each GATE: pass with no waiver;
release moves here only after both. The private set is published from the same
stage to get-ucc releases/ucc/v4/ and read back against the record before this
commit reaches main.
This branch is already included in the target branch. There is nothing to merge.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin agent/0f011458-release-v4:agent/0f011458-release-v4
git switch agent/0f011458-release-v4

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main
git merge --no-ff agent/0f011458-release-v4
git switch agent/0f011458-release-v4
git rebase main
git switch main
git merge --ff-only agent/0f011458-release-v4
git switch agent/0f011458-release-v4
git rebase main
git switch main
git merge --no-ff agent/0f011458-release-v4
git switch main
git merge --squash agent/0f011458-release-v4
git switch main
git merge --ff-only agent/0f011458-release-v4
git switch main
git merge agent/0f011458-release-v4
git push origin main
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
caoer115/ucc!44
No description provided.