search

cleder / pygeoif

Basic implementation of the __geo_interface__ 🌐️
https://pygeoif.readthedocs.io
67 stars 27 forks source link

Bump codecov/codecov-action from 4 to 5 #260

Closed dependabot[bot] closed 2 weeks ago

dependabot[bot] commented 2 weeks ago

Bumps codecov/codecov-action from 4 to 5.

Release notes

Sourced from codecov/codecov-action's releases.

v5.0.0

v5 Release

v5 of the Codecov GitHub Action will use the Codecov Wrapper to encapsulate the CLI. This will help ensure that the Action gets updates quicker.

Migration Guide

The v5 release also coincides with the opt-out feature for tokens for public repositories. In the repository settings page in codecov.io, you can set the ability for Codecov to receive a coverage report from ANY souce. This will allow contributors or other members of a repository to upload without needing access to the Codecov token.

[!WARNING]
The following arguments have been changed

  • file (this has been deprecated in favor of files)
  • plugin (this has been deprecated in favor of plugins)

The following arguments have been added:

  • binary
  • gcov_args
  • gcov_executable
  • gcov_ignore
  • gcov_include
  • report_type
  • skip_validation
  • swift_project

You can see their usage in the action.yml file.

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

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 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)

Summary by Sourcery

CI:

semanticdiff-com[bot] commented 2 weeks ago

Review changes with  SemanticDiff

sourcery-ai[bot] commented 2 weeks ago

Reviewer's Guide by Sourcery

This PR updates the Codecov GitHub Action from version 4 to version 5. The new version introduces significant changes including the use of the Codecov Wrapper to encapsulate the CLI, deprecation of some arguments, and addition of new features. The implementation is straightforward, requiring only a version bump in the GitHub Actions workflow file.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change Details Files
Update Codecov GitHub Action to version 5
  • Changed version specifier from v4 to v5 in GitHub Actions workflow
  • Maintains existing configuration parameters which are still compatible
 .github/workflows/run-all-tests.yml
Tips and commands #### Interacting with Sourcery - **Trigger a new review:** Comment `@sourcery-ai review` on the pull request. - **Continue discussions:** Reply directly to Sourcery's review comments. - **Generate a GitHub issue from a review comment:** Ask Sourcery to create an issue from a review comment by replying to it. - **Generate a pull request title:** Write `@sourcery-ai` anywhere in the pull request title to generate a title at any time. - **Generate a pull request summary:** Write `@sourcery-ai summary` anywhere in the pull request body to generate a PR summary at any time. You can also use this command to specify where the summary should be inserted. #### Customizing Your Experience Access your [dashboard](https://app.sourcery.ai) to: - Enable or disable review features such as the Sourcery-generated pull request summary, the reviewer's guide, and others. - Change the review language. - Add, remove or edit custom review instructions. - Adjust other review settings. #### Getting Help - [Contact our support team](mailto:support@sourcery.ai) for questions or feedback. - Visit our [documentation](https://docs.sourcery.ai) for detailed guides and information. - Keep in touch with the Sourcery team by following us on [X/Twitter](https://x.com/SourceryAI), [LinkedIn](https://www.linkedin.com/company/sourcery-ai/) or [GitHub](https://github.com/sourcery-ai).
coderabbitai[bot] commented 2 weeks ago

[!IMPORTANT]

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

🪧 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://docs.coderabbit.ai) 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.
what-the-diff[bot] commented 2 weeks ago

PR Summary

codiumai-pr-agent-free[bot] commented 2 weeks ago

CI Failure Feedback 🧐

(Checks updated until commit https://github.com/cleder/pygeoif/commit/2412cda099b6f7b102a8ce52f4a3c2fb20ce8109)

**Action:** test-coverage (3.12)
**Failed stage:** [Upload coverage to Codecov](https://github.com/cleder/pygeoif/actions/runs/11843292467/job/33003896602) [❌]
**Failure summary:** The action failed due to an error during the Codecov commit creation process:
  • The Codecov CLI attempted to create a commit but failed because a token was required for the
    operation.
  • The error message indicated that the branch is protected, necessitating a token for authentication.
  • As a result, the process exited with an error code 1.
    • Relevant error logs: ```yaml 1: ##[group]Operating System 2: Ubuntu ... 224: tests/test_linear_ring.py ........................... [ 71%] 225: tests/test_multiline.py ..................... [ 75%] 226: tests/test_multipoint.py ..................... [ 80%] 227: tests/test_multipolygon.py .................. [ 85%] 228: tests/test_point.py .................................. [ 93%] 229: tests/test_polygon.py .............................. [100%] 230: =============================== warnings summary =============================== 231: tests/hypothesis/test_line.py::test_max_points_lt_2 232: /home/runner/work/pygeoif/pygeoif/tests/hypothesis/test_line.py:17: NonInteractiveExampleWarning: The `.example()` method is good for exploring strategies, but should only be used interactively. We recommend using `@given` for tests - it performs better, saves and replays failures to avoid flakiness, and reports minimal examples. (strategy: line_strings(max_points=1)) ... 258: tests/hypothesis/test_line.py::test_convex_hull_bounds 259: tests/hypothesis/test_line.py::test_convex_hull_bounds 260: tests/hypothesis/test_line.py::test_convex_hull_bounds 261: tests/hypothesis/test_line.py::test_convex_hull_bounds 262: tests/hypothesis/test_line.py::test_convex_hull_bounds 263: /home/runner/work/pygeoif/pygeoif/tests/hypothesis/test_line.py:56: UserWarning: The convex Hull will only return the projection to 2 dimensions xy coordinates 264: assert line.convex_hull.bounds == line.bounds 265: tests/hypothesis/test_linear_ring.py::test_max_points_lt_3 266: /home/runner/work/pygeoif/pygeoif/tests/hypothesis/test_linear_ring.py:15: NonInteractiveExampleWarning: The `.example()` method is good for exploring strategies, but should only be used interactively. We recommend using `@given` for tests - it performs better, saves and replays failures to avoid flakiness, and reports minimal examples. (strategy: linear_rings(max_points=3)) ... 355: tests/hypothesis/test_point.py::test_convex_hull 356: tests/hypothesis/test_point.py::test_convex_hull 357: tests/hypothesis/test_point.py::test_convex_hull 358: tests/hypothesis/test_point.py::test_convex_hull 359: tests/hypothesis/test_point.py::test_convex_hull 360: /home/runner/work/pygeoif/pygeoif/tests/hypothesis/test_point.py:41: UserWarning: The convex Hull will only return the projection to 2 dimensions xy coordinates 361: assert point.convex_hull.bounds == point.bounds 362: tests/hypothesis/test_polygon.py::test_max_points_lt_3 363: /home/runner/work/pygeoif/pygeoif/tests/hypothesis/test_polygon.py:16: NonInteractiveExampleWarning: The `.example()` method is good for exploring strategies, but should only be used interactively. We recommend using `@given` for tests - it performs better, saves and replays failures to avoid flakiness, and reports minimal examples. (strategy: polygons(max_points=3)) ... 432: /home/runner/work/pygeoif/pygeoif/tests/test_polygon.py:226: UserWarning: The convex Hull will only return the projection to 2 dimensions xy coordinates 433: assert polygon.convex_hull == geometry.LineString([(0, 0), (2, 2)]) 434: tests/test_polygon.py::test_convex_hull_3d_collapsed_to_point 435: /home/runner/work/pygeoif/pygeoif/tests/test_polygon.py:232: UserWarning: The convex Hull will only return the projection to 2 dimensions xy coordinates 436: assert polygon.convex_hull == geometry.Point(0, 0) 437: -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html 438: ---------- coverage: platform linux, python 3.12.7-final-0 ----------- 439: Coverage XML written to file coverage.xml 440: ================ 428 passed, 1 xfailed, 155 warnings in 19.10s ================= 441: ##[group]Run codecov/codecov-action@v5 442: with: 443: fail_ci_if_error: true ... 512: CC_CODE: 513: CC_DIR: 514: CC_DISABLE_FILE_FIXES: false 515: CC_DISABLE_SEARCH: false 516: CC_DRY_RUN: false 517: CC_ENTERPRISE_URL: 518: CC_ENV: 519: CC_EXCLUDES: 520: CC_FAIL_ON_ERROR: true ... 571: gpg: Good signature from "Codecov Uploader (Codecov Uploader Verification Key) " [unknown] 572: gpg: WARNING: This key is not certified with a trusted signature! 573: gpg: There is no indication that the signature belongs to the owner. 574: Primary key fingerprint: 2703 4E7F DB85 0E0B BC2C 62FF 806B B28A ED77 9869 575: codecov: OK 576: ==> CLI integrity verified 577:  -> Token of length 0 detected 578: ==> Running create-commit 579: ./codecov --verbose create-commit --fail-on-error --git-service github 580: info - 2024-11-14 18:30:02,321 -- ci service found: github-actions 581: debug - 2024-11-14 18:30:02,324 -- versioning system found: 582: debug - 2024-11-14 18:30:02,327 -- versioning system found: 583: warning - 2024-11-14 18:30:02,330 -- No config file could be found. Ignoring config. 584: debug - 2024-11-14 18:30:02,330 -- No codecov_yaml found 585: debug - 2024-11-14 18:30:02,333 -- Starting create commit process --- {"verbose": true, "auto_load_params_from": null, "codecov_yml_path": null, "enterprise_url": null, "version": "cli-9.0.4", "command": "create-commit", "fail_on_error": true, "git_service": "github", "parent_sha": null, "pull_request_number": "260", "branch": "dependabot/github_actions/codecov/codecov-action-5", "commit_sha": "9abc3678dd349995e375a88145e73639f21cc922", "slug": "cleder/pygeoif"} 586: info - 2024-11-14 18:30:02,828 -- Process Commit creating complete 587: debug - 2024-11-14 18:30:02,828 -- Commit creating result --- {"result": "RequestResult(error=RequestError(code='HTTP Error 400', params={}, description='{\"message\":\"Token required because branch is protected\"}\\n'), warnings=[], status_code=400, text='{\"message\":\"Token required because branch is protected\"}\\n')"} 588: error - 2024-11-14 18:30:02,828 -- Commit creating failed: {"message":"Token required because branch is protected"} 589: ==> Failed to create-commit 590:  Exiting... 591: ##[error]Process completed with exit code 1. ```
    ✨ CI feedback usage guide:
    The CI feedback tool (`/checks)` automatically triggers when a PR has a failed check. The tool analyzes the failed checks and provides several feedbacks: - Failed stage - Failed test name - Failure summary - Relevant error logs In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR: ``` /checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}" ``` where `{repo_name}` is the name of the repository, `{run_number}` is the run number of the failed check, and `{job_number}` is the job number of the failed check. #### Configuration options - `enable_auto_checks_feedback` - if set to true, the tool will automatically provide feedback when a check is failed. Default is true. - `excluded_checks_list` - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list. - `enable_help_text` - if set to true, the tool will provide a help message with the feedback. Default is true. - `persistent_comment` - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true. - `final_update_message` - if `persistent_comment` is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true. See more information about the `checks` tool in the [docs](https://pr-agent-docs.codium.ai/tools/ci_feedback/).
    github-actions[bot] commented 2 weeks ago

    Failed to generate code suggestions for PR

    github-actions[bot] commented 2 weeks ago

    Preparing review...