Skip to content

chore(deps): bump codecov/codecov-action from 4 to 7 - #81

Open
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/github_actions/codecov/codecov-action-7
Open

chore(deps): bump codecov/codecov-action from 4 to 7#81
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/github_actions/codecov/codecov-action-7

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 31, 2026

Copy link
Copy Markdown

Bumps codecov/codecov-action from 4 to 7.

Release notes

Sourced from codecov/codecov-action's releases.

v7.0.0

⚠️ Due to migration issues with keybase, we are unable to update our keys under the codecovsecurity account. We have deleted the account and are using codecovsecops with the original gpg key

What's Changed

Full Changelog: codecov/codecov-action@v6.0.1...v7.0.0

v6.0.2

This is a copy of the v7.0.0 release to make updates easier

What's Changed

Full Changelog: codecov/codecov-action@v6.0.1...v6.0.2

v6.0.1

What's Changed

Full Changelog: codecov/codecov-action@v6.0.0...v6.0.1

v6.0.0

⚠️ This version introduces support for node24 which make cause breaking changes for systems that do not currently support node24. ⚠️

What's Changed

Full Changelog: codecov/codecov-action@v5.5.4...v6.0.0

v5.5.5

This release only contains the keybase.io change as described here.

Full Changelog: codecov/codecov-action@v5.5.4...v5.5.5

v5.5.4

This is a mirror of v5.5.2. v6 will be released which requires node24

What's Changed

... (truncated)

Changelog

Sourced from codecov/codecov-action's changelog.

v5.5.2

What's Changed

Full Changelog: https://github.com/codecov/codecov-action/compare/v5.5.1..v5.5.2

v5.5.1

What's Changed

Full Changelog: https://github.com/codecov/codecov-action/compare/v5.5.0..v5.5.1

v5.5.0

What's Changed

Full Changelog: https://github.com/codecov/codecov-action/compare/v5.4.3..v5.5.0

v5.4.3

What's Changed

Full Changelog: https://github.com/codecov/codecov-action/compare/v5.4.2..v5.4.3

v5.4.2

... (truncated)

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [codecov/codecov-action](https://github.com/codecov/codecov-action) from 4 to 7.
- [Release notes](https://github.com/codecov/codecov-action/releases)
- [Changelog](https://github.com/codecov/codecov-action/blob/main/CHANGELOG.md)
- [Commits](codecov/codecov-action@v4...v7)

---
updated-dependencies:
- dependency-name: codecov/codecov-action
  dependency-version: '7'
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot @github

dependabot Bot commented on behalf of github Aug 31, 2026

Copy link
Copy Markdown
Author

Labels

The following labels could not be found: github-actions. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

@dependabot
dependabot Bot requested a review from srpatcha as a code owner August 31, 2026 23:16
@dependabot dependabot Bot added dependencies Dependency updates major Breaking API or behaviour change labels Aug 31, 2026
@dependabot
dependabot Bot requested a review from hshanmug12 as a code owner August 31, 2026 23:16
@dependabot dependabot Bot added dependencies Dependency updates major Breaking API or behaviour change labels Aug 31, 2026

@srpatcha srpatcha left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review — eDB#81 "chore(deps): bump codecov/codecov-action from 4 to 7"

head: ee5358c author: app/dependabot ci: the build/test workflow never ran — the only reported checks are Analyze (Python), CodeQL and assign, all pass

Verdict: The bump clears the v4→v5 rewrite without needing an edit, because ci.yml:60 already uses the plural files: that v5 renamed file: to, and flags: is unchanged across the range. It also picks up a real security fix (VULN-1652, template injection in run: steps, fixed in v6.0.1). So: correct as written. But CI — eDB did not run on this PR, the single line it changes is the last step of the job that never completes, and this repo has not had a green coverage upload since at least May — so the change is entirely unverified, and the step it touches has not executed in months.

Findings

# Severity File:line Finding Recommended fix
1 High .github/workflows/ci.yml (at base 5e436bd6), lines 6-7 CI — eDB never triggered on this PR, and its absence reads as success. At this PR's base commit 5e436bd63d53b14b5b75f5a0cc5e816642691388 the workflow carried pull_request: branches: [main], while the PR targets master — the trigger silently did not match. The Test (Python …) matrix is absent, not failing, so the overall green tick is composed entirely of CodeQL and assign. master has since been fixed (PR #70, 6d53641, now branches: [master, main]), but this PR branched before that. Same shape as the required_status_checks addendum of 2026-09-03 recorded for eDB#71/#72/#73; #80 and #81 share the same stale base. Rebase onto current master. Nothing else gives this PR evidence, and dependabot will not do it — see finding 3. Needs a human rebase and force-push to the dependabot branch, or close-and-reopen by hand.
2 High .github/workflows/ci.yml:33, :58, matrix at :16-18 The step this PR changes has not executed successfully in months, and would not have executed even if CI had run. codecov-action is the last step of the test job (:58). The job dies at :33 on pip install -r requirements.txtno requirements.txt exists on master — so control never reaches :58. Run 33472965435 (master, 2026-09-01): six of nine matrix legs failure in 9-40s, three legs queued from 05:16:30Z to exactly 2026-09-02T05:16:30Z then cancelled, which is the 24h0m2s on the last three master runs. Every CI — eDB run since 2026-05 concluded failure. Whatever coverage badge eDB is publishing, no upload from this workflow is behind it. The requirements.txt half is already fixed in open PR #82 (autofix/ci-install-project-deps) — do not open a duplicate; land #82 first. The 24h queue starvation is not covered by #82: add timeout-minutes to the test job so a leg that cannot get a runner fails in minutes, not a day.
3 Medium Repository state Dependabot was removed from this repo after this PR was opened. .github/dependabot.yml does not exist on origin/master — deleted by #68, "chore(ci): remove Dependabot, add Claude + Copilot code review", merged 2026-09-01; this PR was opened 2026-08-31. Nothing will rebase it (finding 1), nothing will close it if superseded, and its own "The following labels could not be found: github-actions" comment is now permanently unactionable. Eleven dependabot PRs (#71-#81) are orphaned this way. Triage #71-#81 in one deliberate pass: rebase and merge what you want, close the rest citing #68. The org-wide gap is already filed as the proposal of 2026-09-03, "Dependabot was disabled org-wide, and no section of the design owns dependency-vulnerability monitoring".
4 Low .github/workflows/ci.yml:58-61 The upload is unauthenticated and non-failing, and this bump makes both matter slightly more. There is no token: input, so uploads rely on tokenless public-repo credit, which codecov rate-limits; and there is no fail_ci_if_error, so an upload that silently does not happen looks identical to one that did. flags: edb-py${{ matrix.python-version }} collapses the three OS legs of the 3×3 matrix into three flags, so ubuntu-22.04, macos-13 and windows-2022 coverage for the same Python version all land on one flag and overwrite rather than merge. All pre-existing, none introduced by this diff. After #82 lands and the job can actually reach :58: add token: ${{ secrets.CODECOV_TOKEN }}, and include matrix.os in the flag (edb-${{ matrix.os }}-py${{ matrix.python-version }}). Consider fail_ci_if_error: true only once the pipeline is otherwise green — turning it on against a red pipeline just adds noise.
5 Low Repo settings — master branch protection gh api repos/embeddedos-org/eDB/branches/master/protectionrequired_status_checks: null, required_approving_review_count: 1. Nothing gates merge on a check. Low here because the effect is already covered by finding 1 and this PR is BLOCKED/REVIEW_REQUIRED, so a human must still approve. Already filed as the §28.3 proposal of 2026-09-03 and its addendum, which names eDB. Require CI — eDB once #82 makes it capable of going green.

Not a finding, recorded as checked — this is why the bump needs no edit. The v4→v5 rewrite moved the action onto the Codecov CLI and renamed the singular file: input to plural files:. ci.yml:60 already uses files: coverage.xml, so the one rename that breaks most v4→v5 bumps does not apply here. flags: is unchanged across v4-v7. The rest of the range: v6.0.0 moves to Node 24 (Actions Runner ≥ 2.327.1, satisfied by all three hosted runner images in the matrix); v6.0.1 fixes VULN-1652, template injection in run: steps — a security fix worth having; v6.0.2/v7.0.0 are the same code, re-released because the codecovsecurity keybase account was deleted and signing moved to codecovsecops. No input used by this workflow was renamed or removed.

Architecture conformance

Conforms. Infrastructure-tier change (master design §21, "Infrastructure — .github, website, docs, CI templates") to a Tier-3 Advanced repository (§21, "eAI, eNI, eDB"). No source file, #include, link line or manifest entry, so §5.1 dependency direction is untouched; no public API or ABI moves, so §23.2's contracts are unaffected. Findings 1-2 bear on §28's evidence policy — a coverage step that has not run since May cannot support any Implemented or Validated claim resting on test coverage — but that gap is already filed as §28.2 (2026-09-02), §28.3 (2026-09-03) and the required_status_checks addendum (2026-09-03), which already names eDB and this exact branches: [main] trigger mismatch. No new proposal appended — this PR produced no gap that is not already written down.

Proposed changes

Order matters, and this PR is last:

  1. Land #82 so ci.yml:33 stops failing on a file that does not exist, and the test job can reach :58 for the first time in months (finding 2).
  2. Add timeout-minutes to the test job (finding 2, second half).
  3. Rebase this PR onto master so CI — eDB triggers (finding 1). Only then does merging it mean anything.
  4. Separately, add the codecov token and fix the flag to include matrix.os (finding 4), and triage the eleven orphaned dependabot PRs (finding 3).

Verification I ran

  • gh pr view 81 --json baseRefOid5e436bd6…; git show 5e436bd6:.github/workflows/ci.ymlpull_request: branches: [main] against a PR targeting master. Direct evidence for finding 1.
  • git show origin/master:.github/workflows/ci.yml:33 pip install -r requirements.txt; :58-61 the codecov step with files: coverage.xml and flags: edb-py…; matrix at :16-18 is 3 Python × 3 OS. git show origin/master:requirements.txt → does not exist.
  • gh run list --workflow=ci.yml --limit 8 → every run since 2026-05 concluded failure; last three master runs 24h0m2s each.
  • gh run view 33472965435 --json jobs → six legs failure (9-40s), three legs cancelled after exactly 24h queued. Evidence for finding 2.
  • git show origin/master:.github/dependabot.ymlfatal: … exists on disk, but not in 'origin/master'; #68 "chore(ci): remove Dependabot" merged 2026-09-01. Evidence for finding 3.
  • gh pr list#82 autofix/ci-install-project-deps is open and already covers the requirements.txt defect, which is why I opened no fix PR for it.
  • gh api repos/embeddedos-org/eDB/branches/master/protectionrequired_status_checks: null, reviews 1.
  • Read the v5.5.x/v6.0.0/v6.0.1/v6.0.2/v7.0.0 release notes from the PR body for the compatibility statement above.

Not checked

  • Nothing was executed. No workflow ran with codecov-action@v7, no coverage was uploaded, and none can be until findings 1 and 2 are addressed. The compatibility conclusion rests on comparing the documented input changes against the actual with: block — sound for that question, not a substitute for a run.
  • I did not check whether a CODECOV_TOKEN secret exists in this repository, only that the workflow does not reference one. Finding 4's token recommendation assumes one would need to be added; that assumption is unverified.
  • I did not open a job log for the three starved matrix legs, so I have not confirmed which OS legs they are — name: Test (Python ${{ matrix.python-version }}) at ci.yml:13 omits matrix.os, so all nine legs report under three names. macos-13/windows-2022 starvation is consistent with the 24h queued duration but is inferred, not observed.
  • I did not verify what the eDB README currently claims about coverage, so I make no statement about whether a published badge is stale — only that this workflow has uploaded nothing.
  • The local eDB checkout has diverged from origin/master (1 ahead, 3 behind) with a clean tree; every file above was read from origin/master or from the PR base via git show. I did not stash, reset, rebase or check out anything.

Automated architecture review of ee5358c8dee8 — scheduled, model claude-opus-5, checked against the EmbeddedOS Master Design v2.0. Advisory only: this reviewer never approves, requests changes, or merges. Reply here to discuss or push back — a wrong finding is a bug worth reporting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Dependency updates major Breaking API or behaviour change

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant