Skip to content

chore: Configure Renovate #17

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 17, 2025
Merged

chore: Configure Renovate #17

merged 1 commit into from
Feb 17, 2025

Conversation

pactflow-renovate-bot[bot]
Copy link
Contributor

@pactflow-renovate-bot pactflow-renovate-bot bot commented Feb 11, 2025

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

  • docker-compose.yml (docker-compose)
  • .github/workflows/build.yml (github-actions)
  • .github/workflows/trigger_partner_docs_update.yml (github-actions)
  • 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.
  • Apply crowd-sourced package replacement rules.
  • Apply crowd-sourced workarounds for known problems with packages.
  • Pin Docker digests.
  • Pin github-action digests.
  • Enable Renovate configuration migration PRs when needed.
  • Pin dependency versions for development dependencies.

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to .github/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 6 Pull Requests:

chore(deps): pin dependencies
  • Schedule: ["at any time"]
  • Branch name: gh-renovate/pin-dependencies
  • Merge into: master
  • Pin @pact-foundation/pact to 12.1.0
  • Pin absolute-version to 1.0.2
  • Upgrade actions/checkout to 11bd71901bbe5b1630ceea73d27597364c9af683
  • Upgrade actions/setup-node to 1a4442cacd436585916779262731d5b162bc6ec7
  • Pin eslint to 8.51.0
  • Pin jest to 29.7.0
  • Upgrade pactfoundation/pact-broker to sha256:5261a9ee7176d76d77d19d3781be67827b231bed353c2cc2aacafb5eb5a6ee70
  • Upgrade postgres to sha256:6e3358e46e34dae6c184f48fd06fe1b3dbf958ad5b83480031907e52b9ec2a7d
chore(deps): update actions/setup-node action to v4
  • Schedule: ["at any time"]
  • Branch name: gh-renovate/actions-setup-node-4.x
  • Merge into: master
  • Upgrade actions/setup-node to 1d0ff469b7ec7b3cb9d8673fde0c81c44821de2a
chore(deps): update dependency @pact-foundation/pact to v14
  • Schedule: ["at any time"]
  • Branch name: gh-renovate/pact-foundation-pact-14.x
  • Merge into: master
  • Upgrade @pact-foundation/pact to ^14.0.0
chore(deps): update dependency absolute-version to v2
  • Schedule: ["at any time"]
  • Branch name: gh-renovate/absolute-version-2.x
  • Merge into: master
  • Upgrade absolute-version to ^2.0.0
chore(deps): update dependency eslint to v9
  • Schedule: ["at any time"]
  • Branch name: gh-renovate/major-eslint-monorepo
  • Merge into: master
  • Upgrade eslint to ^9.0.0
chore(deps): lock file maintenance
  • Schedule: ["before 4am on monday"]
  • Branch name: gh-renovate/lock-file-maintenance
  • Merge into: master
  • Regenerate lock files to use latest dependency versions

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

@pactflow-renovate-bot pactflow-renovate-bot bot force-pushed the github-renovate/configure branch from 879d2ca to 48ab02b Compare February 14, 2025 01:36
@JP-Ellis JP-Ellis merged commit 207b930 into master Feb 17, 2025
4 checks passed
@JP-Ellis JP-Ellis deleted the github-renovate/configure branch February 17, 2025 20:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant