Skip to content
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

Configure Renovate #3

Merged
merged 2 commits into from
Dec 8, 2023
Merged

Configure Renovate #3

merged 2 commits into from
Dec 8, 2023

Conversation

descope[bot]
Copy link
Contributor

@descope descope bot commented Jun 29, 2023

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

  • composer.json (composer)
  • .github/workflows/main.yml (github-actions)
  • .github/workflows/staged.yml (github-actions)

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 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.
  • Preserve (but continue to upgrade) any existing SemVer ranges.
  • Do not separate patch and minor upgrades into separate PRs for the same dependency.
  • Rebase existing PRs any time the base branch has been updated.
  • Apply crowd-sourced workarounds for known problems with packages.
  • Group known monorepo packages together.
  • Use curated list of recommended non-monorepo package groupings.

🔡 Would you like to change the way Renovate is upgrading your dependencies? Simply edit the renovate.json in this branch with your custom config and the list of Pull Requests in the "What to Expect" section below will be updated the next time Renovate runs.


What to Expect

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

Update actions/checkout action to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-checkout-4.x
  • Merge into: main
  • Upgrade actions/checkout to v4
Update dependency phpunit/phpunit to v10
  • Schedule: ["at any time"]
  • Branch name: renovate/phpunit-phpunit-10.x
  • Merge into: main
  • Upgrade phpunit/phpunit to ^10.0
Update dependency web-token/jwt-framework to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/major-jwt-framework-packages
  • Merge into: main
  • Upgrade web-token/jwt-framework to 3.2.8
Update tibdex/github-app-token action to v2
  • Schedule: ["at any time"]
  • Branch name: renovate/tibdex-github-app-token-2.x
  • Merge into: main
  • Upgrade tibdex/github-app-token to v2

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


@descope descope bot added the renovate label Jun 29, 2023
@descope descope bot force-pushed the renovate/configure branch 2 times, most recently from 873468d to e81d1de Compare June 29, 2023 18:10
@descope descope bot force-pushed the renovate/configure branch from e81d1de to 57913b0 Compare June 29, 2023 22:13
@omercnet omercnet merged commit 652ed12 into main Dec 8, 2023
1 check passed
@omercnet omercnet deleted the renovate/configure branch December 8, 2023 20:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant