Trez/actions-ansi-to-html
4
0
Fork 0
Code Issues 1 Pull Requests 1 Actions 1 Packages Projects Releases 4 Wiki Activity

chore: Configure Renovate #1

Merged
Trez.One merged 2 commits from renovate/configure into main 2025-11-10 17:23:45 -05:00
Conversation 0 Commits 2 Files Changed 1
+7
renovate-bot commented 2025-11-10 17:10:34 -05:00
Member
Copy Link
Copy Source

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

  • 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.
  • Enable Renovate Dependency Dashboard creation.
  • 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.
  • Raise a PR first before any automerging.
  • Automerge digest upgrades if they pass tests.
  • Automerge patch upgrades if they pass tests.
  • Require all status checks to pass before any automerging.
  • Use semantic prefixes for commit messages and PR titles.
  • Removes rate limit for PR creation per hour.
  • Limit to maximum 10 open PRs at any time.
  • Pin Docker digests.
  • Convert pinned GitHub Action digests to SemVer.
  • Enable Docker Compose image updating.
  • Schedule during typical non-office hours on weekdays (i.e., 10 PM - 5 AM) and anytime on weekends.
  • Rebase existing PRs any time the base branch has been updated.
  • Separate each minor version of dependencies into individual branches/PRs.
  • Separate patch and minor releases of dependencies into separate PRs.
  • Presets for Docker Hosts and Git Actions
  • Run Renovate on following schedule: * 0-4,22-23 * * 1-5,* * * * 0,6

🔡 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 11 Pull Requests:

🔧 Renovate: Update (patch) npm/@​types/node to 18.7.23 to v18.7.23
  • Schedule: ["* 0-4,22-23 * * 1-5","* * * * 0,6"]
  • Branch name: renovate/npm-types-node-18-7-23
  • Merge into: main
  • Upgrade @types/node to 18.7.23
🔧 Renovate: Update (minor) npm/@​types/node to 18.8.5 to v18.8.5
  • Schedule: ["* 0-4,22-23 * * 1-5","* * * * 0,6"]
  • Branch name: renovate/npm-types-node-18-8-5
  • Merge into: main
  • Upgrade @types/node to 18.8.5
🔧 Renovate: Update (minor) npm/@​types/node to 18.11.19 to v18.11.19
  • Schedule: ["* 0-4,22-23 * * 1-5","* * * * 0,6"]
  • Branch name: renovate/npm-types-node-18-11-19
  • Merge into: main
  • Upgrade @types/node to 18.11.19
🔧 Renovate: Update (minor) npm/@​types/node to 18.13.0 to v18.13.0
  • Schedule: ["* 0-4,22-23 * * 1-5","* * * * 0,6"]
  • Branch name: renovate/npm-types-node-18-13-0
  • Merge into: main
  • Upgrade @types/node to 18.13.0
🔧 Renovate: Update (minor) npm/@​types/node to 18.14.6 to v18.14.6
  • Schedule: ["* 0-4,22-23 * * 1-5","* * * * 0,6"]
  • Branch name: renovate/npm-types-node-18-14-6
  • Merge into: main
  • Upgrade @types/node to 18.14.6
🔧 Renovate: Update (minor) npm/@​types/node to 18.15.13 to v18.15.13
  • Schedule: ["* 0-4,22-23 * * 1-5","* * * * 0,6"]
  • Branch name: renovate/npm-types-node-18-15-13
  • Merge into: main
  • Upgrade @types/node to 18.15.13
🔧 Renovate: Update (minor) npm/@​types/node to 18.16.20 to v18.16.20
  • Schedule: ["* 0-4,22-23 * * 1-5","* * * * 0,6"]
  • Branch name: renovate/npm-types-node-18-16-20
  • Merge into: main
  • Upgrade @types/node to 18.16.20
🔧 Renovate: Update (minor) npm/@​types/node to 18.17.19 to v18.17.19
  • Schedule: ["* 0-4,22-23 * * 1-5","* * * * 0,6"]
  • Branch name: renovate/npm-types-node-18-17-19
  • Merge into: main
  • Upgrade @types/node to 18.17.19
🔧 Renovate: Update (minor) npm/@​types/node to 18.18.14 to v18.18.14
  • Schedule: ["* 0-4,22-23 * * 1-5","* * * * 0,6"]
  • Branch name: renovate/npm-types-node-18-18-14
  • Merge into: main
  • Upgrade @types/node to 18.18.14
🔧 Renovate: Update (minor) npm/@​types/node to 18.19.130 to v18.19.130
  • Schedule: ["* 0-4,22-23 * * 1-5","* * * * 0,6"]
  • Branch name: renovate/npm-types-node-18-19-130
  • Merge into: main
  • Upgrade @types/node to 18.19.130
🔧 Renovate: Update (major) npm/@​types/node to 24.10.0 to v24
  • Schedule: ["* 0-4,22-23 * * 1-5","* * * * 0,6"]
  • Branch name: renovate/npm-types-node-24-10-0
  • Merge into: main
  • Upgrade @types/node to ^24.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. 🚦 Renovate will begin keeping your dependencies up-to-date only once you merge or close this Pull Request. --- ### 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. - Enable Renovate Dependency Dashboard creation. - 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. - Raise a PR first before any automerging. - Automerge `digest` upgrades if they pass tests. - Automerge `patch` upgrades if they pass tests. - Require all status checks to pass before any automerging. - Use semantic prefixes for commit messages and PR titles. - Removes rate limit for PR creation per hour. - Limit to maximum 10 open PRs at any time. - Pin Docker digests. - Convert pinned GitHub Action digests to SemVer. - Enable Docker Compose image updating. - Schedule during typical non-office hours on weekdays (i.e., 10 PM - 5 AM) and anytime on weekends. - Rebase existing PRs any time the base branch has been updated. - Separate each `minor` version of dependencies into individual branches/PRs. - Separate `patch` and `minor` releases of dependencies into separate PRs. - Presets for Docker Hosts and Git Actions - Run Renovate on following schedule: * 0-4,22-23 * * 1-5,* * * * 0,6 🔡 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 11 Pull Requests: <details> <summary>🔧 Renovate: Update (patch) npm/@&#8203;types/node to 18.7.23 to v18.7.23</summary> - Schedule: ["* 0-4,22-23 * * 1-5","* * * * 0,6"] - Branch name: `renovate/npm-types-node-18-7-23` - Merge into: `main` - Upgrade [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped) to `18.7.23` </details> <details> <summary>🔧 Renovate: Update (minor) npm/@&#8203;types/node to 18.8.5 to v18.8.5</summary> - Schedule: ["* 0-4,22-23 * * 1-5","* * * * 0,6"] - Branch name: `renovate/npm-types-node-18-8-5` - Merge into: `main` - Upgrade [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped) to `18.8.5` </details> <details> <summary>🔧 Renovate: Update (minor) npm/@&#8203;types/node to 18.11.19 to v18.11.19</summary> - Schedule: ["* 0-4,22-23 * * 1-5","* * * * 0,6"] - Branch name: `renovate/npm-types-node-18-11-19` - Merge into: `main` - Upgrade [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped) to `18.11.19` </details> <details> <summary>🔧 Renovate: Update (minor) npm/@&#8203;types/node to 18.13.0 to v18.13.0</summary> - Schedule: ["* 0-4,22-23 * * 1-5","* * * * 0,6"] - Branch name: `renovate/npm-types-node-18-13-0` - Merge into: `main` - Upgrade [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped) to `18.13.0` </details> <details> <summary>🔧 Renovate: Update (minor) npm/@&#8203;types/node to 18.14.6 to v18.14.6</summary> - Schedule: ["* 0-4,22-23 * * 1-5","* * * * 0,6"] - Branch name: `renovate/npm-types-node-18-14-6` - Merge into: `main` - Upgrade [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped) to `18.14.6` </details> <details> <summary>🔧 Renovate: Update (minor) npm/@&#8203;types/node to 18.15.13 to v18.15.13</summary> - Schedule: ["* 0-4,22-23 * * 1-5","* * * * 0,6"] - Branch name: `renovate/npm-types-node-18-15-13` - Merge into: `main` - Upgrade [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped) to `18.15.13` </details> <details> <summary>🔧 Renovate: Update (minor) npm/@&#8203;types/node to 18.16.20 to v18.16.20</summary> - Schedule: ["* 0-4,22-23 * * 1-5","* * * * 0,6"] - Branch name: `renovate/npm-types-node-18-16-20` - Merge into: `main` - Upgrade [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped) to `18.16.20` </details> <details> <summary>🔧 Renovate: Update (minor) npm/@&#8203;types/node to 18.17.19 to v18.17.19</summary> - Schedule: ["* 0-4,22-23 * * 1-5","* * * * 0,6"] - Branch name: `renovate/npm-types-node-18-17-19` - Merge into: `main` - Upgrade [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped) to `18.17.19` </details> <details> <summary>🔧 Renovate: Update (minor) npm/@&#8203;types/node to 18.18.14 to v18.18.14</summary> - Schedule: ["* 0-4,22-23 * * 1-5","* * * * 0,6"] - Branch name: `renovate/npm-types-node-18-18-14` - Merge into: `main` - Upgrade [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped) to `18.18.14` </details> <details> <summary>🔧 Renovate: Update (minor) npm/@&#8203;types/node to 18.19.130 to v18.19.130</summary> - Schedule: ["* 0-4,22-23 * * 1-5","* * * * 0,6"] - Branch name: `renovate/npm-types-node-18-19-130` - Merge into: `main` - Upgrade [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped) to `18.19.130` </details> <details> <summary>🔧 Renovate: Update (major) npm/@&#8203;types/node to 24.10.0 to v24</summary> - Schedule: ["* 0-4,22-23 * * 1-5","* * * * 0,6"] - Branch name: `renovate/npm-types-node-24-10-0` - Merge into: `main` - Upgrade [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped) to `^24.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). <!--renovate-config-hash:68b5a08503a4be63067cf30e338144bea1a9bce7edb8c91993991741cfb3a704-->
renovate-bot added the dependenciesrenovate labels 2025-11-10 17:10:34 -05:00
renovate-bot added 1 commit 2025-11-10 17:10:36 -05:00
🔧 Renovate: add renovate.json
Push Runner / Release Action (pull_request) Has been cancelled
Details
Push Runner / Test Action (pull_request) Has been cancelled
Details
2e82c092d6
Trez.One force-pushed renovate/configure from 2e82c092d6 to 20a8ee2ec5 2025-11-10 17:14:25 -05:00 Compare
Trez.One added 1 commit 2025-11-10 17:15:40 -05:00
Enabling npm Renovate manager. 95a6c27c54
Trez.One merged commit c8c8fa210a into main 2025-11-10 17:23:45 -05:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
dependencies
docker-compose
manual
renovate
No Label dependencies renovate
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
gitea-sonarqube-bot renovate-bot root Trez.One
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Trez/actions-ansi-to-html#1
Delete Branch "renovate/configure"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?