projects/events-cash-register

Watch

Fork 0

chore(deps): update ci dependencies #217

Merged

renovate-bot merged 1 commit from renovate-ci into main

2026-08-27 22:23:24 +00:00

renovate-bot commented

2026-08-27 22:20:25 +00:00

Member

This PR contains the following updates:

Package	Change	Type	Update	Pending
@types/node (source)	`26.2.0` → `26.3.0`	devDependencies	minor	`26.4.0`
docker.io/library/node (source)	`26.7.0-alpine` → `26.8.1-alpine`	final	minor
git.zarantonello.dev/projects/events-cash-register-cups (source)	`v2026.01.01.1` → `v2026.08.27.1`		minor
https://git.zarantonello.dev/projects/forgejo-agent	`v1.9.1` → `v1.9.3`	action	patch
pnpm (source)	`11.23.0` → `11.24.0`		minor
pnpm (source)	`11.23.0` → `11.24.0`	packageManager	minor

Release Notes

projects/forgejo-agent (https://git.zarantonello.dev/projects/forgejo-agent)

`v1.9.3`

Compare Source

Bug Fixes

use curl -L to follow redirect to r2 download (#235) (ce9393e)

`v1.9.2`

Compare Source

Bug Fixes

deps: update dependency typebox to v1.3.18 (#233) (d0c49f4)

pnpm/pnpm (pnpm)

`v11.24.0`: pnpm 11.24

Compare Source

Minor Changes

Added global build approvals pnpm/pnpm#14101.

Patch Changes

Fixed pnpm v11 incorrectly reporting confirmModulesPurge as unrecognized when set in pnpm-workspace.yaml. The Rust CLI now identifies the unsupported option as a pnpm v11 setting instead of suggesting an unrelated setting.
pnpm install --frozen-lockfile no longer fails with ERR_PNPM_FROZEN_LOCKFILE_WITH_OUTDATED_LOCKFILE when the pinned pnpm version recorded in pnpm-lock.yaml has to be re-resolved before it can be installed. It runs the pnpm version the lockfile pins and leaves the lockfile unchanged #14124.
Under nodeLinker: hoisted, peer-resolution variants of an injected directory dependency (a file: snapshot) are materialized as separate copies again instead of collapsing onto the first-seen variant. Each copy keeps its own peer-resolved dependency set, so a project pinning one peer version no longer resolves another project's variant — Bit root components with conflicting peers across injected copies rely on this.
Fixed pnpm install --merge-git-branch-lockfiles --frozen-lockfile failing with ERR_PNPM_OUTDATED_LOCKFILE when a branch lockfile predates the removal of a dependency, or its move to another dependency group #13966. A dependency that no project declares anymore is no longer reinstated by the merge, and the packages it was the only path to are dropped with it.
Batch workspace publishing accepts a shared scope-specific credential, rejects mismatched credentials for a registry before publishing, and runs the publish and postpublish scripts after each completed registry group pnpm/pnpm#14101.
The Rust CLI now honors five settings it recognized but ignored: updateNotifier, legacyDirFiltering, initAuthorName / initAuthorEmail / initAuthorUrl, initLicense, and initVersion. pnpm install and pnpm add check once a day for a newer pnpm and print how to get it (turn it off with updateNotifier: false); a {<dir>} filter selector can go back to matching the subtree below the directory with legacyDirFiltering: true; and pnpm init writes the configured author, license, and version into the package.json it scaffolds. PNPM_CONFIG_INIT_VERSION is now read as well.

maxsockets, npm's spelling of maxSockets, is no longer ignored: both spellings are read from pnpm-workspace.yaml, the global config file, the environment, and the command line, in that increasing order of precedence — a value passed on the command line now wins even when the two sides spelled the setting differently.

A lastUpdateCheck timestamp dated in the future — after a clock change, a restored snapshot, or a hand-edited state file — no longer silences the update check until that time comes around.

legacyDirFiltering no longer reaches the workspace-root selectors pnpm generates for itself: the !{<workspace-root>} exclusion a recursive run / exec / add / test appends, and the {<workspace-root>} inclusion --workspace-root appends. Read as subtree matches they named every project below the root, so a recursive command under the setting selected nothing at all, and --workspace-root pulled in every project below the root instead of the root alone #14101.
pnpm install --frozen-lockfile no longer fails when pnpm-lock.yaml records the pinned pnpm version alongside an engine package the running pnpm does not install it from. An entry pinning another version is still refused, and a plain install rewrites the block #14124.

Configuration

📅 Schedule: (UTC)

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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

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

This PR has been generated by Mend Renovate CLI.

This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | Type | Update | Pending | |---|---|---|---|---|---|---| | [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/node) ([source](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node)) | [`26.2.0` → `26.3.0`](https://renovatebot.com/diffs/npm/@types%2fnode/26.2.0/26.3.0) | ![age](https://developer.mend.io/api/mc/badges/age/npm/@types%2fnode/26.3.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@types%2fnode/26.2.0/26.3.0?slim=true) | devDependencies | minor | `26.4.0` | | [docker.io/library/node](https://hub.docker.com/_/node) ([source](https://github.com/nodejs/docker-node)) | `26.7.0-alpine` → `26.8.1-alpine` | ![age](https://developer.mend.io/api/mc/badges/age/docker/docker.io%2flibrary%2fnode/26.8.1?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/docker/docker.io%2flibrary%2fnode/26.7.0/26.8.1?slim=true) | final | minor | | | [git.zarantonello.dev/projects/events-cash-register-cups](https://hub.docker.com/_/alpine) ([source](https://github.com/alpinelinux/docker-alpine)) | `v2026.01.01.1` → `v2026.08.27.1` | ![age](https://developer.mend.io/api/mc/badges/age/docker/git.zarantonello.dev%2fprojects%2fevents-cash-register-cups/v2026.08.27.1?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/docker/git.zarantonello.dev%2fprojects%2fevents-cash-register-cups/v2026.01.01.1/v2026.08.27.1?slim=true) | | minor | | | [https://git.zarantonello.dev/projects/forgejo-agent](https://git.zarantonello.dev/projects/forgejo-agent) | `v1.9.1` → `v1.9.3` | ![age](https://developer.mend.io/api/mc/badges/age/forgejo-tags/projects%2fforgejo-agent/v1.9.3?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/forgejo-tags/projects%2fforgejo-agent/v1.9.1/v1.9.3?slim=true) | action | patch | | | [pnpm](https://pnpm.io) ([source](https://github.com/pnpm/pnpm/tree/HEAD/pnpm11/pnpm)) | `11.23.0` → `11.24.0` | ![age](https://developer.mend.io/api/mc/badges/age/npm/pnpm/11.24.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/pnpm/11.23.0/11.24.0?slim=true) | | minor | | | [pnpm](https://pnpm.io) ([source](https://github.com/pnpm/pnpm/tree/HEAD/pnpm11/pnpm)) | [`11.23.0` → `11.24.0`](https://renovatebot.com/diffs/npm/pnpm/11.23.0/11.24.0) | ![age](https://developer.mend.io/api/mc/badges/age/npm/pnpm/11.24.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/pnpm/11.23.0/11.24.0?slim=true) | packageManager | minor | | --- ### Release Notes <details> <summary>projects/forgejo-agent (https://git.zarantonello.dev/projects/forgejo-agent)</summary> ### [`v1.9.3`](https://git.zarantonello.dev/projects/forgejo-agent/releases/tag/v1.9.3) [Compare Source](https://git.zarantonello.dev/projects/forgejo-agent/compare/v1.9.2...v1.9.3) ##### Bug Fixes - use curl -L to follow redirect to r2 download ([#235](https://git.zarantonello.dev/projects/forgejo-agent/issues/235)) ([ce9393e](https://git.zarantonello.dev/projects/forgejo-agent/commit/ce9393ea3b22d28d8b7ac1b23e9c2e0d5afe5c93)) ### [`v1.9.2`](https://git.zarantonello.dev/projects/forgejo-agent/releases/tag/v1.9.2) [Compare Source](https://git.zarantonello.dev/projects/forgejo-agent/compare/v1.9.1...v1.9.2) ##### Bug Fixes - **deps:** update dependency typebox to v1.3.18 ([#233](https://git.zarantonello.dev/projects/forgejo-agent/issues/233)) ([d0c49f4](https://git.zarantonello.dev/projects/forgejo-agent/commit/d0c49f4198531f3be3e95840f99a3aa50e73abef)) </details> <details> <summary>pnpm/pnpm (pnpm)</summary> ### [`v11.24.0`](https://github.com/pnpm/pnpm/releases/tag/v11.24.0): pnpm 11.24 [Compare Source](https://github.com/pnpm/pnpm/compare/v11.23.0...v11.24.0) ##### Minor Changes - Added global build approvals [pnpm/pnpm#14101](https://github.com/pnpm/pnpm/issues/14101). ##### Patch Changes - Fixed pnpm v11 incorrectly reporting `confirmModulesPurge` as unrecognized when set in `pnpm-workspace.yaml`. The Rust CLI now identifies the unsupported option as a pnpm v11 setting instead of suggesting an unrelated setting. - `pnpm install --frozen-lockfile` no longer fails with `ERR_PNPM_FROZEN_LOCKFILE_WITH_OUTDATED_LOCKFILE` when the pinned pnpm version recorded in `pnpm-lock.yaml` has to be re-resolved before it can be installed. It runs the pnpm version the lockfile pins and leaves the lockfile unchanged [#14124](https://github.com/pnpm/pnpm/issues/14124). - Under `nodeLinker: hoisted`, peer-resolution variants of an injected directory dependency (a `file:` snapshot) are materialized as separate copies again instead of collapsing onto the first-seen variant. Each copy keeps its own peer-resolved dependency set, so a project pinning one peer version no longer resolves another project's variant — Bit root components with conflicting peers across injected copies rely on this. - Fixed `pnpm install --merge-git-branch-lockfiles --frozen-lockfile` failing with `ERR_PNPM_OUTDATED_LOCKFILE` when a branch lockfile predates the removal of a dependency, or its move to another dependency group [#13966](https://github.com/pnpm/pnpm/issues/13966). A dependency that no project declares anymore is no longer reinstated by the merge, and the packages it was the only path to are dropped with it. - Batch workspace publishing accepts a shared scope-specific credential, rejects mismatched credentials for a registry before publishing, and runs the `publish` and `postpublish` scripts after each completed registry group [pnpm/pnpm#14101](https://github.com/pnpm/pnpm/issues/14101). - The Rust CLI now honors five settings it recognized but ignored: `updateNotifier`, `legacyDirFiltering`, `initAuthorName` / `initAuthorEmail` / `initAuthorUrl`, `initLicense`, and `initVersion`. `pnpm install` and `pnpm add` check once a day for a newer pnpm and print how to get it (turn it off with `updateNotifier: false`); a `{<dir>}` filter selector can go back to matching the subtree below the directory with `legacyDirFiltering: true`; and `pnpm init` writes the configured author, license, and version into the `package.json` it scaffolds. `PNPM_CONFIG_INIT_VERSION` is now read as well. `maxsockets`, npm's spelling of `maxSockets`, is no longer ignored: both spellings are read from `pnpm-workspace.yaml`, the global config file, the environment, and the command line, in that increasing order of precedence — a value passed on the command line now wins even when the two sides spelled the setting differently. A `lastUpdateCheck` timestamp dated in the future — after a clock change, a restored snapshot, or a hand-edited state file — no longer silences the update check until that time comes around. `legacyDirFiltering` no longer reaches the workspace-root selectors pnpm generates for itself: the `!{<workspace-root>}` exclusion a recursive `run` / `exec` / `add` / `test` appends, and the `{<workspace-root>}` inclusion `--workspace-root` appends. Read as subtree matches they named every project below the root, so a recursive command under the setting selected nothing at all, and `--workspace-root` pulled in every project below the root instead of the root alone [#14101](https://github.com/pnpm/pnpm/issues/14101). - `pnpm install --frozen-lockfile` no longer fails when `pnpm-lock.yaml` records the pinned pnpm version alongside an engine package the running pnpm does not install it from. An entry pinning another version is still refused, and a plain install rewrites the block [#14124](https://github.com/pnpm/pnpm/issues/14124). </details> --- ### Configuration 📅 **Schedule**: (UTC) - 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. 👻 **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://github.com/renovatebot/renovate/discussions) if that's undesired. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate CLI](https://github.com/renovatebot/renovate).

renovate-bot added 1 commit

2026-08-27 22:20:25 +00:00

chore(deps): update ci dependencies

renovate/stability-days Updates have met minimum release age requirement

Details

check-commitizen.yaml / Check the PR title (pull_request) Successful in 2s

Details

check-formatter.yaml / Checks with formatters (pull_request) Successful in 18s

Details

check-linter.yaml / Checks with linters (pull_request) Successful in 38s

Details

check-syntax.yaml / Checks with static tools (pull_request) Successful in 1m46s