chore(deps): update teatimeguest/setup-texlive-action action to v3.3.0

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
teatimeguest/setup-texlive-action	action	minor	v3.2.1 -> v3.3.0

---

Release Notes

teatimeguest/setup-texlive-action (teatimeguest/setup-texlive-action)

v3.3.0

Compare Source

Full Commit SHA

e69e0852590264df4a35dbc6cc94009a2466a562

Features

• 5f5372b check and use the remote version by default if repository is set (#​283)

Bug Fixes

• a862468 address the certification problem (#​304)

Performance Improvements

• 0459d55 add source map support

Dependency Updates

• 1599cad bump undici from 5.28.3 to 5.28.4 (#​293)
• 85524ce bump ts-pattern from 5.0.8 to 5.1.0 (#​295)
• 664f4a2 bump ts-pattern from 5.1.0 to 5.1.1 (#​297)
• 37b69eb bump temporal-polyfill from 0.2.3 to 0.2.4 (#​298)
• ed98b31 bump semver from 7.6.0 to 7.6.2 (#​299)
• f0dcfc5 bump ts-pattern from 5.1.1 to 5.1.2 (#​300)
• 2f30ae1 bump temporal-polyfill from 0.2.4 to 0.2.5 (#​301)
• f0b800b bump tslib from 2.6.2 to 2.6.3 (#​302)
• d1e1416 bump ts-pattern from 5.1.2 to 5.2.0 (#​303)

---

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.

[github-actions]

The diff you've shown changes the version of teatimeguest/setup-texlive-action used within a GitHub Actions workflow.

It moves from v3.2.1 to v3.3.0. It's a typical change in software projects to upgrade dependencies to avail of new features, improvements, or bug fixes. Ideally, this kind of change should have been properly tested to avoid potential breaking changes introduced between these versions.

However, there's no syntactical irregularity or error visible in the provided code snippet.

[github-actions]

From the provided code diff, it appears that there is no confusion. It shows a change in GitHub Actions workflow file that switches from using version v3.2.1 to version v3.3.0 of the teatimeguest/setup-texlive-action. As long as v3.3.0 of setup-texlive-action exists and has no major changes or requirements that would break your current build process, this update should work correctly.

[github-actions]

The provided diff indicates that one line of code was altered in a configuration file for running continuous integration jobs. No conflicts or irregularities are present within the presented changes.

The replaced line indicates an update from version 3.2.1 to 3.3.0 of a GitHub action called "setup-texlive-action" from the user "teatimeguest". This likely indicates incorporating updates, improvements, or fixes from the newer version of the action into the build process. As long as version 3.3.0 of 'teatimeguest/setup-texlive-action' exists and works as expected, there should be no issues.

Remember, updating versions may introduce new features but could also contain new unexpected behaviors if not tested properly, so it's important to verify that the new version integrates well with your existing set-up after applying the changes.

[github-actions]

Your code highlights a change in the GitHub Actions workflow. The "teatimeguest/setup-texlive-action" version has been changed from v3.2.1 to v3.3.0.

This is not irregular or particularly confusing; it simply means that the workflow is using a newer version of the "setup-texlive-action".

However, one potential point of confusion or error could be if the newer version (v3.3.0) of "teatimeguest/setup-texlive-action" has different behaviours or breaking changes from the previous version (v3.2.1). This would require checking the release notes or documentation of the newer version for any breaking changes or alterations in behavior.

[yegor256]

@rultor merge

[rultor]

@rultor merge

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

[rultor]

@rultor merge

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