varfish-org / varfish-cli

VarFish REST API client (CLI + Python package)
MIT License
2 stars 3 forks source link

chore(deps): bump codecov/codecov-action from 3 to 4 #106

Open dependabot[bot] opened 9 months ago

dependabot[bot] commented 9 months ago

Bumps codecov/codecov-action from 3 to 4.

Release notes

Sourced from codecov/codecov-action's releases.

v4.0.0

v4 of the Codecov Action uses the CLI as the underlying upload. The CLI has helped to power new features including local upload, the global upload token, and new upcoming features.

Breaking Changes

  • The Codecov Action runs as a node20 action due to node16 deprecation. See this post from GitHub on how to migrate.
  • Tokenless uploading is unsupported. However, PRs made from forks to the upstream public repos will support tokenless (e.g. contributors to OS projects do not need the upstream repo's Codecov token). This doc shows instructions on how to add the Codecov token.
  • OS platforms have been added, though some may not be automatically detected. To see a list of platforms, see our CLI download page
  • Various arguments to the Action have been changed. Please be aware that the arguments match with the CLI's needs

v3 versions and below will not have access to CLI features (e.g. global upload token, ATS).

What's Changed

... (truncated)

Changelog

Sourced from codecov/codecov-action's changelog.

4.0.0-beta.2

Fixes

  • #1085 not adding -n if empty to do-upload command

4.0.0-beta.1

v4 represents a move from the universal uploader to the Codecov CLI. Although this will unlock new features for our users, the CLI is not yet at feature parity with the universal uploader.

Breaking Changes

  • No current support for aarch64 and alpine architectures.
  • Tokenless uploading is unsuported
  • Various arguments to the Action have been removed

3.1.4

Fixes

  • #967 Fix typo in README.md
  • #971 fix: add back in working dir
  • #969 fix: CLI option names for uploader

Dependencies

  • #970 build(deps-dev): bump @​types/node from 18.15.12 to 18.16.3
  • #979 build(deps-dev): bump @​types/node from 20.1.0 to 20.1.2
  • #981 build(deps-dev): bump @​types/node from 20.1.2 to 20.1.4

3.1.3

Fixes

  • #960 fix: allow for aarch64 build

Dependencies

  • #957 build(deps-dev): bump jest-junit from 15.0.0 to 16.0.0
  • #958 build(deps): bump openpgp from 5.7.0 to 5.8.0
  • #959 build(deps-dev): bump @​types/node from 18.15.10 to 18.15.12

3.1.2

Fixes

  • #718 Update README.md
  • #851 Remove unsupported path_to_write_report argument
  • #898 codeql-analysis.yml
  • #901 Update README to contain correct information - inputs and negate feature
  • #955 fix: add in all the extra arguments for uploader

Dependencies

  • #819 build(deps): bump openpgp from 5.4.0 to 5.5.0
  • #835 build(deps): bump node-fetch from 3.2.4 to 3.2.10
  • #840 build(deps): bump ossf/scorecard-action from 1.1.1 to 2.0.4
  • #841 build(deps): bump @​actions/core from 1.9.1 to 1.10.0
  • #843 build(deps): bump @​actions/github from 5.0.3 to 5.1.1
  • #869 build(deps): bump node-fetch from 3.2.10 to 3.3.0
  • #872 build(deps-dev): bump jest-junit from 13.2.0 to 15.0.0
  • #879 build(deps): bump decode-uri-component from 0.2.0 to 0.2.2

... (truncated)

Commits


Dependabot compatibility score

You can trigger a rebase of this PR 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 merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show 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)

Note Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

Summary by CodeRabbit

holtgrewe commented 1 month ago

@coderabbitai full review

coderabbitai[bot] commented 1 month ago
:white_check_mark: Actions performed Full review triggered.
coderabbitai[bot] commented 1 month ago

Walkthrough

The changes in the pull request focus on the GitHub Actions workflow configuration within the .github/workflows/main.yml file. Key updates include the introduction of a matrix strategy for the testing job to support multiple Python versions (3.10, 3.11, and 3.12) and an update of the Codecov action from version 3 to version 4. Other jobs, including canceling previous workflows, linting, and building documentation, remain unchanged in their structure and steps.

Changes

File Path Change Summary
.github/workflows/main.yml - Updated Codecov action from v3 to v4 in the testing job.
- Introduced a matrix strategy for testing across Python versions 3.10, 3.11, and 3.12.
- No changes to the cancel-previous, linting, and sphinx documentation jobs.

Sequence Diagram(s)

sequenceDiagram
    participant A as Developer
    participant B as GitHub Actions
    participant C as Codecov
    participant D as Testing Framework

    A->>B: Push code changes
    B->>B: Cancel previous workflows (if not main)
    B->>B: Lint code
    B->>B: Build documentation
    B->>D: Run tests on Python 3.10
    B->>D: Run tests on Python 3.11
    B->>D: Run tests on Python 3.12
    D->>C: Report test coverage
    C->>B: Update coverage report

Poem

🐇 In the land of code where bunnies play,
A workflow update brightens the day.
With Python versions hopping in line,
Our tests now run, all working fine!
Codecov's new coat, shiny and bright,
Keeps our coverage in clear sight! 🌟


📜 Recent review details **Configuration used: CodeRabbit UI** **Review profile: CHILL**
📥 Commits Files that changed from the base of the PR and between 878af61cda7c617be16eda55f2c450346c50598b and deb16e6df9ef0dbbce4063fcd9bb050eb9794a77.
📒 Files selected for processing (1) * .github/workflows/main.yml (1 hunks)
🧰 Additional context used
🔇 Additional comments (2)
.github/workflows/main.yml (2)
Line range hint `66-70`: **Approve matrix strategy for Python versions, but clarification needed.** The introduction of a matrix strategy to test across Python versions 3.10, 3.11, and 3.12 is a good practice that enhances the robustness of your testing process. This ensures compatibility across multiple Python versions. However, this change seems unrelated to the main objective of updating the Codecov action. Could you please clarify why this change was included in this PR? It might be better to separate unrelated changes into different PRs for clarity and easier review. To verify the impact of this change, let's check if the project's `setup.py` or `pyproject.toml` specifies compatible Python versions: ```shell #!/bin/bash # Check for Python version specifications in setup.py or pyproject.toml echo "Checking setup.py:" rg 'python_requires' setup.py echo "Checking pyproject.toml:" rg '\[tool\.poetry\.dependencies\]' -A 5 pyproject.toml ``` --- `95-95`: **Approve Codecov action update, but verify configuration.** The update of the Codecov action from v3 to v4 aligns with the PR objectives. This is a significant update that introduces the use of Codecov CLI for uploads and removes support for tokenless uploading (except for PRs from forks to public repositories). However, the PR objectives mention that various arguments for the action have been modified to align with the CLI's requirements. It's important to verify if any additional configuration is needed for the action to work correctly with v4. Let's check if there are any Codecov-related configuration files in the repository that might need updating: Additionally, please review the [Codecov Action v4 documentation](https://github.com/codecov/codecov-action#usage) to ensure all necessary configurations are in place, especially regarding the handling of upload tokens for your repository type (public/private).
---
🪧 Tips ### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit , please review it.` - `Generate unit testing code for this file.` - `Open a follow-up GitHub issue for this discussion.` - Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples: - `@coderabbitai generate unit testing code for this file.` - `@coderabbitai modularize this function.` - PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples: - `@coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.` - `@coderabbitai read src/utils.ts and generate unit testing code.` - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.` - `@coderabbitai help me debug CodeRabbit configuration file.` Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. ### CodeRabbit Commands (Invoked using PR comments) - `@coderabbitai pause` to pause the reviews on a PR. - `@coderabbitai resume` to resume the paused reviews. - `@coderabbitai review` to trigger an incremental review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai full review` to do a full review from scratch and review all the files again. - `@coderabbitai summary` to regenerate the summary of the PR. - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai configuration` to show the current CodeRabbit configuration for the repository. - `@coderabbitai help` to get help. ### Other keywords and placeholders - Add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. - Add `@coderabbitai summary` to generate the high-level summary at a specific location in the PR description. - Add `@coderabbitai` anywhere in the PR title to generate the title automatically. ### CodeRabbit Configuration File (`.coderabbit.yaml`) - You can programmatically configure CodeRabbit by adding a `.coderabbit.yaml` file to the root of your repository. - Please see the [configuration documentation](https://docs.coderabbit.ai/guides/configure-coderabbit) for more information. - If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: `# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json` ### Documentation and Community - Visit our [Documentation](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](http://discord.gg/coderabbit) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.