oap/pepela
Watch
1
0
Fork
You've already forked pepela
 0
Code Issues Pull requests 1 Projects Releases Packages Wiki Activity Actions

Configure Renovate #1

Open
renovate wants to merge 2 commits from renovate/configure into main
pull from: renovate/configure
merge into: oap:main
Conversation 1 Commits 2 Files changed 1 +4
renovate commented 2026-09-28 22:47:16 -07: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.

📚 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

  • 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
  • Provide a link to octochangelog's improved breakdown for Renovate's changelogs

What to Expect

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

Update module github.com/alexedwards/scs/v2 to v2.9.0
  • Schedule: ["at any time"]
  • Branch name: renovate/github.com-alexedwards-scs-v2-2.x
  • Merge into: main
  • Upgrade github.com/alexedwards/scs/v2 to v2.9.0
Update module github.com/coreos/go-oidc/v3 to v3.21.0
  • Schedule: ["at any time"]
  • Branch name: renovate/github.com-coreos-go-oidc-v3-3.x
  • Merge into: main
  • Upgrade github.com/coreos/go-oidc/v3 to v3.21.0
Update module golang.org/x/oauth2 to v0.37.0
  • Schedule: ["at any time"]
  • Branch name: renovate/golang.org-x-oauth2-0.x
  • Merge into: main
  • Upgrade golang.org/x/oauth2 to v0.37.0

❓ 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 CLI.

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 * `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 - Provide a link to octochangelog's improved breakdown for Renovate's changelogs --- ### What to Expect With your current configuration, Renovate will create 3 Pull Requests: <details> <summary>Update module github.com/alexedwards/scs/v2 to v2.9.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/github.com-alexedwards-scs-v2-2.x` - Merge into: `main` - Upgrade [github.com/alexedwards/scs/v2](https://github.com/alexedwards/scs) to `v2.9.0` </details> <details> <summary>Update module github.com/coreos/go-oidc/v3 to v3.21.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/github.com-coreos-go-oidc-v3-3.x` - Merge into: `main` - Upgrade [github.com/coreos/go-oidc/v3](https://github.com/coreos/go-oidc) to `v3.21.0` </details> <details> <summary>Update module golang.org/x/oauth2 to v0.37.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/golang.org-x-oauth2-0.x` - Merge into: `main` - Upgrade [golang.org/x/oauth2](https://go.googlesource.com/oauth2) to `v0.37.0` </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 CLI](https://github.com/renovatebot/renovate). <!--renovate-config-hash:7748ea026d07812cba2cb72643e0f135ccbe933bb95169741a551e58b5dfc5cb--> 
The onboarding config had only $schema, so monorepo grouping, the
dependency dashboard and :ignoreModulesAndTests were off.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
oap commented 2026-10-06 00:17:31 -07:00
Owner
Copy link

I pushed e2c173b to this branch. It adds "extends": ["config:recommended"].

The onboarding renovate.json had only $schema. That turned off config:recommended, so monorepo grouping, the dependency dashboard and :ignoreModulesAndTests were off. renovate-config-validator --strict accepts the new file. Renovate updates the PR description on its next run (Monday 05:00).

Review: do not merge yet. This config change does not fix the problem below.

nix/package.nix has a fixed vendorHash. Renovate cannot update that hash, so each gomod PR (scs, go-oidc, oauth2) gives a hash mismatch. pepela is a flake input of nix-config (flake.nix), and nix-config's weekly lockFileMaintenance pulls pepela main. Thus one merged bump breaks nix-config check and the nas deploy.

Before you merge, do one of these:

  1. Add a CI job here that runs nix build. Then fix vendorHash by hand in each Renovate PR.
  2. Add a postUpgradeTasks step that updates the hash. This also needs allowedPostUpgradeCommands in the nas global config (hosts/nas/renovate.nix).

Also, the build uses Go 1.25 with GOEXPERIMENT=jsonv2. Do not merge a bump of the go directive without a build.

There are no workflows here, so a renovate/* push or a bot PR runs no job and gets no secrets.

🤖 Generated with Claude Code

I pushed e2c173b to this branch. It adds `"extends": ["config:recommended"]`. The onboarding `renovate.json` had only `$schema`. That turned off `config:recommended`, so monorepo grouping, the dependency dashboard and `:ignoreModulesAndTests` were off. `renovate-config-validator --strict` accepts the new file. Renovate updates the PR description on its next run (Monday 05:00). **Review: do not merge yet.** This config change does not fix the problem below. `nix/package.nix` has a fixed `vendorHash`. Renovate cannot update that hash, so each gomod PR (scs, go-oidc, oauth2) gives a hash mismatch. pepela is a flake input of nix-config (`flake.nix`), and nix-config's weekly `lockFileMaintenance` pulls pepela `main`. Thus one merged bump breaks nix-config `check` and the nas deploy. Before you merge, do one of these: 1. Add a CI job here that runs `nix build`. Then fix `vendorHash` by hand in each Renovate PR. 2. Add a `postUpgradeTasks` step that updates the hash. This also needs `allowedPostUpgradeCommands` in the nas global config (`hosts/nas/renovate.nix`). Also, the build uses Go 1.25 with `GOEXPERIMENT=jsonv2`. Do not merge a bump of the `go` directive without a build. There are no workflows here, so a `renovate/*` push or a bot PR runs no job and gets no secrets. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
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 switch renovate/configure
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
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
oap/pepela!1
No description provided.