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 #201

Merged
merged 1 commit into from Jul 20, 2022
Merged

Configure Renovate #201

merged 1 commit into from Jul 20, 2022

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 20, 2022

Mend Renovate

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/continuous-integration.yml (github-actions)
  • .github/workflows/docs-build.yml (github-actions)
  • .github/workflows/release-on-milestone-closed.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.
  • Ignore node_modules, bower_components, vendor and various test/tests directories.
  • Automerge patch and minor upgrades if they pass tests.
  • If automerging, push the new commit directly to the base branch (no PR).
  • Wait for branch tests to pass or fail before creating the PR.
  • Rebase existing PRs any time the base branch has been updated.
  • Separate major versions of dependencies into individual branches/PRs.
  • Do not separate patch and minor upgrades into separate PRs for the same dependency.
  • Raise PR when vulnerability alerts are detected.
  • Evaluate schedules according to timezone UTC.
  • Append Signed-off-by: to signoff Git commits.
  • Apply label renovate to PRs.
  • Group all minor and patch updates together.
  • Default configuration for repositories in the Laminas organisation

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

chore(deps): update dependency laminas/laminas-coding-standard to ~2.3.0
chore(deps): update dependency psr/cache to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/psr-cache-3.x
  • Merge into: 3.2.x
  • Upgrade psr/cache to ^1.0 || ^3.0
chore(deps): update dependency psr/simple-cache to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/psr-simple-cache-3.x
  • Merge into: 3.2.x
  • Upgrade psr/simple-cache to ^1.0 || ^3.0
chore(deps): lock file maintenance
  • Schedule: ["before 2am"]
  • Branch name: renovate/lock-file-maintenance
  • Merge into: 3.2.x
  • Regenerate lock files to use latest dependency versions

⚠ Dependency Lookup Warnings ⚠

Please correct - or verify that you can safely ignore - these lookup failures before you merge this PR.

  • Failed to look up dependency laminas/laminas-cache-storage-implementation

Files affected: composer.json


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


Read more information about the use of Renovate Bot within Laminas.

@renovate renovate bot added the renovate label Jul 20, 2022
@Ocramius Ocramius added this to the 3.2.0 milestone Jul 20, 2022
@Ocramius Ocramius self-assigned this Jul 20, 2022
@Ocramius Ocramius merged commit 591cea7 into 3.2.x Jul 20, 2022
@Ocramius Ocramius deleted the renovate/configure branch July 20, 2022 18:32
@Ocramius
Copy link
Member

We may want to drop dependabot here, perhaps 🤔

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.

None yet

1 participant