Skip to content

chore(main): release 2.0.1 - #51

Merged
Vivswan merged 2 commits into
mainfrom
release-please--branches--main
Aug 14, 2026
Merged

chore(main): release 2.0.1#51
Vivswan merged 2 commits into
mainfrom
release-please--branches--main

Conversation

@github-actions

@github-actions github-actions Bot commented Aug 14, 2026

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

2.0.1 (2026-08-14)

Bug Fixes

  • apply review fixes to the docs and tooling sweep (73b6b4a)
  • apply review fixes to the harness audit batch (ceb9f46)
  • apply review fixes to the src-side audit batch (b9de617)
  • attest build provenance and attach the sigstore bundle to releases (b5db672)
  • centralize the token-leak sweep in the runner (7dcc225)
  • classify rate limits structurally on every path (65f97a2)
  • correct mock identity minting and the pages resurrect bug (9152a91)
  • cover every faultable section in the fuzz fault battery (e41aa99)
  • derive owner-kind sensitivity from the section declaration (0181f01)
  • discover schema-corpus scenarios across all scenario roots (d34d031)
  • harden the CI tooling (6fb2603)
  • keep spec-pinned gaps out of automatic graduation (ae278c9)
  • parse live bodies through parseLive in the seven asserting sections (56ca3e4)
  • reject required-sections entries excluded by the sections allowlist (c1fc169)
  • single-tag releases - version tags live only on packaged commits (2372661)
  • size the harness kill cap for the directed fuzz battery (8543af8)
  • strengthen the remaining per-section representations (3fc0f85)

This PR was generated with Release Please. See documentation.

@github-actions github-actions Bot added the autorelease: pending release-please release PR awaiting merge/tag label Aug 14, 2026
@github-actions
github-actions Bot requested a review from Vivswan as a code owner August 14, 2026 09:15
@Vivswan
Vivswan force-pushed the main branch 2 times, most recently from 3f43d11 to 2372661 Compare August 14, 2026 09:24
@github-actions
github-actions Bot force-pushed the release-please--branches--main branch from 348f3fa to ed7a67a Compare August 14, 2026 09:31
last-release-sha records the merge parent so the squash merge itself lands the next cycle's boundary on main: version tags live on packaged children that are not on main, so release-please cannot find the boundary by tag.
@Vivswan
Vivswan merged commit ac6909f into main Aug 14, 2026
@Vivswan
Vivswan deleted the release-please--branches--main branch August 14, 2026 09:38
@Vivswan Vivswan added autorelease: tagged release-please release PR has been tagged and removed autorelease: pending release-please release PR awaiting merge/tag labels Aug 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

autorelease: tagged release-please release PR has been tagged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant