gitea/blog
45
20
Fork 32
Code Issues 10 Pull Requests 1 Actions Activity

Configure Renovate #299

Merged
techknowlogick merged 1 commits from renovate/configure into main 2023-10-03 17:04:05 +00:00
Conversation 0 Commits 1 Files Changed 1 +6
renovate-bot commented 2023-10-03 17:00:40 +00:00
Member
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

  • .drone.yml (droneci)
  • .gitea/workflows/delete_preview.yml (github-actions)
  • .gitea/workflows/publish-blog.yml (github-actions)
  • .gitea/workflows/test-pr.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
  • 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 directories.
  • Group known monorepo packages together.
  • Use curated list of recommended non-monorepo package groupings.
  • Apply crowd-sourced package replacement rules.
  • Apply crowd-sourced workarounds for known problems with packages.

🔡 Would you like to change the way Renovate is upgrading your dependencies? Simply edit the renovate.json5 in this branch with your custom config and the list of Pull Requests in the "What to Expect" section below will be updated the next time Renovate runs.

What to Expect

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

fix(deps): update docusaurus monorepo to v2.4.3
chore(deps): update golang docker tag to v1.21
  • Schedule: ["at any time"]
  • Branch name: renovate/golang-1.x
  • Merge into: main
  • Upgrade golang to 1.21
fix(deps): update dependency @easyops-cn/docusaurus-search-local to ^0.36.0
chore(deps): update actions/checkout action to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-checkout-4.x
  • Merge into: main
  • Upgrade actions/checkout to v4
fix(deps): update dependency @mdx-js/react to v2
  • Schedule: ["at any time"]
  • Branch name: renovate/major-mdx-monorepo
  • Merge into: main
  • Upgrade @mdx-js/react to ^2.0.0
fix(deps): update dependency clsx to v2
  • Schedule: ["at any time"]
  • Branch name: renovate/clsx-2.x
  • Merge into: main
  • Upgrade clsx to ^2.0.0
fix(deps): update dependency prism-react-renderer to v2
  • Schedule: ["at any time"]
  • Branch name: renovate/prism-react-renderer-2.x
  • Merge into: main
  • Upgrade prism-react-renderer to ^2.0.0
fix(deps): update react monorepo to v18 (major)
  • Schedule: ["at any time"]
  • Branch name: renovate/major-react-monorepo
  • Merge into: main
  • Upgrade react to ^18.0.0
  • Upgrade react-dom to ^18.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.

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 * `.drone.yml` (droneci) * `.gitea/workflows/delete_preview.yml` (github-actions) * `.gitea/workflows/publish-blog.yml` (github-actions) * `.gitea/workflows/test-pr.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 - 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 directories. - Group known monorepo packages together. - Use curated list of recommended non-monorepo package groupings. - Apply crowd-sourced package replacement rules. - Apply crowd-sourced workarounds for known problems with packages. 🔡 Would you like to change the way Renovate is upgrading your dependencies? Simply edit the `renovate.json5` in this branch with your custom config and the list of Pull Requests in the "What to Expect" section below will be updated the next time Renovate runs. --- ### What to Expect With your current configuration, Renovate will create 8 Pull Requests: <details> <summary>fix(deps): update docusaurus monorepo to v2.4.3</summary> - Schedule: ["at any time"] - Branch name: `renovate/docusaurus-monorepo` - Merge into: `main` - Upgrade [@docusaurus/core](https://github.com/facebook/docusaurus) to `2.4.3` - Upgrade [@docusaurus/module-type-aliases](https://github.com/facebook/docusaurus) to `2.4.3` - Upgrade [@docusaurus/plugin-client-redirects](https://github.com/facebook/docusaurus) to `2.4.3` - Upgrade [@docusaurus/preset-classic](https://github.com/facebook/docusaurus) to `2.4.3` </details> <details> <summary>chore(deps): update golang docker tag to v1.21</summary> - Schedule: ["at any time"] - Branch name: `renovate/golang-1.x` - Merge into: `main` - Upgrade golang to `1.21` </details> <details> <summary>fix(deps): update dependency @easyops-cn/docusaurus-search-local to ^0.36.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/easyops-cn-docusaurus-search-local-0.x` - Merge into: `main` - Upgrade [@easyops-cn/docusaurus-search-local](https://github.com/easyops-cn/docusaurus-search-local) to `^0.36.0` </details> <details> <summary>chore(deps): update actions/checkout action to v4</summary> - Schedule: ["at any time"] - Branch name: `renovate/actions-checkout-4.x` - Merge into: `main` - Upgrade [actions/checkout](https://github.com/actions/checkout) to `v4` </details> <details> <summary>fix(deps): update dependency @mdx-js/react to v2</summary> - Schedule: ["at any time"] - Branch name: `renovate/major-mdx-monorepo` - Merge into: `main` - Upgrade [@mdx-js/react](https://github.com/mdx-js/mdx) to `^2.0.0` </details> <details> <summary>fix(deps): update dependency clsx to v2</summary> - Schedule: ["at any time"] - Branch name: `renovate/clsx-2.x` - Merge into: `main` - Upgrade [clsx](https://github.com/lukeed/clsx) to `^2.0.0` </details> <details> <summary>fix(deps): update dependency prism-react-renderer to v2</summary> - Schedule: ["at any time"] - Branch name: `renovate/prism-react-renderer-2.x` - Merge into: `main` - Upgrade [prism-react-renderer](https://github.com/FormidableLabs/prism-react-renderer) to `^2.0.0` </details> <details> <summary>fix(deps): update react monorepo to v18 (major)</summary> - Schedule: ["at any time"] - Branch name: `renovate/major-react-monorepo` - Merge into: `main` - Upgrade [react](https://github.com/facebook/react) to `^18.0.0` - Upgrade [react-dom](https://github.com/facebook/react) to `^18.0.0` </details> <br /> 🚸 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:b0e8c3aba9246cf9ec209c46e593f123f2daeea739622a97656e285413290a78-->
renovate-bot added 1 commit 2023-10-03 17:00:41 +00:00
chore(deps): add renovate.json5
All checks were successful
check-and-test / check-and-test (pull_request) Successful in 2m34s
Details
delete closed PR preview s3 / delete_preview (pull_request) Successful in 19s
Details
a5bd0a7e1d
techknowlogick merged commit b610884a72 into main 2023-10-03 17:04:05 +00:00
techknowlogick deleted branch renovate/configure 2023-10-03 17:04:06 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
in progress

   
kind/bug

   
kind/deployment

   
kind/docs

   
kind/enhancement

   
kind/feature

   
kind/lint

   
kind/proposal

   
kind/question

   
kind/security

   
kind/testing

   
kind/translation

   
kind/ui

   
lgtm/done

   
lgtm/need 1

   
lgtm/need 2

   
priority/critical

   
priority/low

   
priority/maybe

   
priority/medium

   
reviewed/duplicate

   
reviewed/invalid

   
reviewed/wontfix

   
status/blocked

   
status/needs-feedback

   
status/wip
No Label
in progress
kind/bug
kind/deployment
kind/docs
kind/enhancement
kind/feature
kind/lint
kind/proposal
kind/question
kind/security
kind/testing
kind/translation
kind/ui
lgtm/done
lgtm/need 1
lgtm/need 2
priority/critical
priority/low
priority/maybe
priority/medium
reviewed/duplicate
reviewed/invalid
reviewed/wontfix
status/blocked
status/needs-feedback
status/wip
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
1 Participants
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: gitea/blog#299
No description provided.
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?