Skip to content

chore(release): record 3.1.2 channel completion - #309

Merged
wybaby168 merged 2 commits into
mainfrom
release/3.1.2-status
Sep 20, 2026
Merged

wybaby168 merged 2 commits into
mainfrom
release/3.1.2-status

Conversation

@wybaby168

@wybaby168 wybaby168 commented Sep 20, 2026 •

Copy link
Copy Markdown
Member

Summary

  • Record the completed 3.1.2 rollout with zero audited channel gaps.
  • Make status-only CI skip runtime checks that require build outputs, while keeping repository governance and metadata checks.
  • Backport the workflow guard to the private source after the frozen 3.1.2 postcheck; do not alter the release candidate.

Related Issue

N/A: this is release-status and CI maintenance for the completed 3.1.2 rollout.

Change Classification

  • User-visible UI or rendering change
  • Non-visual change
  • File-format or renderer behavior
  • Public API, package, Worker, WASM, or deployment-path change

Verification

Check Result
pnpm release:status:write Pass: 100 Release assets, 89 npm packages, 17 component repositories, zero gaps
node --test .github/scripts/release-ci-impact.test.mjs Pass
pnpm verify:github-governance Pass
Public CI and PR governance on this head Required before merge

Sample / Fixture Evidence

N/A: only release metadata and CI conditions change; no renderer input or sample is affected.

Visual Evidence

N/A: non-visual release metadata and CI maintenance.

Risk And Compatibility

  • Affected packages/formats: no package or format bytes; only artifacts/release-status.json and the public status-only CI path.
  • Compatibility or migration risk: none for consumers; runtime regressions still run for runtime changes.
  • Rollback: revert this metadata/CI commit without moving the immutable v3.1.2 tag or replacing npm bytes.

Checklist

  • I added or updated focused automated coverage, or explained why it is not needed.
  • I updated user-facing documentation or release notes when behavior or API changed, or marked them not applicable.
  • I verified offline/private-deployment paths when changing Worker, WASM, fonts, vendor assets, or URLs, or marked them not applicable.
  • I did not commit secrets, customer files, private samples, generated caches, or unrelated changes.

Source commit: 98434eb4ca3c7720eec0d8644dce9e196866a070
Public CI run 35506331222 failed because the status-only fast path omitted the core build while IFC verification still ran.

Source commit: 98434eb4ca3c7720eec0d8644dce9e196866a070
@wybaby168
wybaby168 merged commit d01cde9 into main Sep 20, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant