Configure Renovate #151

Open
teckids_renovate_bot wants to merge 1 commit from renovate/configure into master

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

  • Dockerfile (dockerfile)
  • .forgejo/workflows/build.yml (github-actions)
  • .forgejo/workflows/test.yml (github-actions)
  • .gitlab-ci.yml (gitlabci)
  • package.json (npm)

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
  • 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.

🔡 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:

Pin dependencies
  • Schedule: ["at any time"]
  • Branch name: renovate/pin-dependencies
  • Merge into: master
  • Upgrade alpine to sha256:25109184c71bdad752c8312a8623239686a9a2071e8825f20acb8f2198c3f659
  • Upgrade caddy to sha256:fce4f15aad23222c0ac78a1220adf63bae7b94355d5ea28eee53910624acedfa
  • Upgrade gcr.io/kaniko-project/executor to sha256:2562c4fe551399514277ffff7dcca9a3b1628c4ea38cb017d7286dc6ea52f4cd
  • Upgrade https://codeberg.org/umglurf/kaniko-action to main
Update dependency bulma to v1.0.4
  • Schedule: ["at any time"]
  • Branch name: renovate/bulma-1.x-lockfile
  • Merge into: master
  • Upgrade bulma to 1.0.4
Update dependency @​fortawesome/fontawesome-free to v6.7.2
Update dependency @​fortawesome/fontawesome-free to v7
Lock file maintenance
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/lock-file-maintenance
  • Merge into: master
  • Regenerate lock files to use latest dependency versions

🚸 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 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 * `Dockerfile` (dockerfile) * `.forgejo/workflows/build.yml` (github-actions) * `.forgejo/workflows/test.yml` (github-actions) * `.gitlab-ci.yml` (gitlabci) * `package.json` (npm) ### 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 - 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. 🔡 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>Pin dependencies</summary> - Schedule: ["at any time"] - Branch name: `renovate/pin-dependencies` - Merge into: `master` - Upgrade alpine to `sha256:25109184c71bdad752c8312a8623239686a9a2071e8825f20acb8f2198c3f659` - Upgrade caddy to `sha256:fce4f15aad23222c0ac78a1220adf63bae7b94355d5ea28eee53910624acedfa` - Upgrade gcr.io/kaniko-project/executor to `sha256:2562c4fe551399514277ffff7dcca9a3b1628c4ea38cb017d7286dc6ea52f4cd` - Upgrade https://codeberg.org/umglurf/kaniko-action to `main` </details> <details> <summary>Update dependency bulma to v1.0.4</summary> - Schedule: ["at any time"] - Branch name: `renovate/bulma-1.x-lockfile` - Merge into: `master` - Upgrade [bulma](https://github.com/jgthms/bulma) to `1.0.4` </details> <details> <summary>Update dependency @&#8203;fortawesome/fontawesome-free to v6.7.2</summary> - Schedule: ["at any time"] - Branch name: `renovate/font-awesome` - Merge into: `master` - Upgrade [@fortawesome/fontawesome-free](https://github.com/FortAwesome/Font-Awesome) to `6.7.2` </details> <details> <summary>Update dependency @&#8203;fortawesome/fontawesome-free to v7</summary> - Schedule: ["at any time"] - Branch name: `renovate/major-font-awesome` - Merge into: `master` - Upgrade [@fortawesome/fontawesome-free](https://github.com/FortAwesome/Font-Awesome) to `^7.0.0` </details> <details> <summary>Lock file maintenance</summary> - Schedule: ["* 0-3 * * 1"] - Branch name: `renovate/lock-file-maintenance` - Merge into: `master` - Regenerate lock files to use latest dependency versions </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 [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-config-hash:145620d9ba8542ad205fc7eab78397ecba8468b050fe81486c3b144632611792-->
Add renovate.json
Some checks failed
/ check (push) Failing after 1m51s
f619778eb6
Some checks failed
/ check (push) Failing after 1m51s
This pull request can be merged automatically.
This branch is out-of-date with the base branch
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

Merge

Merge the changes and update on Forgejo.
git switch master
git merge --no-ff renovate/configure
git switch renovate/configure
git rebase master
git switch master
git merge --ff-only renovate/configure
git switch renovate/configure
git rebase master
git switch master
git merge --no-ff renovate/configure
git switch master
git merge --squash renovate/configure
git switch master
git merge --ff-only renovate/configure
git switch master
git merge renovate/configure
git push origin master
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
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
teckids/teckids-website!151
No description provided.