[eseiler]

Adds .github/workflows/dependency_submission.yml, the same workflow as in seqan/hibf#353: on every push to main that changes cmake/package-lock.cmake or cmake/CPM.cmake (and on manual dispatch), the CPM packages and the CPM version go to the dependency graph via seqan/actions/cpm_dependency_submission (seqan/actions#190).

• Typical trigger: merging the PR of cron_cpm.yml. The snapshot belongs to the merge commit, so the graph matches main.
• Uses GITHUB_TOKEN with contents: write for this job only; no App token or secrets.
• A newer push cancels an older run that has not finished, because only the latest snapshot counts.
• Problems (e.g. a disabled dependency graph) are warning annotations, not failures.

Merging this PR does not change the package lock, so it does not submit anything. To submit the current main, run the workflow once by hand (Actions → Dependency Submission → Run workflow).

Checked locally with the action from main of seqan/actions: the package lock gives hibf, seqan3, sharg, googletest, robin-hood and use_ccache, plus CPM 0.43.2, with no warnings.

🤖 Generated with Claude Code

[seqan-pr-bot]

Documentation preview available at https://seqan.github.io/docs-preview/seqan/needle/271/

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 84.05%. Comparing base (59e7436) to head (f267f00).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #271   +/-   ##
=======================================
  Coverage   84.05%   84.05%           
=======================================
  Files          19       19           
  Lines        1091     1091           
  Branches      134      134           
=======================================
  Hits          917      917           
  Misses        174      174           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.