docs(adr): record the release-notes and attribution gates as 0050 and 0051 #722
No reviewers
Labels
No labels
breaking
bug
documentation
enhancement
epic
good first issue
help wanted
refactoring
resolution/duplicate
resolution/invalid
resolution/wontfix
security
severity/critical
severity/high
severity/low
severity/medium
status/abandoned
status/blocked
status/needs-decision
status/needs-info
status/needs-verification
testing
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
sixfold-space/madtea!722
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "docs/adr-breaking-notes-and-attribution"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
I add two proposed decision records.
0050 - the release notes surface every breaking change: a Breaking changes changelog group, a gate check that requires the
!subject marker on a public-API break, and a release preflight that requires a migration section. Tracked in #719.0051 - third-party attribution is verified at the gate: the attribution check reads every Go embed directive and requires each target to be first-party or declared, and the generator writes and verifies a vendored-attribution section in the NOTICE. Tracked in #720.
Both stay proposed until the work lands and the issue closes. #675 depends on #719.