feibisi/Studio
1
0
Fork 0
Code Issues Pull requests 1 Projects Releases Packages Wiki Activity Actions 8

chore: Configure Renovate #1

Open
feibisi wants to merge 1 commit from renovate/configure into main
pull from: renovate/configure
merge into: feibisi:main
Conversation 0 Commits 1 Files changed 1 +9
feibisi commented 2026-02-19 07:55: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/gitleaks.yml (github-actions)
  • .forgejo/workflows/trivy.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

With your current configuration, Renovate will create 1 Pull Request:

chore(deps): update https://code.forgejo.org/actions/checkout action to v6

❓ 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/gitleaks.yml` (github-actions) * `.forgejo/workflows/trivy.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 With your current configuration, Renovate will create 1 Pull Request: <details> <summary>chore(deps): update https://code.forgejo.org/actions/checkout action to v6</summary> - Schedule: ["at any time"] - Branch name: `renovate/https-code.forgejo.org-actions-checkout-6.x` - Merge into: `main` - Upgrade [https://code.forgejo.org/actions/checkout](https://code.forgejo.org/actions/checkout) to `v6` </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:a242e8d222b766007de284fdab796f531cfc6fce399c202b8621d0b0d29adae9-->
feibisi added 1 commit 2026-02-19 07:55:42 +08:00
Add renovate.json
Some checks failed
gitleaks 密钥泄露扫描 / gitleaks (pull_request) Has been cancelled
Details
Trivy 依赖漏洞扫描 / trivy-scan (pull_request) Has been cancelled
Details
5f8339f5e0
renovate-bot force-pushed renovate/configure from 5f8339f5e0 to 024b9d0a2a 2026-02-19 09:19:56 +08:00 Compare
renovate-bot force-pushed renovate/configure from 024b9d0a2a to a2284c1709 2026-02-19 09:22:04 +08:00 Compare
renovate-bot force-pushed renovate/configure from a2284c1709 to e1ea41cfd6 2026-02-19 09:23:42 +08:00 Compare
renovate-bot force-pushed renovate/configure from e1ea41cfd6 to 26c197e444 2026-02-19 14:00:22 +08:00 Compare
renovate-bot force-pushed renovate/configure from 26c197e444 to f192042e0c 2026-02-19 20:00:24 +08:00 Compare
renovate-bot force-pushed renovate/configure from f192042e0c to 14bf28bb82 2026-02-20 02:00:26 +08:00 Compare
renovate-bot force-pushed renovate/configure from 14bf28bb82 to 2688e04afc 2026-02-20 08:00:26 +08:00 Compare
renovate-bot force-pushed renovate/configure from 2688e04afc to 47d3fcf2ea 2026-02-20 14:00:22 +08:00 Compare
renovate-bot force-pushed renovate/configure from 47d3fcf2ea to 1d35f36491 2026-02-20 20:00:22 +08:00 Compare
renovate-bot force-pushed renovate/configure from 1d35f36491 to 10966c5c8f 2026-02-21 02:00:25 +08:00 Compare
renovate-bot force-pushed renovate/configure from 10966c5c8f to bd510e1bf6 2026-02-21 08:00:33 +08:00 Compare
renovate-bot force-pushed renovate/configure from bd510e1bf6 to 30942c25cb 2026-02-21 14:00:26 +08:00 Compare
renovate-bot force-pushed renovate/configure from 30942c25cb to 41dcae63e6 2026-02-21 20:00:33 +08:00 Compare
Some checks are pending
gitleaks 密钥泄露扫描 / gitleaks (pull_request) Waiting to run
Details
Trivy 依赖漏洞扫描 / trivy-scan (pull_request) Waiting to run
Details
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
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
size/S

   
stale

长期无活动

No labels
size/S
stale
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: feibisi/Studio#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?