🚀🧑‍💻 - 3.6.0 - release v3.6.0 guided organization setup and reusable runners #574

Release Type

Minor

Release Version

3.6.0

Changelog

• Reuse existing organization Variables and Secrets during setup, and configure selected repositories in one guided batch session ([#538] ✨ - feat reuse organization configuration and set up selected repositories in one guided session #546).
• Discover and select reusable self-hosted runner profiles, preserve native source workflows, and review installation parity ([#556] ✨ - feat select reusable runner profiles in setup and reconcile source workflow parity #563).
• Accept the literal runner-group routes generated by setup in workflow validation ([#570] 🐛 - bugfix setup generated runner groups fail source workflow validation #571, fixes 🐛🧑‍💻 - bugfix setup generated runner groups fail source workflow validation #570).
• Exclude disposable setup permission-probe branches from owned push automation, including source workflow upgrades with LF and CRLF inputs ([#569] 🐛 - bugfix permission probes trigger normal automation on temporary branches #572, fixes 🐛🧑‍💻 - bugfix permission probes trigger normal automation on temporary branches #569).

Additional Context

The maintainer explicitly authorized publishing v3.6.0 through the normal release flow after CI, Codecov and RepoWise passed for the included pull requests.

Reviewed development snapshot: 41705056436cd58087cadbaa021e30a6fa2f4b8c.
Previous production release: v3.5.6 (5b0dd52f2af98fc260bf4b3859cc581e3e833ac8).
Comparison: v3.5.6...4170505

The real native permission-probe regression passed on the reviewed development snapshot: no workflow runs were admitted and the owned temporary ref was removed. Publication is needed to repeat the complete source and platform setup Apply against the updated default branch.

Use the Action-managed release branch, promotion PR, immutable accepted-production tag, npm/GitHub publication and development reconciliation. Preserve required checks and repository protections. Dependency vulnerability work and the separate ruleset-field follow-up #573 are outside this release.