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.
📚 See our Reading List for relevant documentation you may be interested in reading.
🔡 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.
Detected Package Files
.gitea/workflows/ci.yaml (github-actions)
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 (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 Forgejo contains a link to the commit-to-commit diff
Ensure that every dependency pinned by digest and sourced from Gitea contains a link to the commit-to-commit diff
Ensure that every dependency pinned by digest and sourced from GitHub.com and Github enterprise contains a link to the commit-to-commit diff
Ensure that every dependency pinned by digest and sourced from GitLab.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
Enable Renovate Dependency Dashboard creation.
Use semantic prefixes for commit messages and PR titles.
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 Forgejo contains a link to the commit-to-commit diff
Ensure that every dependency pinned by digest and sourced from Gitea contains a link to the commit-to-commit diff
Ensure that every dependency pinned by digest and sourced from GitHub.com and Github enterprise contains a link to the commit-to-commit diff
Ensure that every dependency pinned by digest and sourced from GitLab.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
What to Expect
With your current configuration, Renovate will create 4 Pull Requests:
❓ 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.
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.
📚 See our [Reading List](https://docs.renovatebot.com/reading-list/) for relevant documentation you may be interested in reading.
🔡 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.
---
### Detected Package Files
* `.gitea/workflows/ci.yaml` (github-actions)
* `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 (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 Forgejo contains a link to the commit-to-commit diff
- Ensure that every dependency pinned by digest and sourced from Gitea contains a link to the commit-to-commit diff
- Ensure that every dependency pinned by digest and sourced from GitHub.com and Github enterprise contains a link to the commit-to-commit diff
- Ensure that every dependency pinned by digest and sourced from GitLab.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
- Enable Renovate Dependency Dashboard creation.
- Use semantic prefixes for commit messages and PR titles.
- 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 Forgejo contains a link to the commit-to-commit diff
- Ensure that every dependency pinned by digest and sourced from Gitea contains a link to the commit-to-commit diff
- Ensure that every dependency pinned by digest and sourced from GitHub.com and Github enterprise contains a link to the commit-to-commit diff
- Ensure that every dependency pinned by digest and sourced from GitLab.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
---
### What to Expect
With your current configuration, Renovate will create 4 Pull Requests:
<details>
<summary>chore(deps): Update dependency go to 1.26</summary>
- Schedule: ["at any time"]
- Branch name: `renovate/go-1.x`
- Merge into: `main`
- Upgrade [go](https://github.com/actions/go-versions) to `1.26`
</details>
<details>
<summary>chore(deps): Update module github.com/nats-io/nats.go to v1.52.0</summary>
- Schedule: ["at any time"]
- Branch name: `renovate/github.com-nats-io-nats.go-1.x`
- Merge into: `main`
- Upgrade [github.com/nats-io/nats.go](https://github.com/nats-io/nats.go) to `v1.52.0`
</details>
<details>
<summary>chore(deps): Update actions/checkout action to v6</summary>
- Schedule: ["at any time"]
- Branch name: `renovate/actions-checkout-6.x`
- Merge into: `main`
- Upgrade [actions/checkout](https://github.com/actions/checkout) to `v6`
</details>
<details>
<summary>chore(deps): Update actions/setup-go action to v6</summary>
- Schedule: ["at any time"]
- Branch name: `renovate/actions-setup-go-6.x`
- Merge into: `main`
- Upgrade [actions/setup-go](https://github.com/actions/setup-go) 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 [Mend Renovate](https://github.com/renovatebot/renovate).
<!--renovate-config-hash:e80b4e42a3043bc12fa0640db4bac392d2bf770acf841360d7c8ceeeac2ec1a9-->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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.
📚 See our Reading List for relevant documentation you may be interested in reading.
🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to
renovate.jsonin this branch. Renovate will update the Pull Request description the next time it runs.Detected Package Files
.gitea/workflows/ci.yaml(github-actions)go.mod(gomod)Configuration Summary
Based on the default config's presets, Renovate will:
fixfor dependencies andchorefor all others if semantic commits are in use.node_modules,bower_components,vendorand various test/tests (except for nuget) directories.fixfor dependencies andchorefor all others if semantic commits are in use.node_modules,bower_components,vendorand various test/tests (except for nuget) directories.What to Expect
With your current configuration, Renovate will create 4 Pull Requests:
chore(deps): Update dependency go to 1.26
renovate/go-1.xmain1.26chore(deps): Update module github.com/nats-io/nats.go to v1.52.0
renovate/github.com-nats-io-nats.go-1.xmainv1.52.0chore(deps): Update actions/checkout action to v6
renovate/actions-checkout-6.xmainv6chore(deps): Update actions/setup-go action to v6
renovate/actions-setup-go-6.xmainv6❓ 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 Mend Renovate.