UNCLASSIFIED - NO CUI

Skip to content

Configure Renovate

renovate requested to merge renovate/configure into development

Welcome to Renovate! This is an onboarding MR to help you understand and configure settings before regular Merge Requests begin.

🚦 To activate Renovate, merge this Merge Request. To disable Renovate, simply close this Merge Request unmerged.


Detected Package Files

  • Dockerfile (dockerfile)
  • helm/values.yaml (helm-values)
  • files/requirements.txt (pip_requirements)
  • hardening_manifest.yaml (ironbank)

What to Expect

With your current configuration, Renovate will create 5 Merge Requests:

Update dependency coverage to v6.4.1
  • Schedule: ["at any time"]
  • Branch name: renovate/coverage-6.x
  • Merge into: development
  • Upgrade coverage to ==6.4.1
Update dependency werkzeug to v2.1.2
  • Schedule: ["at any time"]
  • Branch name: renovate/werkzeug-2.x
  • Merge into: development
  • Upgrade werkzeug to ==2.1.2
Update dependency jsonschema to v4.6.0
  • Schedule: ["at any time"]
  • Branch name: renovate/jsonschema-4.x
  • Merge into: development
  • Upgrade jsonschema to ==4.6.0
Update dependency jinja2 to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/jinja2-3.x
  • Merge into: development
  • Upgrade jinja2 to ==3.1.2
Update helm values docker.io/datawire/aes to v2
  • Schedule: ["at any time"]
  • Branch name: renovate/docker.io-datawire-aes-2.x
  • Merge into: development
  • Upgrade docker.io/datawire/aes to 2.2.2

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 MR has been generated by Renovate Bot.

Merge request reports