Repository navigation
ci: keep only the Dependabot ecosystems this repo has manifests for - #19
Conversation
cargo, mix, npm and pip entries have no Cargo.toml, mix.exs, package.json or requirements.txt behind them, so each weekly run failed (8 of the last 10 dynamic runs: pip, npm_and_yarn, hex). Drop them and add the julia ecosystem for Project.toml. The github-actions entry and its codeql-action hold stay. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0136P7ZoXueEiNpcpgdeBR67
|
No actionable comments were generated in the recent review. Summary
Merge Risk:
|
|



Summary
dependabot.ymlstill carries the template'scargo,mix,npmandpipentries. This repo has noCargo.toml,mix.exs,package.jsonorrequirements.txt, so each weekly run for them fails: 8 of the last 10 dynamic Dependabot runs failed (pip in /.,npm_and_yarn in /.,hex in /.). It has no entry for the one manifest it does have,Project.toml.Changes
.github/dependabot.yml: remove cargo, mix, npm, pip; add thejuliaecosystem forProject.toml; keepgithub-actionsand its codeql-action hold unchanged. The mislabelled "Rust/Cargo" comment that sat above the codeqlignoreis gone with the entry it described.CHANGELOG.adoc: Fixed entry.This is the manual equivalent of the mint-time
prune-dependabot-ecosystemsstep, which evidently never ran for this repository.tests/workflows/mint_cleanup_test.shuses its own fixture, so it is unaffected.Testing
yqparses the file. I cannot run Dependabot from here, so the real test is the next scheduled run: the three failing ecosystems no longer exist andjuliahas a manifest.test/ext/Project.toml(added in #12) would need its owndirectoriesentry then; left for that PR.Generated by Claude Code