sam
/
awlpi
1
0
Fork 0
Code Issues Pull Requests 1 Packages Projects Releases Wiki Activity

Configure Renovate #1

Open
renovate-bot wants to merge 1 commits from renovate/configure into master
pull from: renovate/configure
merge into: sam:master
Conversation 0 Commits 1 Files Changed 1 +10
renovate-bot commented 2022-09-13 02:00:27 +00: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

  • go.mod (gomod)

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.
  • Add [skip ci] to commit message body whenever pinning.
  • Raise PR when vulnerability alerts are detected.
  • Use semantic prefixes for commit messages and PR titles.

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

fix(deps): update module github.com/go-chi/chi/v5 to v5.0.12
  • Schedule: ["at any time"]
  • Branch name: renovate/github.com-go-chi-chi-v5-5.x
  • Merge into: master
  • Upgrade github.com/go-chi/chi/v5 to v5.0.12
fix(deps): update module github.com/swaggo/http-swagger to v1.3.4
  • Schedule: ["at any time"]
  • Branch name: renovate/github.com-swaggo-http-swagger-1.x
  • Merge into: master
  • Upgrade github.com/swaggo/http-swagger to v1.3.4
fix(deps): update module git.froth.zone/sam/awl to v0.6.12
  • Schedule: ["at any time"]
  • Branch name: renovate/git.froth.zone-sam-awl-0.x
  • Merge into: master
  • Upgrade git.froth.zone/sam/awl to v0.6.12
fix(deps): update module github.com/swaggo/swag to v1.16.3
  • Schedule: ["at any time"]
  • Branch name: renovate/github.com-swaggo-swag-1.x
  • Merge into: master
  • Upgrade github.com/swaggo/swag to v1.16.3
fix(deps): update module github.com/swaggo/http-swagger to v2
  • Schedule: ["at any time"]
  • Branch name: renovate/github.com-swaggo-http-swagger-2.x
  • Merge into: master
  • Upgrade github.com/swaggo/http-swagger to v2.0.2

🚸 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 * `go.mod` (gomod) ### 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. - Add `[skip ci]` to commit message body whenever pinning. - Raise PR when vulnerability alerts are detected. - Use semantic prefixes for commit messages and PR titles. 🔡 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 5 Pull Requests: <details> <summary>fix(deps): update module github.com/go-chi/chi/v5 to v5.0.12</summary> - Schedule: ["at any time"] - Branch name: `renovate/github.com-go-chi-chi-v5-5.x` - Merge into: `master` - Upgrade [github.com/go-chi/chi/v5](https://github.com/go-chi/chi) to `v5.0.12` </details> <details> <summary>fix(deps): update module github.com/swaggo/http-swagger to v1.3.4</summary> - Schedule: ["at any time"] - Branch name: `renovate/github.com-swaggo-http-swagger-1.x` - Merge into: `master` - Upgrade [github.com/swaggo/http-swagger](https://github.com/swaggo/http-swagger) to `v1.3.4` </details> <details> <summary>fix(deps): update module git.froth.zone/sam/awl to v0.6.12</summary> - Schedule: ["at any time"] - Branch name: `renovate/git.froth.zone-sam-awl-0.x` - Merge into: `master` - Upgrade git.froth.zone/sam/awl to `v0.6.12` </details> <details> <summary>fix(deps): update module github.com/swaggo/swag to v1.16.3</summary> - Schedule: ["at any time"] - Branch name: `renovate/github.com-swaggo-swag-1.x` - Merge into: `master` - Upgrade [github.com/swaggo/swag](https://github.com/swaggo/swag) to `v1.16.3` </details> <details> <summary>fix(deps): update module github.com/swaggo/http-swagger to v2</summary> - Schedule: ["at any time"] - Branch name: `renovate/github.com-swaggo-http-swagger-2.x` - Merge into: `master` - Upgrade [github.com/swaggo/http-swagger](https://github.com/swaggo/http-swagger) to `v2.0.2` </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:db440407e4ac1edcb17cdccd348bbdb0de754b0217812eb7a76cc7351dd6c780-->
renovate-bot force-pushed renovate/configure from 9cff8e66b2 to 52acd4224f 2022-09-15 12:00:19 +00:00 Compare
renovate-bot force-pushed renovate/configure from 52acd4224f to 3823b2c2e2 2022-10-04 14:07:50 +00:00 Compare
renovate-bot force-pushed renovate/configure from 3823b2c2e2 to bc3f50961b 2024-03-16 21:34:57 +00:00 Compare
This pull request can be merged automatically.
You are not authorized to merge this pull request.
You can also view command line instructions.

Step 1:

From your project repository, check out a new branch and test the changes.
git checkout -b renovate/configure master
git pull origin renovate/configure

Step 2:

Merge the changes and update on Forgejo.
git checkout master
git merge --no-ff renovate/configure
git push origin master
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
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: sam/awlpi#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?