chore(deps): update dependency tsx to ^4.23.7 #49

2026-08-05T11:00:33+02:00

remco commented

2026-08-05 11:00:33 +02:00

This PR contains the following updates:

Package	Type	Update	Change
tsx (source)	devDependencies	patch	`^4.23.6` -> `^4.23.7`

❗ Important

Release Notes retrieval for this PR were skipped because no github.com credentials were available.
If you are self-hosted, please see this instruction.

Configuration

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

🚦 Automerge: Enabled.

♻ 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 Renovate Bot.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [tsx](https://tsx.hirok.io) ([source](https://github.com/privatenumber/tsx)) | devDependencies | patch | [`^4.23.6` -> `^4.23.7`](https://renovatebot.com/diffs/npm/tsx/4.23.6/4.23.7) | > :exclamation: **Important** > > Release Notes retrieval for this PR were skipped because no github.com credentials were available. > If you are self-hosted, please see [this instruction](https://github.com/renovatebot/renovate/blob/master/docs/usage/examples/self-hosting.md#githubcom-token-for-release-notes). --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Enabled. ♻ **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 [Renovate Bot](https://github.com/renovatebot/renovate).

remco added 1 commit 2026-08-05 11:00:33 +02:00

chore(deps): update dependency tsx to ^4.23.7

renovate/artifacts Artifact file update failure

CI / check (push) Failing after 7s

Details

CI / release (push) Skipped

Details

CI / deploy (push) Skipped

Details

CI / check (pull_request) Failing after 8s

Details

CI / release (pull_request) Skipped

Details

CI / deploy (pull_request) Skipped

Details

ac9b3e3cb5

remco scheduled this pull request to auto merge when all checks succeed 2026-08-05 11:00:34 +02:00

remco commented

2026-08-05 11:00:35 +02:00

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml

.                                        | [WARN] Unsupported engine: wanted: {"node":">=26"} (current: {"node":"v22.23.2","pnpm":"11.20.0"})
? Verifying lockfile against supply-chain policies (522 entries)...
✗ Lockfile failed supply-chain policy check (522 entries in 5.3s)
[ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification:
  [email protected] was published at 2026-08-05T01:17:31.000Z, within the minimumReleaseAge cutoff (2026-08-04T09:00:25.982Z)

The lockfile contains entries that the active policies reject. This can mean the lockfile is stale, or that someone committed a lockfile that bypassed the policy locally — inspect recent changes to pnpm-lock.yaml before trusting it. If the changes look expected, run "pnpm clean --lockfile" and then "pnpm install" to rebuild from a fresh resolution. Alternatively, relax the policy that flagged them.

### ⚠️ Artifact update problem Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is. ♻ Renovate will retry this branch, including artifacts, only when one of the following happens: - any of the package files in this branch needs updating, or - the branch becomes conflicted, or - you click the rebase/retry checkbox if found above, or - you rename this PR's title to start with "rebase!" to trigger it manually The artifact failure details are included below: ##### File name: pnpm-lock.yaml ``` . | [WARN] Unsupported engine: wanted: {"node":">=26"} (current: {"node":"v22.23.2","pnpm":"11.20.0"}) ? Verifying lockfile against supply-chain policies (522 entries)... ✗ Lockfile failed supply-chain policy check (522 entries in 5.3s) [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification: [email protected] was published at 2026-08-05T01:17:31.000Z, within the minimumReleaseAge cutoff (2026-08-04T09:00:25.982Z) The lockfile contains entries that the active policies reject. This can mean the lockfile is stale, or that someone committed a lockfile that bypassed the policy locally — inspect recent changes to pnpm-lock.yaml before trusting it. If the changes look expected, run "pnpm clean --lockfile" and then "pnpm install" to rebuild from a fresh resolution. Alternatively, relax the policy that flagged them. ```

remco merged commit ac9b3e3cb5 into main

2026-08-05 11:00:36 +02:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: remco/EpicNext-Cms#49