Repository navigation
docs(release): release-notes entries are opt-in — only severe releases need one (#1870 policy revision) - #2057
Merged
Conversation
…s need one (#1870 policy revision)
Contributor
📦 Built Package ArtifactBranch: Option A — Install this exact build (recommended)npm install -g billion-context@0.0.2100-pr.2057.db6ae02This exact version is immutable and reproducible. The rolling Option B — Download artifact
tar xzf billion-context-pr2057.tgz
npm install -g packageInstall instructions are refreshed on each push. |
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Policy change per owner (2026-10-04): 默认不需要写 release-notes 条目,只有严重版本需要写。
Previously (#1873): every stable release required an entry — the dispatch/publish gates aborted when missing. That blocked today's 0.1.183 one-click run at the entry gate.
Now: entries are opt-in severity declarations.
::notice::… shipping silently+ passChanged:
.github/workflows/release-manual.yml— dispatch-time gate inverted (missing → notice+pass).github/workflows/release.yml— pre-publish gate inverted.github/workflows/release-bugfix.yml— sameAGENTS.md§5 — step 4 bullet: "only SEVERE releases need an entry"reference/release.md— step 4, one-click prerequisite, bugfix flow §157 wordingrelease-notes/README.md— opt-in note added to the rulesUntouched: tier semantics (#1977 silent-by-default, only
criticalvisible), the companion-package validation workflow (release-notes.ymlvalidates entries that EXIST), span aggregation insrc/update-notes.ts(holes are fine — spans just cover the entries that exist). 0.1.183's existing entry (#2055) is unaffected.Verified: 3× YAML parse OK; gate logic simulated both ways against the real package (present → validate, absent → notice+pass).