Update orgoro/coverage action to v3.3#113
Open
renovate[bot] wants to merge 1 commit intomainfrom
Open
Conversation
26f610a to
f10ba64
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v3.1→v3.3Release Notes
orgoro/coverage (orgoro/coverage)
v3.3.1: — renamed files counted as modifiedCompare Source
Fix
compareCommitswas only counting files with statusaddedormodified. The GitHub compare API also returnsrenamedfor git rename detection — those files were silently dropped, so refactor PRs that rename files lost coverage tracking on them. Now renamed files are included as modified. (#350, originally proposed in #325 by @mangunowsky)Full changelog: orgoro/coverage@v3.3...v3.3.1
v3.3: — node24 runtime, configurable title, docsCompare Source
Runtime
node20tonode24^5.4,@types/node ^24,jest/ts-jest ^29Features
titleinput — heading text for the PR comment. Default changed fromPython CoveragetoCode Coveragesince the action works for any language producing cobertura xml. Setting a unique value per matrix entry (e.g.Python Coverage 3.10,Python Coverage 3.11) posts separate comments instead of overwriting one shared one. Closes #328, #320.Docs
contents: read,pull-requests: write). Closes #310.Fixes
Lines→Statementsto matchcoverage.pyterminology. Closes #250.The default
titlechanged fromPython CoveragetoCode Coverage. The first post-upgrade run will create a new comment instead of updating the existingPython Coverageone (the old comment becomes orphaned on each open PR). To preserve the old behavior, pin the title:Full changelog: orgoro/coverage@v3.2...v3.3
v3.2: - node20, support to sourceDir and don't fail on non pull requests (skip instead)Compare Source
What's Changed
New Contributors
Full Changelog: orgoro/coverage@v3.1...v3.2
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.