Seuma/forgejo-integration

Fork 0

chore: Configure Renovate #20

Open

RenovateBot wants to merge 2 commits from renovate/configure into main

RenovateBot commented

2026-03-03 22:59:31 +00:00

Collaborator

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.

Detected Package Files

package.json (npm)

Configuration Summary

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

Start dependency updates only once this onboarding PR is merged
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 GitHub.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
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 GitHub.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

🔡 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.

What to Expect

With your current configuration, Renovate will create 8 Pull Requests:

chore(deps): replace dependency npm-run-all with npm-run-all2 ^5.0.0

Schedule: ["at any time"]
Branch name: renovate/npm-run-all-replacement
Merge into: main
Upgrade npm-run-all to ^5.0.0

chore(deps): update dependency @types/node to v22.19.15

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

chore(deps): update dependency esbuild to v0.27.4

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

chore(deps): update dependency eslint to v9.39.4

Schedule: ["at any time"]
Branch name: renovate/eslint-monorepo
Merge into: main
Upgrade eslint to 9.39.4

chore(deps): update dependency @types/vscode to v1.110.0

Schedule: ["at any time"]
Branch name: renovate/vscode-1.x-lockfile
Merge into: main
Upgrade @types/vscode to 1.110.0

chore(deps): update dependency typescript-eslint to v8.57.1

Schedule: ["at any time"]
Branch name: renovate/typescript-eslint-monorepo
Merge into: main
Upgrade typescript-eslint to 8.57.1

chore(deps): update dependency @types/node to v24

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

chore(deps): update dependency eslint to v10

Schedule: ["at any time"]
Branch name: renovate/major-eslint-monorepo
Merge into: main
Upgrade eslint to ^10.0.0

❓ 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 has been generated by Renovate Bot.

Welcome to [Renovate](https://github.com/renovatebot/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. --- ### Detected Package Files * `package.json` (npm) ### Configuration Summary Based on the default config's presets, Renovate will: - Start dependency updates only once this onboarding PR is merged - 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 GitHub.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 - 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 GitHub.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 🔡 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. --- ### What to Expect With your current configuration, Renovate will create 8 Pull Requests: <details> <summary>chore(deps): replace dependency npm-run-all with npm-run-all2 ^5.0.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/npm-run-all-replacement` - Merge into: `main` - Upgrade [npm-run-all](https://github.com/mysticatea/npm-run-all) to `^5.0.0` </details> <details> <summary>chore(deps): update dependency @types/node to v22.19.15</summary> - Schedule: ["at any time"] - Branch name: `renovate/node-22.x-lockfile` - Merge into: `main` - Upgrade [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped) to `22.19.15` </details> <details> <summary>chore(deps): update dependency esbuild to v0.27.4</summary> - Schedule: ["at any time"] - Branch name: `renovate/esbuild-0.x-lockfile` - Merge into: `main` - Upgrade [esbuild](https://github.com/evanw/esbuild) to `0.27.4` </details> <details> <summary>chore(deps): update dependency eslint to v9.39.4</summary> - Schedule: ["at any time"] - Branch name: `renovate/eslint-monorepo` - Merge into: `main` - Upgrade [eslint](https://github.com/eslint/eslint) to `9.39.4` </details> <details> <summary>chore(deps): update dependency @types/vscode to v1.110.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/vscode-1.x-lockfile` - Merge into: `main` - Upgrade [@types/vscode](https://github.com/DefinitelyTyped/DefinitelyTyped) to `1.110.0` </details> <details> <summary>chore(deps): update dependency typescript-eslint to v8.57.1</summary> - Schedule: ["at any time"] - Branch name: `renovate/typescript-eslint-monorepo` - Merge into: `main` - Upgrade [typescript-eslint](https://github.com/typescript-eslint/typescript-eslint) to `8.57.1` </details> <details> <summary>chore(deps): update dependency @types/node to v24</summary> - Schedule: ["at any time"] - Branch name: `renovate/node-24.x` - Merge into: `main` - Upgrade [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped) to `24.x` </details> <details> <summary>chore(deps): update dependency eslint to v10</summary> - Schedule: ["at any time"] - Branch name: `renovate/major-eslint-monorepo` - Merge into: `main` - Upgrade [eslint](https://github.com/eslint/eslint) to `^10.0.0` </details> --- ❓ Got questions? Check out Renovate's [Docs](https://docs.renovatebot.com/), particularly the Getting Started section. If you need any further assistance then you can also [request help here](https://github.com/renovatebot/renovate/discussions). --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).

RenovateBot added 1 commit

2026-03-03 22:59:31 +00:00

Add renovate.json a420abf5e7

Seuma added 1 commit

2026-03-03 23:16:12 +00:00

Merge branch 'main' into renovate/configure 7dd1fb7ba1

This pull request can be merged automatically.

You are not authorized to merge this pull request.

View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u origin renovate/configure:renovate/configure

git switch renovate/configure

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main

git merge --no-ff renovate/configure

git switch renovate/configure

git rebase main

git switch main

git merge --ff-only renovate/configure

git switch renovate/configure

git rebase main

git switch main

git merge --no-ff renovate/configure

git switch main

git merge --squash renovate/configure