[PR #1] [CLOSED] chore: Configure Renovate #8

Closed
opened 2026-06-08 08:27:10 +00:00 by ryangr0 · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/webgrip/action-typescript-template/pull/1
Author: @Ryangr0
Created: 2/8/2026
Status: Closed

Base: mainHead: renovate/configure


📝 Commits (1)

📊 Changes

1 file changed (+3 additions, -0 deletions)

View changed files

renovate.json (+3 -0)

📄 Description

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

🚦 Renovate will begin keeping your dependencies up-to-date only once you merge or close this Pull Request.


Detected Package Files

  • docker-compose.yml (docker-compose)
  • ops/action/Dockerfile (dockerfile)
  • 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.
  • Apply labels dependencies and {{arg1}} to PRs.

🔡 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): update dependency @​babel/eslint-parser to v7.28.6
  • Schedule: ["at any time"]
  • Branch name: renovate/babel-monorepo
  • Merge into: main
  • Upgrade @babel/eslint-parser to 7.28.6
chore(deps): update npm
  • Schedule: ["at any time"]
  • Branch name: renovate/npm
  • Merge into: main
  • Upgrade @vercel/ncc to 0.38.4
  • Upgrade ts-jest to 29.4.6
  • Upgrade typescript to 5.9.3
chore(deps): update dependency @typescript-eslint/eslint-plugin to v8.54.0
chore(deps): update eslint monorepo to v9.39.2
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-monorepo
  • Merge into: main
  • Upgrade @eslint/js to 9.39.2
  • Upgrade eslint to 9.39.2
chore(deps): update dependency @​stylistic/eslint-plugin to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/major-eslint-stylistic-monorepo
  • Merge into: main
  • Upgrade @stylistic/eslint-plugin to ^5.0.0
chore(deps): update eslint monorepo to v10 (major)
  • Schedule: ["at any time"]
  • Branch name: renovate/major-eslint-monorepo
  • Merge into: main
  • Upgrade @eslint/js to ^10.0.0
  • Upgrade eslint to ^10.0.0
chore(deps): update jest monorepo to v30 (major)
  • Schedule: ["at any time"]
  • Branch name: renovate/major-jest-monorepo
  • Merge into: main
  • Upgrade @types/jest to ^30.0.0
  • Upgrade jest to ^30.0.0
fix(deps): update dependency @​actions/core to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/major-npm
  • Merge into: main
  • Upgrade @actions/core to ^3.0.0

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


🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/webgrip/action-typescript-template/pull/1 **Author:** [@Ryangr0](https://github.com/Ryangr0) **Created:** 2/8/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `renovate/configure` --- ### 📝 Commits (1) - [`44a3941`](https://github.com/webgrip/action-typescript-template/commit/44a39412a7c187095934b3709605ce2e11e642b0) Add renovate.json ### 📊 Changes **1 file changed** (+3 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `renovate.json` (+3 -0) </details> ### 📄 Description Welcome to [Renovate](https://redirect.github.com/renovatebot/renovate)! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin. 🚦 Renovate will begin keeping your dependencies up-to-date only once you merge or close this Pull Request. --- ### Detected Package Files * `docker-compose.yml` (docker-compose) * `ops/action/Dockerfile` (dockerfile) * `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. - Apply labels `dependencies` and `{{arg1}}` to PRs. 🔡 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): update dependency @&#8203;babel/eslint-parser to v7.28.6</summary> - Schedule: ["at any time"] - Branch name: `renovate/babel-monorepo` - Merge into: `main` - Upgrade [@babel/eslint-parser](https://redirect.github.com/babel/babel) to `7.28.6` </details> <details> <summary>chore(deps): update npm</summary> - Schedule: ["at any time"] - Branch name: `renovate/npm` - Merge into: `main` - Upgrade [@vercel/ncc](https://redirect.github.com/vercel/ncc) to `0.38.4` - Upgrade [ts-jest](https://redirect.github.com/kulshekhar/ts-jest) to `29.4.6` - Upgrade [typescript](https://redirect.github.com/microsoft/TypeScript) to `5.9.3` </details> <details> <summary>chore(deps): update dependency @typescript-eslint/eslint-plugin to v8.54.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/typescript-eslint-monorepo` - Merge into: `main` - Upgrade [@typescript-eslint/eslint-plugin](https://redirect.github.com/typescript-eslint/typescript-eslint) to `8.54.0` </details> <details> <summary>chore(deps): update eslint monorepo to v9.39.2</summary> - Schedule: ["at any time"] - Branch name: `renovate/eslint-monorepo` - Merge into: `main` - Upgrade [@eslint/js](https://redirect.github.com/eslint/eslint) to `9.39.2` - Upgrade [eslint](https://redirect.github.com/eslint/eslint) to `9.39.2` </details> <details> <summary>chore(deps): update dependency @&#8203;stylistic/eslint-plugin to v5</summary> - Schedule: ["at any time"] - Branch name: `renovate/major-eslint-stylistic-monorepo` - Merge into: `main` - Upgrade [@stylistic/eslint-plugin](https://redirect.github.com/eslint-stylistic/eslint-stylistic) to `^5.0.0` </details> <details> <summary>chore(deps): update eslint monorepo to v10 (major)</summary> - Schedule: ["at any time"] - Branch name: `renovate/major-eslint-monorepo` - Merge into: `main` - Upgrade [@eslint/js](https://redirect.github.com/eslint/eslint) to `^10.0.0` - Upgrade [eslint](https://redirect.github.com/eslint/eslint) to `^10.0.0` </details> <details> <summary>chore(deps): update jest monorepo to v30 (major)</summary> - Schedule: ["at any time"] - Branch name: `renovate/major-jest-monorepo` - Merge into: `main` - Upgrade [@types/jest](https://redirect.github.com/DefinitelyTyped/DefinitelyTyped) to `^30.0.0` - Upgrade [jest](https://redirect.github.com/jestjs/jest) to `^30.0.0` </details> <details> <summary>fix(deps): update dependency @&#8203;actions/core to v3</summary> - Schedule: ["at any time"] - Branch name: `renovate/major-npm` - Merge into: `main` - Upgrade [@actions/core](https://redirect.github.com/actions/toolkit) to `^3.0.0` </details> 🚸 Branch 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](https://docs.renovatebot.com/), particularly the Getting Started section. If you need any further assistance then you can also [request help here](https://redirect.github.com/renovatebot/renovate/discussions). --- This PR has been generated by [Renovate Bot](https://redirect.github.com/renovatebot/renovate). <!--renovate-config-hash:94693a990c975907e7f13da3309b9d56ba02b3983519b41786edf5cf031e457c--> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
ryangr0 2026-06-08 08:27:10 +00:00
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
webgrip/action-typescript-template#8
No description provided.