Repository navigation
Fix the invalid Dependabot ecosystem during canonical migration - #87
Conversation
Replace only the invalid empty ecosystem with weekly reviewable GitHub Actions proposals. Preserve every other legacy source file and native lock; no automatic merge or security-alert dismissal.
|
No actionable comments were generated in the recent review. Summary
Merge Risk:
|
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|



Problem
The inherited Dependabot template declares an empty package ecosystem, so GitHub cannot run its version-update configuration. Existing full-SHA consumers and the open Creusot source repair still use this compatibility repository during migration.
Change
Declare the documented
github-actionsecosystem at/on a weekly schedule. Update proposals remain reviewable; there is no automatic merge grant or security-alert dismissal. Native lock changes still require official recovery and caller qualification.The identical configuration repair is included in canonical proven-cicd PR #1. Both currently active repository identities retain valid maintenance configuration during the staged transition. Canonical promotion and legacy maintenance retirement remain explicit later steps.
Validation and write boundary
Reviewed the complete file against GitHub's current Dependabot options reference. No detector, workflow trigger, action pin, native lock or runtime code changes. Hosted checks are the remaining validation; the local execution environment is unavailable.
An automatic review questioned the shared tree ID after history import. The legacy API was read again and independently confirmed main
b931e8e126644516e292601bc644f480a7b2a5a0, tree85a65319b595fbe5e1657c1b0eebb3d142400715, and Dependabot blobe1239092e3965c3d611a997b9e08a7b57f52cda7. Publication then used a single-file contents update with that exact old blob; no broad tree replacement was performed.