WenPai-org/wpmind
WenPai-org/wpmind
7
0
Fork 0
Code Pull requests 1 Projects Releases 1 Packages Activity Actions

chore: Configure Renovate #1

Open
feibisi wants to merge 1 commit from renovate/configure into main
pull from: renovate/configure
merge into: WenPai-org:main
Conversation 0 Commits 1 Files changed 1 +9
feibisi commented 2026-02-19 08:15:41 +08:00
Owner
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

  • .forgejo/workflows/release.yml (github-actions)
  • .forgejo/workflows/wp-release.yml (github-actions)
  • renovate.json (renovate-config-presets)

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

🔡 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

It looks like your repository dependencies are already up-to-date and no Pull Requests will be necessary right away.

❓ 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 * `.forgejo/workflows/release.yml` (github-actions) * `.forgejo/workflows/wp-release.yml` (github-actions) * `renovate.json` (renovate-config-presets) ### 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 🔡 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 It looks like your repository dependencies are already up-to-date and no Pull Requests will be necessary right away. --- ❓ 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:a242e8d222b766007de284fdab796f531cfc6fce399c202b8621d0b0d29adae9-->
feibisi added 1 commit 2026-02-19 08:15:42 +08:00
feibisi added the
size/S
 label 2026-02-19 09:17:39 +08:00
renovate-bot force-pushed renovate/configure from 96e13f0961 to b834036cd2 2026-02-19 14:18:20 +08:00 Compare
renovate-bot force-pushed renovate/configure from b834036cd2 to d1aa6825c5 2026-02-19 20:16:44 +08:00 Compare
renovate-bot force-pushed renovate/configure from d1aa6825c5 to 308dd0ca88 2026-02-20 02:16:51 +08:00 Compare
renovate-bot force-pushed renovate/configure from 308dd0ca88 to 26db8c41a4 2026-02-20 08:17:29 +08:00 Compare
renovate-bot force-pushed renovate/configure from 26db8c41a4 to a165fa700c 2026-02-20 14:16:16 +08:00 Compare
renovate-bot force-pushed renovate/configure from a165fa700c to 671f4ce16a 2026-02-20 20:16:40 +08:00 Compare
renovate-bot force-pushed renovate/configure from 671f4ce16a to f21f4b405a 2026-02-21 02:15:49 +08:00 Compare
renovate-bot force-pushed renovate/configure from f21f4b405a to 96f0e345c4 2026-02-21 08:15:53 +08:00 Compare
renovate-bot force-pushed renovate/configure from 96f0e345c4 to 25c7350e11 2026-02-21 14:17:04 +08:00 Compare
renovate-bot force-pushed renovate/configure from 25c7350e11 to 5cd60770a8 2026-02-21 20:17:41 +08:00 Compare
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 checkout 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 checkout main
git merge --no-ff renovate/configure
git checkout renovate/configure
git rebase main
git checkout main
git merge --ff-only renovate/configure
git checkout renovate/configure
git rebase main
git checkout main
git merge --no-ff renovate/configure
git checkout main
git merge --squash renovate/configure
git checkout main
git merge --ff-only renovate/configure
git checkout main
git merge renovate/configure
git push origin main
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
size/S

   
stale

长期无活动

  
wordpress-plugins
No labels
size/S
stale
wordpress-plugins
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 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: WenPai-org/wpmind#1
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?