惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

人人都是产品经理
人人都是产品经理
Stack Overflow Blog
Stack Overflow Blog
S
SegmentFault 最新的问题
博客园 - 司徒正美
aimingoo的专栏
aimingoo的专栏
U
Unit 42
GbyAI
GbyAI
B
Blog RSS Feed
博客园 - Franky
L
LangChain Blog
Hugging Face - Blog
Hugging Face - Blog
美团技术团队
The GitHub Blog
The GitHub Blog
Y
Y Combinator Blog
云风的 BLOG
云风的 BLOG
H
Hackread – Cybersecurity News, Data Breaches, AI and More
博客园 - 三生石上(FineUI控件)
Microsoft Azure Blog
Microsoft Azure Blog
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
G
Google Developers Blog
Last Week in AI
Last Week in AI
阮一峰的网络日志
阮一峰的网络日志
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
Apple Machine Learning Research
Apple Machine Learning Research

Recent Commits to openclaw:main

test: merge chat side-result checks · openclaw/openclaw@ddd2c2a test: merge cron history checks · openclaw/openclaw@f7eb746 test: merge responsive navigation shell checks · openclaw/openclaw@c2e4b47 docs(changelog): add codex oauth fixes · openclaw/openclaw@628e6cd test: merge navigation routing cases · openclaw/openclaw@5d8cecb Tests: mock channel registry bundled fallback · openclaw/openclaw@2b08233 Secrets: avoid broad web search discovery for single plugin config · openclaw/openclaw@a464f59 test: merge config view browser checks · openclaw/openclaw@20cf511 fix(status): align oauth health with runtime · openclaw/openclaw@eed7116 feat: add macOS screen snapshots for monitor preview (#67954) thanks … · openclaw/openclaw@f377db1 fix: report shared auth scopes in hello-ok (#67810) thanks @BunsDev · openclaw/openclaw@0b6c39b Auto-reply: avoid eager bundled route fallback · openclaw/openclaw@3ea1bf4 Tests: narrow session binding contract setup · openclaw/openclaw@54e4e16 fix(macOS): enable undo/redo in webchat composer text input (#34962) · openclaw/openclaw@00951dc Tests: speed up channel setup promotion · openclaw/openclaw@82b529a Docs: refresh agent instructions · openclaw/openclaw@5775fe2 fix(auth): serialize OAuth refresh across agents to fix #26322 (#67876) · openclaw/openclaw@8e79080 test: allow ollama public surface boundary test · openclaw/openclaw@7d4f1a6 Docs: add test performance guardrails · openclaw/openclaw@89706d3 Tests: restore context-engine usage proof · openclaw/openclaw@e4c4f95 Tests: slim context engine runtime coverage · openclaw/openclaw@74c198f ci: retry failed custom checkouts · openclaw/openclaw@0ee5baf test: trim duplicate provider auth onboarding cases · openclaw/openclaw@1ffc02e matrix: fix sessions_spawn --thread subagent session spawning (#67643) · openclaw/openclaw@1ce2596 test: reduce auth choice fixture churn · openclaw/openclaw@857b9cd test: mock health status config boundaries · openclaw/openclaw@9d5ab4a test: mock onboard config io boundary · openclaw/openclaw@299694d test: mock legacy state plugin boundaries · openclaw/openclaw@2713089 test: mock channel install boundaries · openclaw/openclaw@b945248 test: mock doctor preview channel boundaries · openclaw/openclaw@b1a3ad4
docs(release): require stable main closeout · openclaw/op...
vincentkoc · 2026-06-17 · via Recent Commits to openclaw:main
Original file line numberDiff line numberDiff line change

@@ -100,6 +100,26 @@ Use this skill for release and publish-time workflow. Load `$release-private` if

100100

- `dev`: moving head on `main`

101101

- When using a beta Git tag, publish npm with the matching beta version suffix so the plain version is not consumed or blocked

102102
103+

## Close stable releases on main

104+
105+

Stable publication is not complete until `main` carries the actual shipped release state.

106+
107+

1. Start from fresh latest `main`. Audit `release/YYYY.M.PATCH` against it and

108+

forward-port real fixes that are absent from `main`. Do not blindly merge

109+

release-only compatibility, test, or validation adapters into newer `main`.

110+

2. Set `main` to the shipped stable version, not a speculative next train. Run

111+

`pnpm release:prep` after the root version change, then

112+

`pnpm deps:shrinkwrap:generate`.

113+

3. Make `CHANGELOG.md`'s `## YYYY.M.PATCH` section on `main` exactly match the

114+

tagged release branch. Include the stable `appcast.xml` update when the mac

115+

release published one.

116+

4. Do not add `YYYY.M.PATCH+1`, a beta version, or an empty future changelog

117+

section to `main` until the operator explicitly starts that release train.

118+

5. Run `pnpm release:generated:check`, `pnpm deps:shrinkwrap:check`, and

119+

`OPENCLAW_TESTBOX=1 pnpm check:changed`. Push, then verify `origin/main`

120+

contains the shipped version and changelog before calling the stable release

121+

done.

122+
103123

## Handle versions and release files consistently

104124
105125

- Version locations include:

@@ -778,13 +798,13 @@ node --import tsx scripts/openclaw-npm-postpublish-verify.ts <published-version>

778798

and `.dSYM.zip` artifacts to the existing GitHub release in

779799

`openclaw/openclaw`.

780800

32. For stable releases, download `macos-appcast-<tag>` from the successful

781-

private mac run, update `appcast.xml` on `main`, and verify the feed. Merge

782-

or cherry-pick release branch changes back to `main` after stable succeeds.

801+

private mac run, update `appcast.xml` on `main`, verify the feed, then

802+

complete the **Close stable releases on main** gate.

783803

33. For beta releases, publish the mac assets only when intentionally requested;

784804

expect no shared production

785805

`appcast.xml` artifact and do not update the shared production feed unless a

786806

separate beta feed exists.

787-

34. After publish, verify npm and the attached release artifacts.

807+

34. After stable main closeout, verify npm and the attached release artifacts.

788808
789809

## GHSA advisory work

790810
Original file line numberDiff line numberDiff line change

@@ -155,7 +155,29 @@ the maintainer-only release runbook.

155155

11. After publish, run the npm post-publish verifier, optional standalone

156156

published-npm Telegram E2E when you need post-publish channel proof,

157157

dist-tag promotion when needed, verify the generated GitHub release page,

158-

and run the release announcement steps.

158+

run the release announcement steps, then complete [Stable main

159+

closeout](#stable-main-closeout) before calling a stable release finished.

160+
161+

## Stable main closeout

162+
163+

Stable publication is not complete until `main` carries the actual shipped

164+

release state.

165+
166+

1. Start from fresh latest `main`. Audit `release/YYYY.M.PATCH` against it and

167+

forward-port real fixes that are absent from `main`. Do not blindly merge

168+

release-only compatibility, test, or validation adapters into newer `main`.

169+

2. Set `main` to the shipped stable version, not a speculative next train. Run

170+

`pnpm release:prep` after the root version change, then

171+

`pnpm deps:shrinkwrap:generate`.

172+

3. Make `CHANGELOG.md`'s `## YYYY.M.PATCH` section on `main` exactly match the

173+

tagged release branch. Include the stable `appcast.xml` update when the mac

174+

release published one.

175+

4. Do not add `YYYY.M.PATCH+1`, a beta version, or an empty future changelog

176+

section to `main` until the operator explicitly starts that release train.

177+

5. Run `pnpm release:generated:check`, `pnpm deps:shrinkwrap:check`, and

178+

`OPENCLAW_TESTBOX=1 pnpm check:changed`. Push, then verify `origin/main`

179+

contains the shipped version and changelog before calling the stable release

180+

done.

159181
160182

## Release preflight

161183