This is an automated email from the ASF dual-hosted git repository.

rmaucher pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/tomcat-jakartaee-migration.git


The following commit(s) were added to refs/heads/main by this push:
     new db43e55  Bump codecov/codecov-action from 6.0.1 to 7.0.0
db43e55 is described below

commit db43e5538caac18fd10b9567950f6a421497eb8a
Author: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
AuthorDate: Mon Jun 8 04:53:02 2026 +0000

    Bump codecov/codecov-action from 6.0.1 to 7.0.0
    
    Bumps [codecov/codecov-action](https://github.com/codecov/codecov-action) 
from 6.0.1 to 7.0.0.
    - [Release notes](https://github.com/codecov/codecov-action/releases)
    - 
[Changelog](https://github.com/codecov/codecov-action/blob/main/CHANGELOG.md)
    - 
[Commits](https://github.com/codecov/codecov-action/compare/e79a6962e0d4c0c17b229090214935d2e33f8354...fb8b3582c8e4def4969c97caa2f19720cb33a72f)
    
    ---
    updated-dependencies:
    - dependency-name: codecov/codecov-action
      dependency-version: 7.0.0
      dependency-type: direct:production
      update-type: version-update:semver-major
    ...
    
    Signed-off-by: dependabot[bot] <[email protected]>
---
 .github/workflows/coverage.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.github/workflows/coverage.yml b/.github/workflows/coverage.yml
index 0f0b60c..bb3cb5a 100644
--- a/.github/workflows/coverage.yml
+++ b/.github/workflows/coverage.yml
@@ -52,6 +52,6 @@ jobs:
       run: mvn -V test jacoco:report --file pom.xml --no-transfer-progress
     - name: Upload coverage to Codecov
       # Pin to 6.0.1
-      uses: codecov/codecov-action@e79a6962e0d4c0c17b229090214935d2e33f8354
+      uses: codecov/codecov-action@fb8b3582c8e4def4969c97caa2f19720cb33a72f
       with:
         files: ./target/site/jacoco/jacoco.xml


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to