Skip to content

chore(main): release 3.0.1 - #587

Closed
github-actions[bot] wants to merge 2 commits into
mainfrom
release-please--branches--main
Closed

github-actions[bot] wants to merge 2 commits into
mainfrom
release-please--branches--main

Conversation

@github-actions

@github-actions github-actions Bot commented Nov 12, 2026 •

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

3.0.1 (2026-11-13)

Bug Fixes

  • action: keep settings text from issuing workflow commands, and open --summary before the run (#591) (acb5ba4)
  • branches: refuse a non-boolean control at parse, and let a null "off" converge (#599) (346b640)
  • ci: keep a graduation green, and trigger Auto Fix on every generator input (#602) (57a85b3)
  • deps: ship undici without its open advisories in the action bundle (#593) (fc05599)
  • engine: keep a lower layer's rename when a higher layer adds to the label by its new name (#597) (d3b5eca)
  • engine: name a notice's section once, and report what a refused entry left unattempted (#592) (ee702cd)
  • engine: warn of a _layering or _remove that nothing reads (#605) (bc81ce2)
  • environments: name a key GitHub only reports or does not echo on an entry or a nested entry (#604) (a1ede06)
  • github: hide every request of a redacted target, and read an empty repository as unproven (#589) (924cafe)
  • lint: close three gates that passed what they exist to refuse (#600) (347410e)
  • release: let two prunes of the same build tags both succeed (#594) (4a7d4c6)
  • release: search the whole cycle for changelog commits, and restore the lines 3.0.0 lost (#596) (6256d8b)
  • report: keep a clean check clean under the issue channel, and deliver a long report (#598) (9f31e5c)
  • repository: name a contradictory private/visibility pair and a null security_and_analysis in a check-time note (#603) (94e895d)
  • rulesets: refuse a repeated bypass actor at parse instead of crashing the plan (#586) (faf72da)
  • say "re-run" in advice that the CLI prints too (#607) (48f9266)
  • sections: name a key GitHub only reports on a list entry (#612) (08b057b)
  • sections: never plan the owner, hedge a concealed team 404, and advise the grant the writes need (#588) (8dd68e1)
  • sections: send no empty Pages create, and keep the readable interaction limit in a snapshot (#595) (7338300)
  • snapshot: carry a hidden failure's HTTP status, and say "nothing exists" only when it is true (#609) (4adb938)

This PR was generated with Release Please. See documentation.

@github-actions
github-actions Bot requested a review from Vivswan as a code owner November 12, 2026 01:10
@github-actions github-actions Bot added the autorelease: pending release-please release PR awaiting merge/tag label Nov 12, 2026
@github-actions
github-actions Bot force-pushed the release-please--branches--main branch 7 times, most recently from b9f53a7 to 794d720 Compare November 12, 2026 09:50
@Vivswan
Vivswan enabled auto-merge (squash) November 12, 2026 17:54
@Vivswan
Vivswan disabled auto-merge November 12, 2026 18:14
@github-actions
github-actions Bot force-pushed the release-please--branches--main branch from 763fab1 to 68ddc12 Compare November 13, 2026 01:59
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 commits that are not on main, so release-please cannot find the boundary by tag.
@Vivswan Vivswan closed this Nov 13, 2026
@Vivswan
Vivswan deleted the release-please--branches--main branch November 13, 2026 02:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

autorelease: pending release-please release PR awaiting merge/tag

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant