search

yegor256 / yb-book

This LaTeX class I'm using for all my books I publish on Amazon
https://www.yegor256.com/books.html
MIT License
11 stars 0 forks source link

Update teatimeguest/setup-texlive-action action to v3 #18

Closed renovate[bot] closed 1 year ago

renovate[bot] commented 1 year ago

Mend Renovate

This PR contains the following updates:

Package Type Update Change
teatimeguest/setup-texlive-action action major v2.6.3 -> v3.0.0

[!WARNING] Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

Release Notes

teatimeguest/setup-texlive-action (teatimeguest/setup-texlive-action) ### [`v3.0.0`](https://togithub.com/teatimeguest/setup-texlive-action/releases/tag/v3.0.0) [Compare Source](https://togithub.com/teatimeguest/setup-texlive-action/compare/v2.6.3...v3.0.0) ##### Breaking Changes - Use Node.js v20 as runtime. With Node.js v16 having reached its [end-of-life](https://nodejs.org/en/blog/announcements/nodejs16-eol) and GitHub Actions beginning the [transition to Node.js v20](https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/), the action has upgraded its default runtime to Node.js v20. If you are using a self-hosted runner, update it to [v2.308.0](https://togithub.com/actions/runner/releases/tag/v2.308.0) or later to ensure `node20` runtime functionality. - Change the condition under which `cache-hit` is set to `true`. To be more consistent with official actions such as [`actions/cache`](https://docs.github.com/en/actions/using-workflows/caching-dependencies-to-speed-up-workflows#cache-hits-and-misses), the `cache-hit` output is now set to `true` only if a cache is found that exactly matches the specified version and packages. To simply check if a cache was found, use `cache-restored` instead: ```yaml - name: Setup TeX Live id: setup uses: teatimeguest/setup-texlive-action@v3 - if: fromJSON(steps.setup.outputs.cache-restored) run: echo 'A cache has been found' ``` - Change the default installation prefix to `$RUNNER_TEMP/setup-texlive-action`. - Change the environment variable for updating cache to `SETUP_TEXLIVE_ACTION_FORCE_UPDATE_CACHE`. Actions published on [GitHub Marketplace](https://togithub.com/marketplace?type=actions) have unique names defined in the metadata file `action.yml`. To minimize conflicts with other actions, the action name (`setup-texlive-action`) is now used for the following things: - Directory name of the default installation prefix: ```diff - $RUNNER_TEMP/setup-texlive + $RUNNER_TEMP/setup-texlive-action ``` - Environment variable name: ```diff - SETUP_TEXLIVE_FORCE_UPDATE_CACHE + SETUP_TEXLIVE_ACTION_FORCE_UPDATE_CACHE ``` - Cache keys. - Change the default texmf user directories. As with the [portable installation](https://tug.org/texlive/doc/texlive-en/texlive-en.html#tlportable) of the official installer, `TEXMFHOME`, `TEXMFCONFIG`, and `TEXMFVAR` are now set by default to be the same as `TEXMFLOCAL`, `TEXMFSYSCONFIG`, and `TEXMFSYSVAR`, respectively. To emulate the previous behavior, use environment variables to explicitly specify the user directories: ```yaml - name: Setup TeX Live uses: teatimeguest/setup-texlive-action@v3 env: TEXLIVE_INSTALL_TEXMFHOME: >- ~/texmf TEXLIVE_INSTALL_TEXMFCONFIG: >- ~/.local/texlive//texmf-config TEXLIVE_INSTALL_TEXMFVAR: >- ~/.local/texlive//texmf-var ``` - The `package-file` input now accepts [glob patterns](https://togithub.com/actions/toolkit/tree/main/packages/glob#patterns) for specifying multiple files. Since special characters such as `*` and `?` will need to be escaped, this might break existing workflow behavior. ##### Full Commit SHA ```sha1 c696dd935e72a771c4f5da39fc3ea1d391b9d408 ``` ##### Features - the `package-file` input now accepts glob patterns - add `cache-restored` output ##### Dependency Updates - bump [@​actions/http-client](https://togithub.com/actions/http-client) from 2.1.1 to 2.2.0 ([#​263](https://togithub.com/teatimeguest/setup-texlive-action/issues/263))

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.

This PR has been generated by Mend Renovate. View repository job log here.

yegor256 commented 1 year ago

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

rultor commented 1 year ago

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

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

rultor commented 1 year ago

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

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