Thilawyn/website
1
0
Fork 0
Code Issues 1 Pull Requests 4 Actions Packages Projects Releases Wiki Activity

Configure Renovate #2

Merged
Thilawyn merged 1 commits from renovate/configure into master 2025-09-18 01:49:40 +02:00
Conversation 0 Commits 1 Files Changed 1 +6
renovate-bot commented 2025-09-18 01:31:00 +02:00
Collaborator
Copy Link

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 (bun)
  • compose.yml (docker-compose)
  • Dockerfile (dockerfile)
  • .gitea/workflows/build.yaml (github-actions)
  • .gitea/workflows/lint.yaml (github-actions)
  • packages/common/package.json (npm)
  • packages/server/package.json (npm)
  • packages/webapp/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.

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

Update actions/checkout action to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-checkout-5.x
  • Merge into: master
  • Upgrade actions/checkout to v5
Update actions/setup-node action to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-setup-node-5.x
  • Merge into: master
  • Upgrade actions/setup-node to v5
Update oven-sh/setup-bun action to v2
  • Schedule: ["at any time"]
  • Branch name: renovate/oven-sh-setup-bun-2.x
  • Merge into: master
  • Upgrade oven-sh/setup-bun to v2

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

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` (bun) * `compose.yml` (docker-compose) * `Dockerfile` (dockerfile) * `.gitea/workflows/build.yaml` (github-actions) * `.gitea/workflows/lint.yaml` (github-actions) * `packages/common/package.json` (npm) * `packages/server/package.json` (npm) * `packages/webapp/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. 🔡 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 3 Pull Requests: <details> <summary>Update actions/checkout action to v5</summary> - Schedule: ["at any time"] - Branch name: `renovate/actions-checkout-5.x` - Merge into: `master` - Upgrade [actions/checkout](https://github.com/actions/checkout) to `v5` </details> <details> <summary>Update actions/setup-node action to v5</summary> - Schedule: ["at any time"] - Branch name: `renovate/actions-setup-node-5.x` - Merge into: `master` - Upgrade [actions/setup-node](https://github.com/actions/setup-node) to `v5` </details> <details> <summary>Update oven-sh/setup-bun action to v2</summary> - Schedule: ["at any time"] - Branch name: `renovate/oven-sh-setup-bun-2.x` - Merge into: `master` - Upgrade [oven-sh/setup-bun](https://github.com/oven-sh/setup-bun) to `v2` </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://github.com/renovatebot/renovate/discussions). --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-config-hash:e80b4e42a3043bc12fa0640db4bac392d2bf770acf841360d7c8ceeeac2ec1a9-->
renovate-bot added 1 commit 2025-09-18 01:31:00 +02:00
Add renovate.json
All checks were successful
Lint / lint (push) Successful in 13s
Details
Build / build (pull_request) Successful in 27s
Details
dff5ff4c1a
Thilawyn added 2 commits 2025-09-18 01:37:25 +02:00
Add renovate.json
All checks were successful
Lint / lint (push) Successful in 13s
Details
Build / build (pull_request) Successful in 27s
Details
dff5ff4c1a
Add renovate.json
All checks were successful
Lint / lint (push) Successful in 13s
Details
Build / build (pull_request) Successful in 26s
Details
5e6ee26357
Thilawyn added 2 commits 2025-09-18 01:46:50 +02:00
Add renovate.json
All checks were successful
Lint / lint (push) Successful in 13s
Details
Build / build (pull_request) Successful in 26s
Details
5e6ee26357
Add renovate.json
All checks were successful
Lint / lint (push) Successful in 13s
Details
Build / build (pull_request) Successful in 28s
Details
c2a094802c
Thilawyn merged commit 8e0dfba054 into master 2025-09-18 01:49:40 +02:00
Thilawyn deleted branch renovate/configure 2025-09-18 01:49:40 +02:00
Thilawyn referenced this issue from a commit 2025-09-18 01:49:41 +02:00
Configure Renovate (#2)
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
renovate-bot Thilawyn
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Thilawyn/website#2
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?