chore(deps): update actions/checkout action to v4 #66

renovate · 2023-09-05T04:02:37Z

This PR contains the following updates:

Package	Type	Update	Change
actions/checkout	action	major	`v3.6.0` -> `v4.2.2`

Release Notes

actions/checkout (actions/checkout)

`v4.2.2`

Compare Source

url-helper.ts now leverages well-known environment variables by @jww3 in https://github.com/actions/checkout/pull/1941
Expand unit test coverage for isGhes by @jww3 in https://github.com/actions/checkout/pull/1946

`v4.2.1`

Compare Source

Check out other refs/* by commit if provided, fall back to ref by @orhantoy in https://github.com/actions/checkout/pull/1924

`v4.2.0`

Compare Source

Add Ref and Commit outputs by @lucacome in https://github.com/actions/checkout/pull/1180
Dependency updates by @dependabot- https://github.com/actions/checkout/pull/1777, https://github.com/actions/checkout/pull/1872

`v4.1.7`

Compare Source

Bump the minor-npm-dependencies group across 1 directory with 4 updates by @dependabot in https://github.com/actions/checkout/pull/1739
Bump actions/checkout from 3 to 4 by @dependabot in https://github.com/actions/checkout/pull/1697
Check out other refs/* by commit by @orhantoy in https://github.com/actions/checkout/pull/1774
Pin actions/checkout's own workflows to a known, good, stable version. by @jww3 in https://github.com/actions/checkout/pull/1776

`v4.1.6`

Compare Source

Check platform to set archive extension appropriately by @cory-miller in https://github.com/actions/checkout/pull/1732

What's Changed

Update actions/checkout version in update-main-version.yml by @jww3 in https://github.com/actions/checkout/pull/1650
Check git version before attempting to disable sparse-checkout by @jww3 in https://github.com/actions/checkout/pull/1656
Add SSH user parameter by @cory-miller in https://github.com/actions/checkout/pull/1685

Full Changelog: actions/checkout@v4.1.2...v4.1.3

`v4.1.2`

Compare Source

Fix: Disable sparse checkout whenever sparse-checkout option is not present @dscho in https://github.com/actions/checkout/pull/1598

`v4.1.1`

Compare Source

What's Changed

Update CODEOWNERS to Launch team by @joshmgross in https://github.com/actions/checkout/pull/1510
Correct link to GitHub Docs by @peterbe in https://github.com/actions/checkout/pull/1511
Link to release page from what's new section by @cory-miller in https://github.com/actions/checkout/pull/1514

New Contributors

@joshmgross made their first contribution in https://github.com/actions/checkout/pull/1510
@peterbe made their first contribution in https://github.com/actions/checkout/pull/1511

Full Changelog: actions/checkout@v4.1.0...v4.1.1

`v4.1.0`

Compare Source

Add support for partial checkout filters

`v4.0.0`

Compare Source

Configuration

📅 Schedule: Branch creation - "* 0-3 * * *" in timezone America/Sao_Paulo, Automerge - At any time (no schedule defined).

🚦 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.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

pull-request-quantifier-deprecated · 2023-09-22T19:58:04Z

This PR has 6 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

Quantification details

Label      : Extra Small
Size       : +3 -3
Percentile : 2.4%

Total files changed: 3

Change summary by file extension:
.yml : +3 -3

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

Fast and predictable releases to production:
- Optimal size changes are more likely to be reviewed faster with fewer
  iterations.
- Similarity in low PR complexity drives similar review times.
Review quality is likely higher as complexity is lower:
- Bugs are more likely to be detected.
- Code inconsistencies are more likely to be detected.
Knowledge sharing is improved within the participants:
- Small portions can be assimilated better.
Better engineering practices are exercised:
- Solving big problems by dividing them in well contained, smaller problems.
- Exercising separation of concerns within the code changes.

What can I do to optimize my changes

Use the PullRequestQuantifier to quantify your PR accurately
- Create a context profile for your repo using the context generator
- Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
- Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
- Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
Change your engineering behaviors
- For PRs that fall outside of the desired spectrum, review the details and check if:
  - Your PR could be split in smaller, self-contained PRs instead
  - Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

One line was added: +1 -0
One line was deleted: +0 -1
One line was modified: +1 -1 (git diff doesn't know about modified, it will
interpret that line like one addition plus one deletion)
Change percentiles: Change characteristics (addition, deletion, modification)
of this PR in relation to all other PRs within the repository.

Was this comment helpful? 👍 :ok_hand: :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

pull-request-quantifier-deprecated · 2024-03-12T12:13:58Z

This PR has 6 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

Quantification details

Label      : Extra Small
Size       : +3 -3
Percentile : 2.4%

Total files changed: 3

Change summary by file extension:
.yml : +3 -3

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

Fast and predictable releases to production:
- Optimal size changes are more likely to be reviewed faster with fewer
  iterations.
- Similarity in low PR complexity drives similar review times.
Review quality is likely higher as complexity is lower:
- Bugs are more likely to be detected.
- Code inconsistencies are more likely to be detected.
Knowledge sharing is improved within the participants:
- Small portions can be assimilated better.
Better engineering practices are exercised:
- Solving big problems by dividing them in well contained, smaller problems.
- Exercising separation of concerns within the code changes.

What can I do to optimize my changes

Use the PullRequestQuantifier to quantify your PR accurately
- Create a context profile for your repo using the context generator
- Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
- Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
- Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
Change your engineering behaviors
- For PRs that fall outside of the desired spectrum, review the details and check if:
  - Your PR could be split in smaller, self-contained PRs instead
  - Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

One line was added: +1 -0
One line was deleted: +0 -1
One line was modified: +1 -1 (git diff doesn't know about modified, it will
interpret that line like one addition plus one deletion)
Change percentiles: Change characteristics (addition, deletion, modification)
of this PR in relation to all other PRs within the repository.

Was this comment helpful? 👍 :ok_hand: :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

pull-request-quantifier-deprecated · 2024-03-12T17:03:32Z

This PR has 6 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

Quantification details

Label      : Extra Small
Size       : +3 -3
Percentile : 2.4%

Total files changed: 3

Change summary by file extension:
.yml : +3 -3

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

Fast and predictable releases to production:
- Optimal size changes are more likely to be reviewed faster with fewer
  iterations.
- Similarity in low PR complexity drives similar review times.
Review quality is likely higher as complexity is lower:
- Bugs are more likely to be detected.
- Code inconsistencies are more likely to be detected.
Knowledge sharing is improved within the participants:
- Small portions can be assimilated better.
Better engineering practices are exercised:
- Solving big problems by dividing them in well contained, smaller problems.
- Exercising separation of concerns within the code changes.

What can I do to optimize my changes

Use the PullRequestQuantifier to quantify your PR accurately
- Create a context profile for your repo using the context generator
- Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
- Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
- Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
Change your engineering behaviors
- For PRs that fall outside of the desired spectrum, review the details and check if:
  - Your PR could be split in smaller, self-contained PRs instead
  - Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

One line was added: +1 -0
One line was deleted: +0 -1
One line was modified: +1 -1 (git diff doesn't know about modified, it will
interpret that line like one addition plus one deletion)
Change percentiles: Change characteristics (addition, deletion, modification)
of this PR in relation to all other PRs within the repository.

Was this comment helpful? 👍 :ok_hand: :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

codecov · 2024-12-28T20:09:37Z

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (fc4fd54) to head (6b32ca8).
Report is 6 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main       #66   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           11        11           
  Lines          174       174           
  Branches        23        23           
=========================================
  Hits           174       174

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

renovate · 2024-12-28T20:59:44Z

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 4.x releases. But if you manually upgrade to 4.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

pull-request-quantifier-deprecated bot added the Extra Small label Sep 5, 2023

renovate bot force-pushed the renovate/actions-checkout-4.x branch from ff1b295 to ee4c69f Compare September 22, 2023 19:57

renovate bot force-pushed the renovate/actions-checkout-4.x branch 2 times, most recently from a816537 to c6cc938 Compare October 17, 2023 19:12

renovate bot force-pushed the renovate/actions-checkout-4.x branch from c6cc938 to 16a8470 Compare March 12, 2024 12:13

renovate bot force-pushed the renovate/actions-checkout-4.x branch from 16a8470 to 42ca105 Compare March 12, 2024 16:44

renovate bot force-pushed the renovate/actions-checkout-4.x branch 2 times, most recently from 11ee13a to 78f5d8d Compare April 25, 2024 15:03

renovate bot force-pushed the renovate/actions-checkout-4.x branch from 78f5d8d to b9a0536 Compare May 8, 2024 22:41

renovate bot force-pushed the renovate/actions-checkout-4.x branch from b9a0536 to fd7d5e2 Compare May 16, 2024 19:14

renovate bot force-pushed the renovate/actions-checkout-4.x branch from fd7d5e2 to 6eb0761 Compare June 12, 2024 23:01

renovate bot force-pushed the renovate/actions-checkout-4.x branch from 6eb0761 to 5123e13 Compare September 25, 2024 18:56

renovate bot force-pushed the renovate/actions-checkout-4.x branch from 5123e13 to 1d1b70d Compare October 23, 2024 15:57

chore(deps): update actions/checkout action to v4

6b32ca8

renovate bot force-pushed the renovate/actions-checkout-4.x branch from 1d1b70d to 6b32ca8 Compare December 28, 2024 20:08

GabrielGuedess closed this Dec 28, 2024

renovate bot deleted the renovate/actions-checkout-4.x branch December 28, 2024 20:59

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(deps): update actions/checkout action to v4 #66

chore(deps): update actions/checkout action to v4 #66

renovate bot commented Sep 5, 2023 •

edited

Loading

pull-request-quantifier-deprecated bot commented Sep 22, 2023

What can I do to optimize my changes

How to interpret the change counts in git diff output

pull-request-quantifier-deprecated bot commented Mar 12, 2024

What can I do to optimize my changes

How to interpret the change counts in git diff output

pull-request-quantifier-deprecated bot commented Mar 12, 2024

What can I do to optimize my changes

How to interpret the change counts in git diff output

codecov bot commented Dec 28, 2024 •

edited

Loading

renovate bot commented Dec 28, 2024

chore(deps): update actions/checkout action to v4 #66

chore(deps): update actions/checkout action to v4 #66

Conversation

renovate bot commented Sep 5, 2023 • edited Loading

Release Notes

What's Changed

What's Changed

What's Changed

New Contributors

Configuration

pull-request-quantifier-deprecated bot commented Sep 22, 2023

What can I do to optimize my changes

How to interpret the change counts in git diff output

pull-request-quantifier-deprecated bot commented Mar 12, 2024

What can I do to optimize my changes

How to interpret the change counts in git diff output

pull-request-quantifier-deprecated bot commented Mar 12, 2024

What can I do to optimize my changes

How to interpret the change counts in git diff output

codecov bot commented Dec 28, 2024 • edited Loading

Codecov Report

renovate bot commented Dec 28, 2024

Renovate Ignore Notification

renovate bot commented Sep 5, 2023 •

edited

Loading

codecov bot commented Dec 28, 2024 •

edited

Loading