Repository navigation
docs(changelog): backfill Unreleased entries for merged PRs without one - #1111
Open
pengfei-threemoonslab wants to merge 2 commits into
Open
pengfei-threemoonslab wants to merge 2 commits into
pengfei-threemoonslab wants to merge 2 commits into
Conversation
Add one line each for the OpenShell stack (#943-#948, including the native trust and evidence schemas #959 published), the application reader increments (#963, #1010, #1016-#1019), the Action's application mode (#1015), the YAML timestamp crash in host config hashing (#1100), the slow test marker (#1006) and, under Security, the AWS path-segment and URL-safe Basic redaction gaps (#1082). Lines are appended at the end of Security and of Changes only; no existing line changes. The Unreleased section, renamed 1.3.0, still passes scripts/release_notes.py: 72,069 characters against 125,000.
… issues The OpenShell feature entries (#943-#948) now precede #962's follow-up fixes to them, the application reader and Action entries sit with the other `diff --application` entries, and the #1082 redaction fix sits beside the redaction entry it extends. Entries for pull requests that reference an issue cite it first, as the section does elsewhere: (#874, #963), (#1001, #1010), (#912, #1016), (#874, #1017), (#911, #1018), (#913, #1019) and (#915, #1015).
This branch has not been deployed
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.
Summary
Release prep for v1.3.0 (no tracking issue); the 2026-11-05 backlog review found these PRs without entries.
CHANGELOG.md's## Unreleasedsection becomes the GitHub Release body, and of the 66 PRs merged sincev1.2.0(7fc61ef4), 16 user- or contributor-visible ones had no line. This adds one line for each: a bold headline sentence, a short clause, and the closing issue's number (or the PR's own number when it closes none), following the existing entries. Outside contributors are not named, as in the existing entries. No existing line is edited. New lines go only at the two agreed anchors, so the five other v1.3.0 prep PRs do not conflict:### Security, after thedocs/trust-model.md lists every processentry: the redaction gaps from fix(privacy): redact AWS path keys and URL-safe Basic credentials #1106.### Changes, after theMove the published-release pins … to v1.2.0entry, in this order: OpenShell (stack order), application readers, the Action, the host-diff crash fix, and theslowmarker.Basiccredential (Security)audit --hostinventories policies registered in.shipgate/openshell.json; host-grants0.7→0.8check,preflight,triggerand configuredverifyroute a policy change;TRIGGER-OPENSHELL-BOUNDARY-CHANGED0.8→0.9verify --openshell-proof-config/--openshell-proof-required;docs/openshell-native-trust-schema.v1.json,docs/openshell-native-evidence-schema.v1.json;SHIP-VERIFY-OPENSHELL-BOUNDARY-EXCEEDED,SHIP-VERIFY-OPENSHELL-PROOF-UNAVAILABLEdiff --applicationfollows a caller-supplied tools listnot_establishedcandidatesnameby its source siteif/elsebuilders and an identified agent's capability fieldagent.clone(...); optionalagent_settingsin application comparison0.4application,application_scope,application_fail_on; outputsapplication_status,application_json,application_markdowndiffno longer crashes on an unquoted YAML timestamp in a host fileslowrun nightly and in release verification, not on pull requestsJudgment calls:
(#942, #945)("Configured committed verification reads selected OpenShell file-link chains from the same verified Git object store…") was added by fix(openshell): preserve expansions and bind selected policy links #962 and describes fix(openshell): preserve expansions and bind selected policy links #962's link-chain snapshot. It does not describe feat(openshell): bind selected policy inputs to verifier currency #951's change: each comparison reads the selected policies from its own base and head tree, and the receipt binds their bytes, link targets and missing inputs, Git-ignored files included.### Changes, not Security. Host diff crashes on YAML timestamps resolved as datetime #1100 reports a crash (diffexits 1); its impact section says it "does not demonstrate a permissions bypass".slowpytest marker inpyproject.tomland aCONTRIBUTING.mdparagraph telling contributors when to mark a test and how to reproduce what a pull request runs. That is contributor-visible, like build(deps): group Dependabot version updates per ecosystem (#501) #978's Dependabot line. The sharding itself is not mentioned.docs/changelog/1.3.0.md, is the owner's call.Deliberately not added
These merged PRs still have no entry. Each has a one-phrase reason so the owner can decide:
pyproject.tomluntouched, no runtime dependency or floor moves.hatchling>=1.32.4) and dev and release-toolchain locks; no runtime dependency moved. Itsrfc3161-client1.0.9 fix for GHSA-87gx-4x38-2j9q is in the release signing toolchain (sigstore sign/verify), not in the installed package. The owner may want a Packaging line.actions/setup-python7.0.0 → 7.1.0 in the workflows and inaction.yml's composite setup step; no Action input or output changes. The owner may want a line, sinceaction.ymlis a distribution surface.actions/download-artifact8.0.1 → 8.0.2, workflows only.conftest.pykeeps fixture scans out of the runner's step summary and outputs.verify_dependency_lock.pycalls an extras-qualified exact pin "neither an exact pin nor a direct URL" #500), fix: preserve distribution identity for extras-qualified lock pins #1009: maintainer lock-verification tooling.scripts/verify_dependency_lock.pynow parses extras-qualified pins; no committed lock holds one, andCONTRIBUTING.mdstill tells maintainers to check for them.mainat0e58e6ff, plus asummarize.pyanswer_idfix. It is superseded by the release-time Q2 measurement the runbook requires (§ Cutting the release, step 1).Covered without a ref of their own, so not added: #1088 (the
verifier 0.21 and agent-boundary-result v3 … capability row closedentry), #987 (Two credential shapes are no longer published), #919 ((#778)) and #962 ((#942),(#942, #945)).Type
Authorship
Acceptance criteria
gh pr view N --json title,body,files, plusgit showof the docs,action.yml, CLI and check-catalog hunks). Every flag, input, output, check ID, trigger ID and schema file named was checked against the merged source:verify --openshell-proof-config/--openshell-proof-requiredincli/verify/command.py, the Action inputs and outputs inaction.yml,TRIGGER-OPENSHELL-BOUNDARY-CHANGEDindocs/triggers.json, and the twoSHIP-VERIFY-OPENSHELL-*checks indocs/checks/verify.yaml.docs/openshell-native-trust-schema.v1.jsonanddocs/openshell-native-evidence-schema.v1.json(and their.well-knownkeys). Both are linked from the OpenShell: accept optional native containment evidence bound to a trusted boundary #948 line.git diff origin/main -U0has exactly two hunks,@@ -11,0 +12 @@and@@ -54,0 +56,15 @@.git diff --numstatis16 0 CHANGELOG.md.scripts/release_notes.py --changelog <temp copy with line 3 renamed to ## 1.3.0> --tag v1.3.0exits 0 before and after. The section was 65,257 characters before and is 72,069 after (+6,812), againstMAX_BODY_CHARACTERS = 125,000.Verification
python scripts/release_notes.py --changelog <copy of origin/main's CHANGELOG, ## 1.3.0> --tag v1.3.0python scripts/release_notes.py --changelog <copy of this branch's CHANGELOG, ## 1.3.0> --tag v1.3.0python -m pytest tests/test_distribution_surface_parity.py tests/test_release_advisory_pipeline.py tests/test_release_pipeline.py tests/test_unread_changed_inputs.py -n 4(every test file that namesCHANGELOG)python -m ruff check .Release-readiness notes
docs/checks.md(none changed; the twoSHIP-VERIFY-OPENSHELL-*IDs named here were documented by feat(openshell): bind optional native containment to trusted inputs #959)STABILITY.md(no schema change)The Unreleased section is now 72,069 characters. The other v1.3.0 prep PRs add more, and at cut time the long prose moves to
docs/changelog/1.3.0.md(runbook § Cutting the release, step 1).Out of scope
(#1088)or(#987)to their unreferenced entries, and reordering the fix(openshell): preserve expansions and bind selected policy links #962 OpenShell entries.docs/changelog/1.3.0.mdrecord and theQ2: n/49 development, m/≥30 holdoutline.🤖 Generated with Claude Code