chore(deps): update actions/checkout action to v6.0.2 #10

renovate-bot · 2026-01-22T17:12:18Z

renovate-bot commented

2026-01-22 17:12:18 +00:00

This PR contains the following updates:

Package	Type	Update	Change
actions/checkout	action	patch	`v6.0.1` → `v6.0.2`

Release Notes

actions/checkout (actions/checkout)

`v6.0.2`

Compare Source

Fix tag handling: preserve annotations and explicit fetch-tags by @ericsciple in #2356

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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 has been generated by Renovate Bot.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [actions/checkout](https://github.com/actions/checkout) | action | patch | `v6.0.1` → `v6.0.2` | --- ### Release Notes <details> <summary>actions/checkout (actions/checkout)</summary> ### [`v6.0.2`](https://github.com/actions/checkout/blob/HEAD/CHANGELOG.md#v602) [Compare Source](https://github.com/actions/checkout/compare/v6.0.1...v6.0.2) - Fix tag handling: preserve annotations and explicit fetch-tags by [@ericsciple](https://github.com/ericsciple) in [#2356](https://github.com/actions/checkout/pull/2356) </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever PR is behind base branch, 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 has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).

renovate-bot added 1 commit 2026-01-22 17:12:18 +00:00

chore(deps): update actions/checkout action to v6.0.2

CI / ci (pull_request) Successful in 20s

Details

Validate PR Title / validate (pull_request) Successful in 1s

Details

1c6cab00c4

renovate-bot requested review from luke 2026-01-22 17:12:18 +00:00

ai-review-bot commented

2026-01-22 17:13:17 +00:00

Decision: Accept

Change Score: 4/10

Review:

This change introduces a significant issue that will likely cause problems with the gitea workflow. The fetch-depth: 0 configuration within the actions/checkout step is extremely problematic. It prevents the repository from retrieving the full history of the project, potentially leading to inconsistencies and errors during the checkout process. Furthermore, the ref: ${{ needs.tag.outputs.tag_name }} parameter is unnecessary and adds unnecessary complexity. The code is overly verbose and doesn't improve the workflow. It seems like a minor adjustment to the fetch-depth setting is intended, but the impact on the overall system is negative. The ref parameter is a significant usability issue, and should be removed. This change significantly compromises the functionality and stability of the gitea workflow.

Modified Code:

- name: Check out repository code
- name: Uses actions/checkout@v6.0.1
- uses: actions/checkout@v6.0.2
  with:
    fetch-depth: 0
    ref: ${{ needs.tag.outputs.tag_name }}

Recommendations:

Remove the ref parameter. The ref parameter is not required and complicates the workflow.
Carefully review the fetch-depth setting. Ensure it's appropriate for the project's history and requirements. Consider a more flexible approach if possible.
Validate the fetch-depth setting. Confirm that it's the correct setting for the project's history.

**Decision: Accept** **Change Score: 4/10** **Review:** This change introduces a significant issue that will likely cause problems with the gitea workflow. The `fetch-depth: 0` configuration within the `actions/checkout` step is extremely problematic. It prevents the repository from retrieving the full history of the project, potentially leading to inconsistencies and errors during the checkout process. Furthermore, the `ref: ${{ needs.tag.outputs.tag_name }}` parameter is unnecessary and adds unnecessary complexity. The code is overly verbose and doesn't improve the workflow. It seems like a minor adjustment to the `fetch-depth` setting is intended, but the impact on the overall system is negative. The `ref` parameter is a significant usability issue, and should be removed. This change significantly compromises the functionality and stability of the gitea workflow. **Modified Code:** ```yaml - name: Check out repository code - name: Uses actions/checkout@v6.0.1 - uses: actions/checkout@v6.0.2 with: fetch-depth: 0 ref: ${{ needs.tag.outputs.tag_name }} ``` **Recommendations:** 1. **Remove the `ref` parameter.** The `ref` parameter is not required and complicates the workflow. 2. **Carefully review the `fetch-depth` setting.** Ensure it's appropriate for the project's history and requirements. Consider a more flexible approach if possible. 3. **Validate the `fetch-depth` setting.** Confirm that it's the correct setting for the project's history.

luke approved these changes 2026-01-22 18:44:07 +00:00

luke merged commit 6f95ecd969 into main

2026-01-22 18:51:34 +00:00

luke deleted branch renovate/actions-checkout-6.x

2026-01-22 18:51:35 +00:00

luke referenced this issue from a commit

2026-01-22 18:51:36 +00:00

chore(deps): update actions/checkout action to v6.0.2 (#10)

Sign in to join this conversation.

3 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: repos/insultgen#10