Configure Renovate

[renovate]

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.

📚 See our Reading List for relevant documentation you may be interested in reading.

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to renovate.json in this branch. Renovate will update the Pull Request description the next time it runs.

---

Detected Package Files

• .github/workflows/ci.yml (github-actions)
• .github/workflows/pkg-pr-new.yml (github-actions)
• package.json (npm)

Configuration Summary

Based on the default config's presets, Renovate will:

• Start dependency updates only once this onboarding PR is merged
• Hopefully safe environment variables to allow users to configure.
• Show all Merge Confidence badges for pull requests.
• Enable Renovate Dependency Dashboard creation.
• Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
• Ignore node_modules, bower_components, vendor and various test/tests (except for nuget) directories.
• Group known monorepo packages together.
• Use curated list of recommended non-monorepo package groupings.
• Show only the Age and Confidence Merge Confidence badges for pull requests.
• Apply crowd-sourced package replacement rules.
• Apply crowd-sourced workarounds for known problems with packages.
• Ensure that every dependency pinned by digest and sourced from Forgejo contains a link to the commit-to-commit diff
• Ensure that every dependency pinned by digest and sourced from Gitea contains a link to the commit-to-commit diff
• Ensure that every dependency pinned by digest and sourced from GitHub.com and Github enterprise contains a link to the commit-to-commit diff
• Ensure that every dependency pinned by digest and sourced from GitLab.com contains a link to the commit-to-commit diff
• Correctly link to the source code for golang.org/x packages
• Link to pkg.go.dev/... for golang.org/x packages' title
• Provide a link to octochangelog's improved breakdown for Renovate's changelogs

---

What to Expect

With your current configuration, Renovate will create 10 Pull Requests, up to a maximum of 14 over time (see docs for prConcurrentLimit):

Update dependency effect to v4.0.2

• Schedule: ["at any time"]
• Branch name: renovate/effect-4.x
• Merge into: main
• Upgrade effect to sha512-YeYnLqSFrL4+tCOXRrfNP03w8FILoF/wDl+ukraJAGzXrjcS383W7LAAvGBbLatEyktmLxRq+9xJinx7QzXW5A==

Update dependency pkg-pr-new to v0.0.91

• Schedule: ["at any time"]
• Branch name: renovate/pkg-pr-new-0.x
• Merge into: main
• Upgrade pkg-pr-new to sha512-FQPmjspKRKYV4MlHQnun9snJqlYm6Yhmo12x1O3pgE2Akim/y/BZjMOppK//BFdh222WOj6WGqlmeZfrtUtfgQ==

Update dependency publint to v0.3.25

• Schedule: ["at any time"]
• Branch name: renovate/publint-0.x-lockfile
• Merge into: main
• Upgrade publint to 0.3.25

Update dependency tstyche to v7.2.5

• Schedule: ["at any time"]
• Branch name: renovate/tstyche-7.x-lockfile
• Merge into: main
• Upgrade tstyche to 7.2.5

Update dependency @​rstest/core to ^0.12.0

• Schedule: ["at any time"]
• Branch name: renovate/rstest-core-0.x
• Merge into: main
• Upgrade @rstest/core to sha512-l548qraJA1ymaSRhftgl++HtRf4E5l0Hm8YbzcsrH0t8XIOSpAiXyhgJpeHuyM50fKcNkt1nnS532Y7QV1iwcQ==

Update dependency @​types/node to v26.6.5

• Schedule: ["at any time"]
• Branch name: renovate/node-26.x-lockfile
• Merge into: main
• Upgrade @types/node to 26.6.5

Update dependency tsdown to ^0.23.0

• Schedule: ["at any time"]
• Branch name: renovate/tsdown-0.x
• Merge into: main
• Upgrade tsdown to sha512-MSC2WSOts3in95J334/VIS7KPfor3eCSvndJ6KdoVj9Aak9Kh1aNfz9ws5owhdukuTNSXRdfkPEzA/ihpDD6SA==

Update pnpm to v10.34.6

• Schedule: ["at any time"]
• Branch name: renovate/pnpm-10.x
• Merge into: main
• Upgrade pnpm to sha512-fhrmaoOpFDwRjMGUTzfMTyuKzd7aSwAc+niQj25G5F4VKSc5ymydAmQmzHV+kxjMmMVVHWoWwWUJewAouoe05g==

Update actions/checkout action to v7

• Schedule: ["at any time"]
• Branch name: renovate/actions-checkout-7.x
• Merge into: main
• Upgrade actions/checkout to v7

Update actions/setup-node action to v7

• Schedule: ["at any time"]
• Branch name: renovate/actions-setup-node-7.x
• Merge into: main
• Upgrade actions/setup-node to v7

Update dependency node to v24

• Schedule: ["at any time"]
• Branch name: renovate/node-24.x
• Merge into: main
• Upgrade node to 24

Update dependency typescript to v7

• Schedule: ["at any time"]
• Branch name: renovate/typescript-7.x
• Merge into: main
• Upgrade typescript to sha512-8FYau96o3NKOhbjKi/qNvG/W5jhzxkbdm5sj9AbZ/5T5sWqn3hJgLfGx27sRKZWTvyzCP8dLRBTf5tBTSRVUNA==

Update pnpm to v12

• Schedule: ["at any time"]
• Branch name: renovate/pnpm-12.x
• Merge into: main
• Upgrade pnpm to sha512-JaUWUqGWeFr18ovabf6NxYLr76SsHRgCIc4TkCMcX7dmN4IupLbkYzznSs3LCnf3Ja8RutOBd/3t2u6BipVcuQ==

Update pnpm/action-setup action to v6

• Schedule: ["at any time"]
• Branch name: renovate/pnpm-action-setup-6.x
• Merge into: main
• Upgrade pnpm/action-setup to v6

🚸 PR creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or overwhelm the project. See docs for prHourlyLimit for details.

---

❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section.
If you need any further assistance then you can also request help here.

---

This PR was generated by Mend Renovate. View the repository job log.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 27d69fe

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/effect-rstest@27d69fe

commit: 27d69fe