Skip to content

Configure Renovate#1

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/configure
Open

Configure Renovate#1
renovate[bot] wants to merge 1 commit intomainfrom
renovate/configure

Conversation

@renovate
Copy link
Copy Markdown

@renovate renovate bot commented Mar 17, 2026

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

  • .github/workflows/dry-run.yaml (github-actions)
  • .github/workflows/release.yaml (github-actions)
  • modules/argus_ai/functions/argus_ai_log_analyzer/requirements-dev.txt (pip_requirements)
  • modules/argus_ai/functions/argus_ai_log_analyzer/requirements.txt (pip_requirements)
  • modules/argus_ai/functions/argus_ai_log_chopper/requirements.txt (pip_requirements)

Configuration Summary

Based on the default config's presets, Renovate will:

  • Start dependency updates only once this onboarding PR is merged
  • Hopefully safe environment variables to allow users to configure.
  • Show all Merge Confidence badges for pull requests.
  • 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

🔡 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 4 Pull Requests:

chore(deps): update cognite/toolkit docker tag to v0.7.219
  • Schedule: ["at any time"]
  • Branch name: renovate/cognite-toolkit-0.x
  • Merge into: main
  • Upgrade cognite/toolkit to 0.7.219
chore(deps): update actions/checkout action to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-checkout-6.x
  • Merge into: main
  • Upgrade actions/checkout to v6
chore(deps): update actions/github-script action to v8
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-github-script-8.x
  • Merge into: main
  • Upgrade actions/github-script to v8
chore(deps): update dependency cognite-sdk to v8
  • Schedule: ["at any time"]
  • Branch name: renovate/cognite-sdk-8.x
  • Merge into: main
  • Upgrade cognite-sdk to >=8,<8.1

🚸 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 was generated by Mend Renovate. View the repository job log.

@github-actions
Copy link
Copy Markdown

github-actions bot commented Mar 17, 2026

Dry-run has finished!
Please review before merging

Build output:
  WARNING: Overriding environment variables with values from .env file...
╭───────────────────────────────────────────────────────╮
│ Building project '/__w/argus-ai/argus-ai':            
│   - Toolkit Version '0.7.84'                          │
│   - Environment name 'dev', validation-type 'dev'.    │
│   - Config '/__w/argus-ai/argus-ai/config.dev.yaml'   │
│   - Module directory '/__w/argus-ai/argus-ai/modules' │
╰───────────────────────────────────────────────────────╯
WARNING [MEDIUM]: No 'CDF_PROJECT' environment variable set. This is expected to
match the project set in environment section of 'config.dev.yaml'.
         This is required for building configurations for staging and prod 
environments to ensure that you do not accidentally deploy to the wrong project.
INFO: Build complete. Files are located in build/
Dry-run output:
  WARNING: Overriding environment variables with values from .env file...
  ERROR (ToolkitMissingValueError): Missing environment variables: CDF_CLUSTER 
and CDF_PROJECT

@renovate renovate bot force-pushed the renovate/configure branch from 54f4cbc to e209d98 Compare March 26, 2026 16:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants