Filed by the skills seat (session_01ApyDuQY2fkunMCqXiqvBhR) on the maintainer's direct instruction. Sister card of objectstack-ai/objectstack#10850 — same ruling, this repo's own release machinery.
Provenance (maintainer, PM chat 2026-08-21, verbatim, untranslated)
我每周才发一次版本,changeset 每个pr 都跑有必要吗
After the assessment (keep per-PR changeset validation; cut the per-merge Version-Packages refresh):
立卡吧,version 工作流改成发版前手动触发
包括 objectui 仓库
What to change
If this repo's changesets workflow creates/refreshes a "Version Packages" PR on every push to the default branch, change that trigger to workflow_dispatch only — run manually right before a release. Releases here are weekly; a per-merge refresh burns a CI run per merge for a PR nobody consumes until release day.
- Locate the actual workflow first and measure its current trigger — do not assume it mirrors the objectstack repo's shape. If this repo has no per-merge version-PR refresh at all,
premise_still_valid: false with the measurement is the correct outcome — say so on this card and close it, don't invent an edit.
- The publish/release half stays exactly as it is: releases are human-only.
Explicitly NOT in scope (ruled to keep)
Per-PR changeset validation (each PR carrying a well-formed changeset, and whatever gates check that here) stays on every PR. The ruling cuts only the per-merge version-PR refresh.
Acceptance criterion (one line, executable)
After landing: the version-PR job's on: triggers contain workflow_dispatch and no push-to-default-branch path, and a test merge starts zero Version-Packages refresh runs (verify in the Actions run list).
Filed by the skills seat (
session_01ApyDuQY2fkunMCqXiqvBhR) on the maintainer's direct instruction. Sister card of objectstack-ai/objectstack#10850 — same ruling, this repo's own release machinery.Provenance (maintainer, PM chat 2026-08-21, verbatim, untranslated)
After the assessment (keep per-PR changeset validation; cut the per-merge Version-Packages refresh):
What to change
If this repo's changesets workflow creates/refreshes a "Version Packages" PR on every push to the default branch, change that trigger to
workflow_dispatchonly — run manually right before a release. Releases here are weekly; a per-merge refresh burns a CI run per merge for a PR nobody consumes until release day.premise_still_valid: falsewith the measurement is the correct outcome — say so on this card and close it, don't invent an edit.Explicitly NOT in scope (ruled to keep)
Per-PR changeset validation (each PR carrying a well-formed changeset, and whatever gates check that here) stays on every PR. The ruling cuts only the per-merge version-PR refresh.
Acceptance criterion (one line, executable)
After landing: the version-PR job's
on:triggers containworkflow_dispatchand no push-to-default-branch path, and a test merge starts zero Version-Packages refresh runs (verify in the Actions run list).