Skip to content

docs: record what branch protection now enforces, and cairn the 0.2.0 release - #28

Merged
aidanmoller merged 1 commit into
mainfrom
docs-protection-now-enforced
Sep 14, 2026
Merged

aidanmoller merged 1 commit into
mainfrom
docs-protection-now-enforced

Conversation

@max578

@max578 max578 commented Sep 10, 2026

Copy link
Copy Markdown
Collaborator

Protection was enabled 2026-09-10 and read back from the host API. The process record and contributing guide described it as intended and unverified, which understates it now. Adds the T3 cairn for the 0.2.0 release.

… release

Protection was enabled on main on 2026-09-10 and read back from the host API:
pull request required, one approving code-owner review, ten required checks, no
force push or deletion, administrators may bypass. The process record and the
contributing guide described it as intended and unverified, which was accurate
while it was off and understates it now.

The release itself had no decision record. The cairn carries the version call
(0.2.0 rather than 0.1.1, because three items stop working calls from working),
the three rejected alternatives including removing the retired T argument as its
own notice promised, and the forward cost -- a deprecation with no scheduled
removal, and two documented limitations that ship with the release.
@max578
max578 requested a review from aidanmoller as a code owner September 10, 2026 03:12
@aidanmoller
aidanmoller merged commit dbec5a1 into main Sep 14, 2026
10 checks passed
@aidanmoller
aidanmoller deleted the docs-protection-now-enforced branch September 14, 2026 03:53
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.

2 participants