chore: refresh mise-php admin state snapshot - #25
Conversation
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_f5bd9491-a1de-43e1-b4b8-7d61c01418a2) |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe administrative-state snapshot updates environment metadata, adds the ChangesAdministrative state snapshot
Estimated code review effort: 1 (Trivial) | ~3 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Recaptures mise-php's GitHub configuration now that the autorelease environment rename and the
MAINTENANCE_OWNERremoval have landed.What actually moved, and why:
php-autorelease-publishenvironment's ID, node ID, protection rule ID and timestamps changed. GitHub environments are configuration rather than repository files, so the source rename could not move them. The live environment was still namedphp-maintenance-release; it was replaced with a freshphp-autorelease-publishcarrying identical protection (can_admins_bypass: false,protected_branches: true, one branch policy rule). The old one was confirmed to hold zero deployments, secrets and variables before deletion.php-autorelease-publishwhile GitHub still had the old name. The file was recording the intended state; it now records the real one.repositorychanged fromBigpixelrocket/mise-phptobigpixelrocket/mise-php. The script records the--repoargument verbatim rather than the canonicalfull_nameit already fetches. The lowercase form is whatdocs/repository-settings.mddocuments, so future captures reproduce it.autoreleaselabel moved to alphabetical position. The script stores label names in API order without sorting; the set of twelve names is unchanged.MAINTENANCE_OWNERdoes not appear as a removal because the previous snapshot already listed onlyAUTORELEASE_OWNER.No secret values are present.
secretNamesholds bare names only.Summary by CodeRabbit