chore(deps): update actions/checkout digest to 0ad4b8f

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
actions/checkout	action	digest	1d96c77 -> 0ad4b8f

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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 has been generated by Mend Renovate. View repository job log here.

---

PR-Codex overview

This PR updates the GitHub Actions checkout version in multiple workflows to 0ad4b8fadaa221de15dcec353f45205ec38ea70b.

Detailed summary

• Updated GitHub Actions checkout version to 0ad4b8fadaa221de15dcec353f45205ec38ea70b in various workflows.
• Removed or updated setup actions like g4s8/xcop-action, shadowmoose/GHA-LoC-Badge, FantasticFiasco/action-update-license-year, and teatimeguest/setup-texlive-action.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

[github-actions]

There don't seem to be any functional conflicts, but there is a possible inconsistency in the comments. The comment on the "actions/checkout" step says "# v4" for both the old and new SHA (commit hash). If you are actually changing the version of the "actions/checkout" action you're using, ensure this comment reflects the correct version. If the change does not represent a different version, then there is nothing wrong.

Just in case, verify that the new hash "0ad4b8fadaa221de15dcec353f45205ec38ea70b" refers to the right commit of the "actions/checkout" you want to switch to.

[github-actions]

The provided code diff shows that a change was made to one of the GitHub Actions used in your workflow, specifically actions/checkout. The action's version (v4) is supposedly kept the same, but the SHA hash value after @ has changed.

This inconsistency could lead to different behaviors since in GitHub Actions, two separate commits (signified by the diff SHA values: 1d96c772d19495a3b5c517cd2bc0cb401ea0529f and 0ad4b8fadaa221de15dcec353f45205ec38ea70b) might bring different code changes even though they're labeled with the same explicit version tag (# v4).

It would be worthwhile to verify that the new SHA hash you've switched to, 0ad4b8fadaa221de15dcec353f45205ec38ea70b, actually corresponds to the correct version of actions/checkout that you need. Furthermore, the comment should accurately reflect the version or commit being used.

[github-actions]

The code you have shared is a diff, which is showing the changes made in a GitHub Actions configuration file. This particular diff indicates only one modification: the actions/checkout action version has updated.

In this case, specifically:

• The line - uses: actions/checkout@1d96c772d19495a3b5c517cd2bc0cb401ea0529f # v4 got replaced by
  + uses: actions/checkout@0ad4b8fadaa221de15dcec353f45205ec38ea70b # v4.

This change suggests that the commit SHA identifier used for the version of actions/checkout action is updated from 1d96c772d19495a3b5c517cd2bc0cb401ea0529f to 0ad4b8fadaa221de15dcec353f45205ec38ea70b.

However, there's a minor irregularity or point of confusion here: The comment on both lines declares the version as v4, but typically when a new SHA is used, it comes with a new version. It might lead to confusion if someone refers the version by looking at this comment while it's actually referring to the new commit SHA.

Please note that without additional context, e.g., the actual repository, it's not possible to validate if this commit SHA (0ad4b8fadaa221de15dcec353f45205ec38ea70b) is indeed still version "v4". For a thorough review, consider checking actual commit differences and any associated tags or releases in the originating repository.

[github-actions]

The diff you've presented reflects a change in the checkout action version being used in a GitHub Actions workflow file. The only line of actual code that has changed is where it's specifying the Git SHA (or version) for the checkout action.

• Originally, - uses: actions/checkout@1d96c772d19495a3b5c517cd2bc0cb401ea0529f # v4
• Changed to, + uses: actions/checkout@0ad4b8fadaa221de15dcec353f45205ec38ea70b # v4

However, there is a potential confusion or irregularity in your comment "# v4". This comment suggests that both SHAs refer to version 4 of the checkout action, which might be misleading if not true. If the new commit hash refers to a different version, this could cause unintended consequences in the workflow execution. It's important to ensure that the reference comments accurately correspond to the associated commit hashes to avoid misunderstanding or miscommunication.

As an additional note, ensure that the commit hashes correspond to verified, secure versions of the actions you intend to use. It's generally recommended to use tagged releases rather than arbitrary commit hashes. This adds an extra layer of security as malicious code can't be added to a version without creating a new version.

[github-actions]

The code diff provided shows a change in a GitHub Action workflow file. The change occurs in the specified version of the 'actions/checkout' action. The hash values 1d96c772d19495a3b5c517cd2bc0cb401ea0529f and 0ad4b8fadaa221de15dcec353f45205ec38ea70b represent different commit SHAs.

Although both comments denote # v4, it's possible they are not the same version, because the commit SHAs are different.

To eliminate confusion, ensure that the comment accurately reflects the commit SHA. For example, if 0ad4b8fadaa221de15dcec353f45205ec38ea70b corresponds to version 5, the comment should be updated to # v5 instead of # v4.

Please ensure you are replacing with the correct commit SHA and update the comment accordingly to improve clarity and prevent future confusions.

[github-actions]

The change seen in the diff is an update of the version of the actions/checkout action used in the GitHub Actions workflow to a different commit hash. This isn't necessarily a confusion or irregularity, but rather a standard part of maintaining and updating workflows.

However, it's important to note that this change doesn't accurately reflect the comment present alongside it. The comment indicates the use of version 4 (v4) of the actions/checkout action, but the provided commit hashes do not correlate with any specific version. Commit hashes are unique identifiers for each commit, they don't directly relate to the version of a repository or action.

Therefore, the potential confusion or ambiguity lies in the fact that the comment is not updated or kept consistent with the commit hash. If the commit hash refers to version 4 of the action, then the comment is accurate, but without access to the repository to check the relation between commit hash and version, the exact accuracy is uncertain.

Remember that updating actions in a workflow is a normal process and should be done while understanding what changes the new commits bring. Always verify that the new commit is compatible with your project and achieves the intended results.

[github-actions]

The code diff shows that the version of the actions/checkout action used in a GitHub Actions workflow was changed. The change is from commit hash 1d96c772d19495a3b5c517cd2bc0cb401ea0529f to 0ad4b8fadaa221de15dcec353f45205ec38ea70b.

In terms of syntax and semantics, there doesn't seem to be any confusion or irregularity - it looks like a perfectly valid change for a GitHub Actions workflow.

However, please note that both revisions are marked as # v4. If the comment on these lines is supposed to reflect the version of the actions/checkout action, then manual verification would be necessary to ensure the change indeed reflects version 4 of the action in both cases.

Because commit hashes can identify any point in the repository's history, they don't necessarily map to specific 'version' numbers unless the project has been specifically structured that way.

For this reason, you should ensure that the new commit hash (i.e., 0ad4b8fadaa221de15dcec353f45205ec38ea70b) does indeed correspond to version 4 (if that's your intention) by checking the actions/checkout repository. Note that the only real source of confusion or irregularity here is a minor documentation concern; the actual change (updating the commit hash) is clear from the diff.

[github-actions]

The difference between the two versions of this Github Actions code is a change in the commit hash for the "actions/checkout" action. The older version uses the commit with hash "1d96c772d19495a3b5c517cd2bc0cb401ea0529f", and the newer version uses "0ad4b8fadaa221de15dcec353f45205ec38ea70b". Both are labelled as version 4 ("# v4"), which creates a potential confusion if their functional behaviors are different.

Whether or not this change introduces an issue depends on how behaviors from these two specific commits of "actions/checkout" differ. If they're actually different versions, updating the label to reflect the actual version would prevent future confusion. Otherwise, differences between them might lead to unexpected behaviors for this workflow.

To avoid such confusion, it's generally recommended to point directly to release tags (like @v2) instead of commit hashes when referencing actions, unless there's a specific need to use certain commits. This makes it clear which version of the action you're using.

[github-actions]

The code diff you posted shows a change in the version of an action, specifically actions/checkout, used in a GitHub Actions workflow. The action version has been changed from one commit hash (1d96c772d19495a3b5c517cd2bc0cb401ea0529f) - likely associated with a particular version, to another commit hash (0ad4b8fadaa221de15dcec353f45205ec38ea70b), but the comment right after each line stating '# v4' hasn't changed.

The potential confusion or irregularity might be that the comment still says 'v4', even though the commit hash (and possibly the version) has changed. Ensure that the new commit hash indeed corresponds to version 4 of the actions/checkout action; if it doesn't, you should correct the comment to reflect the accurate version.

Please note, without checking the corresponding repository and hashes, I cannot validate if those hashes point to specific versions or not. Always refer to the official docs or the repository for the most accurate information.

[github-actions]

The diff shows that the version of "actions/checkout" that your job uses has been changed from one commit hash (1d96c772d19495a3b5c517cd2bc0cb401ea0529f) to another (0ad4b8fadaa221de15dcec353f45205ec38ea70b). However, both hashes are marked as v4. If both these hashes are for the same version, there should be no issues.

Potential points of confusion or concern could include:

• The version tag v4 is not changed between the two hashes. If these hashes refer to different versions of the "actions/checkout" action, this could lead to confusion.
• There's no inherent issue with changing a commit hash, but it's unclear why it was changed without further context. It could be due to new features, bug fixes, or security patches. You should verify that the change in the commit hash doesn't introduce any unexpected changes or incompatibilities.

As long as any potential issues related to the change to the specific commit hash have been considered and addressed, the code appears to be regular and correct.

[github-actions]

This code diff shows a change in a GitHub Actions workflow. The change is in the specific version of the "actions/checkout" action that is being used in the workflow.

The line:

- uses: actions/checkout@1d96c772d19495a3b5c517cd2bc0cb401ea0529f # v4

has been replaced with:

+ uses: actions/checkout@0ad4b8fadaa221de15dcec353f45205ec38ea70b # v4

This means that the particular commit or release of the "actions/checkout" action that is being used has been changed.

One irregularity here might be the comment #v4 at the end of both lines. This is commonly used to denote version numbers, but it's not clear from this diff whether version 4 of the action correlates correctly with either of these commits.

Remember that this hash 1d96c772d19495a3b5c517cd2bc0cb401ea0529f and 0ad4b8fadaa221de15dcec353f45205ec38ea70b are commit hashes, and they should represent specific states of the repository, corresponding to the version provided in the comment (in this case v4). If neither of these hashes correspond to the release tagged as v4, you have a discrepancy between your actual code and your versioning comments.

To make sure there's no confusion, double-check that the commit represented by this hash aligns with version v4 for each hash. This could involve checking the repository where this action is hosted to verify which commit hash corresponds to version 4. You can also validate this with the creator of this repository. If the hash does not match the actual v4 (if such exists), you should update the comment or the hashes to match the correct versions.

[yegor256]

@rultor please, try to merge, since 18 checks have passed

[rultor]

@rultor please, try to merge, since 18 checks have passed

@yegor256 OK, I'll try to merge now. You can check the progress of the merge here

[rultor]

@rultor please, try to merge, since 18 checks have passed

@yegor256 Done! FYI, the full log is here (took me 19min)