gravityfargo/bluesky-pds-docker
1
0
Fork 1
Code Issues Pull requests Packages 1 Activity Actions

chore: Configure Renovate #6

Merged
gravityfargo merged 1 commit from renovate/configure into main 2026-05-22 22:24:31 +00:00
Conversation 0 Commits 1 Files changed 1 +6
renovate-bot commented 2026-05-22 22:18:15 +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.

📚 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

  • docker-compose.yaml (docker-compose)
  • Dockerfile (dockerfile)
  • .forgejo/workflows/build-push.yml (github-actions)
  • renovate.json (renovate-config)

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
  • Pin Docker digests.
  • Pin github-action digests.
  • Enable Renovate configuration migration PRs when needed.
  • Pin dependency versions for development dependencies.
  • Recommended configuration for abandoned packages, treating packages without a release for 1 year as abandoned, while taking into account community-sourced overrides.
  • Wait until the npm package is three days old before raising the update. This a) introduces a short delay to allow for malware researchers and scanners to (possibly) detect any malicious behaviour in packages, and b) prevents the maintainer and/or NPM from unpublishing a package you already upgraded to, breaking builds.
  • Run lock file maintenance (updates) early Monday mornings.
  • Disable Renovate Dependency Dashboard creation.
  • default base preset for Forgejo repos

What to Expect

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

chore(deps): pin dependencies
chore(deps): update actions/cache action to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-cache-5.x
  • Merge into: main
  • Upgrade actions/cache to 27d5ce7f107fe9357f9df03efb73ab90386fccae
chore(deps): update docker/build-push-action action to v7
  • Schedule: ["at any time"]
  • Branch name: renovate/docker-build-push-action-7.x
  • Merge into: main
  • Upgrade docker/build-push-action to bcafcacb16a39f128d818304e6c9c0c18556b85f
chore(deps): update docker/login-action action to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/docker-login-action-4.x
  • Merge into: main
  • Upgrade docker/login-action to 4907a6ddec9925e35a0a9e82d7399ccc52663121
chore(deps): update docker/setup-buildx-action action to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/docker-setup-buildx-action-4.x
  • Merge into: main
  • Upgrade docker/setup-buildx-action to 4d04d5d9486b7bd6fa91e7baf45bbb4f8b9deedd
chore(deps): update docker/setup-qemu-action action to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/docker-setup-qemu-action-4.x
  • Merge into: main
  • Upgrade docker/setup-qemu-action to ce360397dd3f832beb865e1373c09c0e9f86d70a
chore(deps): update node.js to v24
  • Schedule: ["at any time"]
  • Branch name: renovate/node-24.x
  • Merge into: main
  • Upgrade node to sha256:2bdb65ed1dab192432bc31c95f94155ca5ad7fc1392fb7eb7526ab682fa5bf14

🚸 PR 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 Mend Renovate.

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 * `docker-compose.yaml` (docker-compose) * `Dockerfile` (dockerfile) * `.forgejo/workflows/build-push.yml` (github-actions) * `renovate.json` (renovate-config) ### 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 - Pin Docker digests. - Pin `github-action` digests. - Enable Renovate configuration migration PRs when needed. - Pin dependency versions for development dependencies. - Recommended configuration for abandoned packages, treating packages without a release for 1 year as abandoned, while taking into account community-sourced overrides. - Wait until the npm package is three days old before raising the update. This a) introduces a short delay to allow for malware researchers and scanners to (possibly) detect any malicious behaviour in packages, and b) prevents the maintainer and/or NPM from unpublishing a package you already upgraded to, breaking builds. - Run lock file maintenance (updates) early Monday mornings. - Disable Renovate Dependency Dashboard creation. - default base preset for Forgejo repos --- ### What to Expect With your current configuration, Renovate will create 7 Pull Requests: <details> <summary>chore(deps): pin dependencies</summary> - Schedule: ["at any time"] - Branch name: `renovate/pin-dependencies` - Merge into: `main` - Upgrade [actions/cache](https://github.com/actions/cache) to `0057852bfaa89a56745cba8c7296529d2fc39830` - Upgrade [actions/checkout](https://github.com/actions/checkout) to `de0fac2e4500dabe0009e67214ff5f5447ce83dd` - Upgrade [docker/build-push-action](https://github.com/docker/build-push-action) to `10e90e3645eae34f1e60eeb005ba3a3d33f178e8` - Upgrade [docker/login-action](https://github.com/docker/login-action) to `c94ce9fb468520275223c153574b00df6fe4bcc9` - Upgrade [docker/setup-buildx-action](https://github.com/docker/setup-buildx-action) to `8d2750c68a42422c14e847fe6c8ac0403b4cbd6f` - Upgrade [docker/setup-qemu-action](https://github.com/docker/setup-qemu-action) to `c7c53464625b32c7a7e944ae62b3e17d2b600130` - Upgrade [node](https://github.com/nodejs/node) to `sha256:968df39aedcea65eeb078fb336ed7191baf48f972b4479711397108be0966920` </details> <details> <summary>chore(deps): update actions/cache action to v5</summary> - Schedule: ["at any time"] - Branch name: `renovate/actions-cache-5.x` - Merge into: `main` - Upgrade [actions/cache](https://github.com/actions/cache) to `27d5ce7f107fe9357f9df03efb73ab90386fccae` </details> <details> <summary>chore(deps): update docker/build-push-action action to v7</summary> - Schedule: ["at any time"] - Branch name: `renovate/docker-build-push-action-7.x` - Merge into: `main` - Upgrade [docker/build-push-action](https://github.com/docker/build-push-action) to `bcafcacb16a39f128d818304e6c9c0c18556b85f` </details> <details> <summary>chore(deps): update docker/login-action action to v4</summary> - Schedule: ["at any time"] - Branch name: `renovate/docker-login-action-4.x` - Merge into: `main` - Upgrade [docker/login-action](https://github.com/docker/login-action) to `4907a6ddec9925e35a0a9e82d7399ccc52663121` </details> <details> <summary>chore(deps): update docker/setup-buildx-action action to v4</summary> - Schedule: ["at any time"] - Branch name: `renovate/docker-setup-buildx-action-4.x` - Merge into: `main` - Upgrade [docker/setup-buildx-action](https://github.com/docker/setup-buildx-action) to `4d04d5d9486b7bd6fa91e7baf45bbb4f8b9deedd` </details> <details> <summary>chore(deps): update docker/setup-qemu-action action to v4</summary> - Schedule: ["at any time"] - Branch name: `renovate/docker-setup-qemu-action-4.x` - Merge into: `main` - Upgrade [docker/setup-qemu-action](https://github.com/docker/setup-qemu-action) to `ce360397dd3f832beb865e1373c09c0e9f86d70a` </details> <details> <summary>chore(deps): update node.js to v24</summary> - Schedule: ["at any time"] - Branch name: `renovate/node-24.x` - Merge into: `main` - Upgrade [node](https://github.com/nodejs/node) to `sha256:2bdb65ed1dab192432bc31c95f94155ca5ad7fc1392fb7eb7526ab682fa5bf14` </details> 🚸 PR 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`](https://docs.renovatebot.com/configuration-options/#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 [Mend Renovate](https://github.com/renovatebot/renovate). <!--renovate-config-hash:87ef954a3c283e5ea88f5d2b3074b9d332f4100e00a9a1a20db57c6a63a95ac3-->
gravityfargo referenced this pull request from a commit 2026-05-22 22:24:32 +00:00
chore: Configure Renovate (!6)
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
1 participant
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
gravityfargo/bluesky-pds-docker!6
No description provided.