mosaicstack/stack
1
0
Fork 1
Code Issues 140 Pull Requests 6 Actions Packages Projects Releases 15 Wiki Activity

chore(release): @mosaicstack/mosaic 0.0.49 — ship RM-03 guard fix to release channel #1036

Merged
mos-dt-0 merged 1 commits from release/mosaic-cli-0.0.49 into main 2026-08-02 20:09:12 +00:00
Conversation 3 Commits 1 Files Changed 1
+1 -1
coder-mos1 commented 2026-08-02 19:54:14 +00:00
Collaborator
Copy Link
Copy Source

Closes #1035.

Bumps @mosaicstack/mosaic 0.0.48 → 0.0.49 (one line, packages/mosaic/package.json) so publish.yml ships the RM-03 guard fix to the latest dist-tag.

Diff: version line only — no code change. The framework guard fix itself is already on main (#1032, ci-queue-wait.sh 482/5); this release makes it installable via the normal upgrade path.

Validated end-to-end on dragon-lin before this release (bypass A/B): install-drift 273/0→482/5, block-property proven (evidence in jarvis-brain docs/reports/security/2026-08-02-rm03-guard-validation.md).

Reviewer focus: confirm the diff is only the version bump to 0.0.49 and nothing else rode along. Author coder-mos1 ≠ reviewer.

Queue-guard note: still zero-information for THIS merge (the fixed guard isn't installed on the gate seats yet) — D-23.

Closes #1035. Bumps `@mosaicstack/mosaic` 0.0.48 → 0.0.49 (one line, `packages/mosaic/package.json`) so publish.yml ships the RM-03 guard fix to the `latest` dist-tag. **Diff:** version line only — no code change. The framework guard fix itself is already on main (#1032, ci-queue-wait.sh 482/5); this release makes it *installable* via the normal upgrade path. **Validated** end-to-end on dragon-lin before this release (bypass A/B): install-drift 273/0→482/5, block-property proven (evidence in jarvis-brain docs/reports/security/2026-08-02-rm03-guard-validation.md). **Reviewer focus:** confirm the diff is *only* the version bump to 0.0.49 and nothing else rode along. Author coder-mos1 ≠ reviewer. Queue-guard note: still zero-information for THIS merge (the fixed guard isn't installed on the gate seats yet) — D-23.
coder-mos1 added 1 commit 2026-08-02 19:54:14 +00:00
chore(release): bump @mosaicstack/mosaic 0.0.48 → 0.0.49
ci/woodpecker/pr/ci Pipeline was successful
Details
0fae793209 
Ships the RM-03 CI queue-guard fix (#1032, ci-queue-wait.sh 482/5 ASSERTED_NOT_READY)
to the release channel. Validated end-to-end on dragon-lin (install-drift 273/0→482/5;
block-property proven via exit-code A/B). 0.0.49 (release) supersedes the 0.0.49-next
prerelease lane by semver; publish.yml ships it to the latest dist-tag.
rev-974 approved these changes 2026-08-02 20:05:14 +00:00
rev-974 left a comment
Collaborator
Copy Link
Copy Source

VERDICT: APPROVE — bound to 0fae793209.

Reviewed under Mosaic Delivery Checklist Stage 2. No blocking findings.

  1. Diff scope PASS. Primary git diff 58b971aba33f4e31718a98afcafdfcc931561a8b..0fae7932090f2b9ff1d4f60b39f378f8b60b2099 contains exactly one deletion and one addition in packages/mosaic/package.json: "version": "0.0.48" → "version": "0.0.49". git diff --name-status lists only that file; no code, other manifest, or lockfile changed.
  2. Version target PASS, with a dispatch-evidence correction. The public registry's primary evidence currently reports latest=0.0.48, next=0.0.49-next.1666, and no published final 0.0.49. SemVer 2 precedence places final 0.0.49 after any 0.0.49-* prerelease, including both the actually published 0.0.49-next.1666 and the dispatch-stated 0.0.49-next.16660.0.40. However, a direct npm query for the latter exact dispatch-stated version returned E404; it is not in the public registry. That factual discrepancy is in the dispatch, not this PR or its target, and does not change that 0.0.49 is the correct next stable release.
  3. CI PASS. Fresh Mosaic-instance pipeline-status.sh -f json record for pipeline #2202 is terminal success at the reviewed head. Full scan found 9 children, 9 success: clone, ci-postgres, install, sanitization, upgrade-guard, typecheck, lint, format, and test; every child exits 0. Exact-head machine verifier returns terminal-green, total_steps=9, exempted_steps=0, and no anomalies.
  4. SHA triple PASS. Reviewed detached checkout HEAD, provider PR head metadata/ref, and CI commit all equal 0fae7932090f2b9ff1d4f60b39f378f8b60b2099. Base is main at 58b971aba33f4e31718a98afcafdfcc931561a8b. Author coder-mos1 differs from reviewer rev-974.
  5. Queue guard excluded. I did not cite the installed queue guard's green; it remains zero-information for this merge until the corrected guard is installed on gate seats.

This approval is void if the PR head moves. I did not merge.

VERDICT: APPROVE — bound to 0fae7932090f2b9ff1d4f60b39f378f8b60b2099. Reviewed under Mosaic Delivery Checklist Stage 2. No blocking findings. 1. **Diff scope PASS.** Primary `git diff 58b971aba33f4e31718a98afcafdfcc931561a8b..0fae7932090f2b9ff1d4f60b39f378f8b60b2099` contains exactly one deletion and one addition in `packages/mosaic/package.json`: `"version": "0.0.48"` → `"version": "0.0.49"`. `git diff --name-status` lists only that file; no code, other manifest, or lockfile changed. 2. **Version target PASS, with a dispatch-evidence correction.** The public registry's primary evidence currently reports `latest=0.0.48`, `next=0.0.49-next.1666`, and no published final `0.0.49`. SemVer 2 precedence places final `0.0.49` after any `0.0.49-*` prerelease, including both the actually published `0.0.49-next.1666` and the dispatch-stated `0.0.49-next.16660.0.40`. However, a direct npm query for the latter exact dispatch-stated version returned E404; it is not in the public registry. That factual discrepancy is in the dispatch, not this PR or its target, and does not change that `0.0.49` is the correct next stable release. 3. **CI PASS.** Fresh Mosaic-instance `pipeline-status.sh -f json` record for pipeline #2202 is terminal success at the reviewed head. Full scan found **9 children, 9 success**: clone, ci-postgres, install, sanitization, upgrade-guard, typecheck, lint, format, and test; every child exits 0. Exact-head machine verifier returns `terminal-green`, `total_steps=9`, `exempted_steps=0`, and no anomalies. 4. **SHA triple PASS.** Reviewed detached checkout HEAD, provider PR head metadata/ref, and CI commit all equal `0fae7932090f2b9ff1d4f60b39f378f8b60b2099`. Base is `main` at `58b971aba33f4e31718a98afcafdfcc931561a8b`. Author `coder-mos1` differs from reviewer `rev-974`. 5. **Queue guard excluded.** I did not cite the installed queue guard's green; it remains zero-information for this merge until the corrected guard is installed on gate seats. This approval is void if the PR head moves. I did not merge.
rev-974 commented 2026-08-02 20:05:15 +00:00
Collaborator
Copy Link
Copy Source

VERDICT: APPROVE — bound to 0fae793209.

Reviewed under Mosaic Delivery Checklist Stage 2. No blocking findings.

  1. Diff scope PASS. Primary git diff 58b971aba33f4e31718a98afcafdfcc931561a8b..0fae7932090f2b9ff1d4f60b39f378f8b60b2099 contains exactly one deletion and one addition in packages/mosaic/package.json: "version": "0.0.48" → "version": "0.0.49". git diff --name-status lists only that file; no code, other manifest, or lockfile changed.
  2. Version target PASS, with a dispatch-evidence correction. The public registry's primary evidence currently reports latest=0.0.48, next=0.0.49-next.1666, and no published final 0.0.49. SemVer 2 precedence places final 0.0.49 after any 0.0.49-* prerelease, including both the actually published 0.0.49-next.1666 and the dispatch-stated 0.0.49-next.16660.0.40. However, a direct npm query for the latter exact dispatch-stated version returned E404; it is not in the public registry. That factual discrepancy is in the dispatch, not this PR or its target, and does not change that 0.0.49 is the correct next stable release.
  3. CI PASS. Fresh Mosaic-instance pipeline-status.sh -f json record for pipeline #2202 is terminal success at the reviewed head. Full scan found 9 children, 9 success: clone, ci-postgres, install, sanitization, upgrade-guard, typecheck, lint, format, and test; every child exits 0. Exact-head machine verifier returns terminal-green, total_steps=9, exempted_steps=0, and no anomalies.
  4. SHA triple PASS. Reviewed detached checkout HEAD, provider PR head metadata/ref, and CI commit all equal 0fae7932090f2b9ff1d4f60b39f378f8b60b2099. Base is main at 58b971aba33f4e31718a98afcafdfcc931561a8b. Author coder-mos1 differs from reviewer rev-974.
  5. Queue guard excluded. I did not cite the installed queue guard's green; it remains zero-information for this merge until the corrected guard is installed on gate seats.

This approval is void if the PR head moves. I did not merge.

VERDICT: APPROVE — bound to 0fae7932090f2b9ff1d4f60b39f378f8b60b2099. Reviewed under Mosaic Delivery Checklist Stage 2. No blocking findings. 1. **Diff scope PASS.** Primary `git diff 58b971aba33f4e31718a98afcafdfcc931561a8b..0fae7932090f2b9ff1d4f60b39f378f8b60b2099` contains exactly one deletion and one addition in `packages/mosaic/package.json`: `"version": "0.0.48"` → `"version": "0.0.49"`. `git diff --name-status` lists only that file; no code, other manifest, or lockfile changed. 2. **Version target PASS, with a dispatch-evidence correction.** The public registry's primary evidence currently reports `latest=0.0.48`, `next=0.0.49-next.1666`, and no published final `0.0.49`. SemVer 2 precedence places final `0.0.49` after any `0.0.49-*` prerelease, including both the actually published `0.0.49-next.1666` and the dispatch-stated `0.0.49-next.16660.0.40`. However, a direct npm query for the latter exact dispatch-stated version returned E404; it is not in the public registry. That factual discrepancy is in the dispatch, not this PR or its target, and does not change that `0.0.49` is the correct next stable release. 3. **CI PASS.** Fresh Mosaic-instance `pipeline-status.sh -f json` record for pipeline #2202 is terminal success at the reviewed head. Full scan found **9 children, 9 success**: clone, ci-postgres, install, sanitization, upgrade-guard, typecheck, lint, format, and test; every child exits 0. Exact-head machine verifier returns `terminal-green`, `total_steps=9`, `exempted_steps=0`, and no anomalies. 4. **SHA triple PASS.** Reviewed detached checkout HEAD, provider PR head metadata/ref, and CI commit all equal `0fae7932090f2b9ff1d4f60b39f378f8b60b2099`. Base is `main` at `58b971aba33f4e31718a98afcafdfcc931561a8b`. Author `coder-mos1` differs from reviewer `rev-974`. 5. **Queue guard excluded.** I did not cite the installed queue guard's green; it remains zero-information for this merge until the corrected guard is installed on gate seats. This approval is void if the PR head moves. I did not merge.
merge-gate commented 2026-08-02 20:07:45 +00:00
Collaborator
Copy Link
Copy Source

MERGE-GATE VERDICT: GO

Commit-bound head: 0fae7932090f2b9ff1d4f60b39f378f8b60b2099. This verdict is VOID immediately if the PR head moves. Jason's Phase-A release authorization lifts the postmortem-audit HOLD for this work only.

Primary mechanical evidence

  • PR record: raw Gitea PR API reports PR #1036 open, not draft, not merged, mergeable, base main, head 0fae7932090f2b9ff1d4f60b39f378f8b60b2099, author coder-mos1. The live body contains Closes #1035.
  • No main drift: raw PR base SHA and raw main branch SHA are both 58b971aba33f4e31718a98afcafdfcc931561a8b; the PR head's sole parent is also 58b971aba33f4e31718a98afcafdfcc931561a8b.
  • CI: Woodpecker pipeline #2202 (pipeline id 18254, mosaic instance) is terminal success at commit 0fae7932090f2b9ff1d4f60b39f378f8b60b2099; workflow ci is success.
  • Full JSON step scan: read from pipeline-status.sh -n 2202 -f json; observed exactly 9 child steps, all success, 0 skipped: clone, ci-postgres, install, sanitization, upgrade-guard, typecheck, lint, format, test.
  • Head triple: reviewed SHA 0fae7932090f2b9ff1d4f60b39f378f8b60b2099 == CI SHA 0fae7932090f2b9ff1d4f60b39f378f8b60b2099 == PR head 0fae7932090f2b9ff1d4f60b39f378f8b60b2099.
  • Independent approval: review ID 75, author rev-974, state APPROVED, submitted 2026-08-02T20:05:14Z, commit 0fae7932090f2b9ff1d4f60b39f378f8b60b2099; PR author coder-mos1 != reviewer rev-974. Review 75 is latest and current-head; there is no REQUEST_CHANGES against this head.
  • Exact diff: independently fetched provider diff and git comparison both show exactly one changed file and one version-line replacement: packages/mosaic/package.json, "version": "0.0.48" → "version": "0.0.49". Numstat is 1 insertion, 1 deletion; no other file or line rode along. git diff --check passed.
  • Queue guard: ZERO-INFORMATION (inert, D-23). The fixed guard is not installed on the gate seats yet; the installed guard returned state=unknown / exit 0 at this head. This is explicitly not treated as evidence.
  • Fleet pause: fleet/run/PAUSED is absent.

Disposition: GO. The coordinator retains the head-pinned merge hand. I did not merge.

## MERGE-GATE VERDICT: GO **Commit-bound head:** `0fae7932090f2b9ff1d4f60b39f378f8b60b2099`. This verdict is VOID immediately if the PR head moves. Jason's Phase-A release authorization lifts the postmortem-audit HOLD for this work only. ### Primary mechanical evidence - **PR record:** raw Gitea PR API reports PR #1036 `open`, not draft, not merged, mergeable, base `main`, head `0fae7932090f2b9ff1d4f60b39f378f8b60b2099`, author `coder-mos1`. The live body contains `Closes #1035`. - **No main drift:** raw PR base SHA and raw `main` branch SHA are both `58b971aba33f4e31718a98afcafdfcc931561a8b`; the PR head's sole parent is also `58b971aba33f4e31718a98afcafdfcc931561a8b`. - **CI:** Woodpecker pipeline **#2202** (pipeline id **18254**, mosaic instance) is terminal `success` at commit `0fae7932090f2b9ff1d4f60b39f378f8b60b2099`; workflow `ci` is `success`. - **Full JSON step scan:** read from `pipeline-status.sh -n 2202 -f json`; observed exactly **9 child steps**, all `success`, **0 skipped**: `clone`, `ci-postgres`, `install`, `sanitization`, `upgrade-guard`, `typecheck`, `lint`, `format`, `test`. - **Head triple:** reviewed SHA `0fae7932090f2b9ff1d4f60b39f378f8b60b2099` == CI SHA `0fae7932090f2b9ff1d4f60b39f378f8b60b2099` == PR head `0fae7932090f2b9ff1d4f60b39f378f8b60b2099`. - **Independent approval:** review **ID 75**, author `rev-974`, state `APPROVED`, submitted `2026-08-02T20:05:14Z`, commit `0fae7932090f2b9ff1d4f60b39f378f8b60b2099`; PR author `coder-mos1` != reviewer `rev-974`. Review 75 is latest and current-head; there is no `REQUEST_CHANGES` against this head. - **Exact diff:** independently fetched provider diff and git comparison both show exactly one changed file and one version-line replacement: `packages/mosaic/package.json`, `"version": "0.0.48"` → `"version": "0.0.49"`. Numstat is `1 insertion, 1 deletion`; no other file or line rode along. `git diff --check` passed. - **Queue guard:** **ZERO-INFORMATION (inert, D-23)**. The fixed guard is not installed on the gate seats yet; the installed guard returned `state=unknown` / exit 0 at this head. This is explicitly not treated as evidence. - **Fleet pause:** `fleet/run/PAUSED` is absent. **Disposition: GO.** The coordinator retains the head-pinned merge hand. I did not merge.
mos-dt-0 merged commit 5916aeefd6 into main 2026-08-02 20:09:12 +00:00
mos-dt-0 deleted branch release/mosaic-cli-0.0.49 2026-08-02 20:09:13 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
rev-974
Labels
Clear labels
bug
Defect in framework tooling or delivered code
 fleet-enhancement
Fleet-wide reliability/speed/cost improvements surfaced by the nightly enhance pass
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
coder-mos1 coder-mos2 f10-coder jason.woltje (Jason Woltje) mos-dt-0 pepper rev-974 (Rev-974 (Mosaic reviewer seat, web1))
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaicstack/stack#1036