Skip to content

Configure Renovate#4

Closed
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/configure
Closed

Configure Renovate#4
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/configure

Conversation

@renovate

@renovate renovate Bot commented Mar 27, 2025

Copy link
Copy Markdown

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

  • Dockerfile-api (dockerfile)
  • Dockerfile-worker (dockerfile)
  • .github/workflows/ci.yaml (github-actions)
  • kustomize/overlays/biosim-gke/kustomization.yaml (kustomize)
  • kustomize/overlays/biosim-local/kustomization.yaml (kustomize)
  • kustomize/overlays/biosim-rke/kustomization.yaml (kustomize)
  • pyproject.toml (poetry)

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 28 Pull Requests:

Update dependency motor to v3.7.1
  • Schedule: ["at any time"]
  • Branch name: renovate/motor-3.x-lockfile
  • Merge into: main
  • Upgrade motor to 3.7.1
Update dependency pyyaml to v6.0.3
  • Schedule: ["at any time"]
  • Branch name: renovate/pyyaml-6.x-lockfile
  • Merge into: main
  • Upgrade pyyaml to 6.0.3
Update dependency ruff to v0.15.8
  • Schedule: ["at any time"]
  • Branch name: renovate/ruff-0.x-lockfile
  • Merge into: main
  • Upgrade ruff to 0.15.8
Update dependency asyncssh to v2.22.0
  • Schedule: ["at any time"]
  • Branch name: renovate/asyncssh-2.x-lockfile
  • Merge into: main
  • Upgrade asyncssh to 2.22.0
Update dependency fastapi to ^0.135.0
  • Schedule: ["at any time"]
  • Branch name: renovate/fastapi-0.x
  • Merge into: main
  • Upgrade fastapi to ^0.135.0
Update dependency gcloud-aio-storage to v9.6.4
  • Schedule: ["at any time"]
  • Branch name: renovate/gcloud-aio-storage-9.x-lockfile
  • Merge into: main
  • Upgrade gcloud-aio-storage to 9.6.4
Update dependency h5py to v3.16.0
  • Schedule: ["at any time"]
  • Branch name: renovate/h5py-3.x-lockfile
  • Merge into: main
  • Upgrade h5py to 3.16.0
Update dependency mypy to v1.19.1
  • Schedule: ["at any time"]
  • Branch name: renovate/mypy-1.x-lockfile
  • Merge into: main
  • Upgrade mypy to 1.19.1
Update dependency numpy to v2.4.3
  • Schedule: ["at any time"]
  • Branch name: renovate/numpy-2.x-lockfile
  • Merge into: main
  • Upgrade numpy to 2.4.3
Update dependency pandas to v2.3.3
  • Schedule: ["at any time"]
  • Branch name: renovate/pandas-2.x-lockfile
  • Merge into: main
  • Upgrade pandas to 2.3.3
Update dependency pydantic to v2.12.5
  • Schedule: ["at any time"]
  • Branch name: renovate/pydantic-2.x-lockfile
  • Merge into: main
  • Upgrade pydantic to 2.12.5
Update dependency pydantic-settings to v2.13.1
  • Schedule: ["at any time"]
  • Branch name: renovate/pydantic-settings-2.x-lockfile
  • Merge into: main
  • Upgrade pydantic-settings to 2.13.1
Update dependency pytest to v8.4.2
  • Schedule: ["at any time"]
  • Branch name: renovate/pytest-8.x-lockfile
  • Merge into: main
  • Upgrade pytest to 8.4.2
Update dependency python to v3.14.3
  • Schedule: ["at any time"]
  • Branch name: renovate/python-3.x
  • Merge into: main
  • Upgrade python to 3.14
  • Upgrade python to 3.14.3-slim-bookworm
Update dependency python-dotenv to v1.2.2
  • Schedule: ["at any time"]
  • Branch name: renovate/python-dotenv-1.x-lockfile
  • Merge into: main
  • Upgrade python-dotenv to 1.2.2
Update dependency python-libsbml to v5.21.1
  • Schedule: ["at any time"]
  • Branch name: renovate/python-libsbml-5.x-lockfile
  • Merge into: main
  • Upgrade python-libsbml to 5.21.1
Update dependency temporalio to v1.24.0
  • Schedule: ["at any time"]
  • Branch name: renovate/temporalio-1.x-lockfile
  • Merge into: main
  • Upgrade temporalio to 1.24.0
Update dependency testcontainers to v4.14.2
  • Schedule: ["at any time"]
  • Branch name: renovate/testcontainers-4.x-lockfile
  • Merge into: main
  • Upgrade testcontainers to 4.14.2
Update dependency types-aiobotocore to v2.26.0
  • Schedule: ["at any time"]
  • Branch name: renovate/types-aiobotocore-2.x-lockfile
  • Merge into: main
  • Upgrade types-aiobotocore to 2.26.0
Update dependency uvicorn to ^0.42.0
  • Schedule: ["at any time"]
  • Branch name: renovate/uvicorn-0.x
  • Merge into: main
  • Upgrade uvicorn to ^0.42.0
Update docker.io/library/mongo Docker tag to v8.2.6
  • Schedule: ["at any time"]
  • Branch name: renovate/docker.io-library-mongo-8.x
  • Merge into: main
  • Upgrade docker.io/library/mongo to 8.2.6
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
Update actions/setup-python action to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-setup-python-6.x
  • Merge into: main
  • Upgrade actions/setup-python to v6
Update dependency chardet to v7
  • Schedule: ["at any time"]
  • Branch name: renovate/chardet-7.x
  • Merge into: main
  • Upgrade chardet to ^7.0.0
Update dependency pandas to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/pandas-3.x
  • Merge into: main
  • Upgrade pandas to ^3.0.0
Update dependency pytest to v9
  • Schedule: ["at any time"]
  • Branch name: renovate/pytest-9.x
  • Merge into: main
  • Upgrade pytest to ^9.0.0
Update dependency pytest-asyncio to v1
  • Schedule: ["at any time"]
  • Branch name: renovate/pytest-asyncio-1.x
  • Merge into: main
  • Upgrade pytest-asyncio to ^1.0.0
Update dependency types-aiobotocore to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/types-aiobotocore-3.x
  • Merge into: main
  • Upgrade types-aiobotocore to ^3.0.0

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

@renovate renovate Bot closed this Mar 31, 2026
@renovate

renovate Bot commented Mar 31, 2026

Copy link
Copy Markdown
Author

Renovate is disabled

Renovate is disabled because the onboarding PR has been unmerged for more than 366 days. To enable Renovate, you can either (a) change this PR's title to get a new onboarding PR, and merge the new onboarding PR, or (b) create a Renovate config file, and commit that file to your base branch.

jcschaff added a commit that referenced this pull request Jun 4, 2026
#4 (in-flight SimulationRunWorkflow loses biosim_run_id on replay):
SimulationRunWorkflow now falls back to the nested
output.biosimulator_workflow_run.biosim_run.id when the new
output.biosimulations_run_id field is None. Child OmexSimWorkflowOutput
payloads recorded under pre-PR2.5 code lack the new top-level field;
pydantic defaults it to None on replay. The fallback uses the canonical
id from the historical BiosimulatorWorkflowRun so the parent still
records the external run id even mid-deploy.

#3 (Temporal NonDeterministicWorkflowError for in-flight OmexSimWorkflow):
The activity-sequence change inside OmexSimWorkflow (1 monolithic ->
2 split + optional 1 early-write) is structurally incompatible with
histories recorded by the old code. An @activity.defn(name=...) alias
can't fix it -- the *number* of scheduled activities also differs. The
Temporal-correct workflow.patched() pattern is deferred (substantial
churn for a one-time transition); the pragmatic mitigation is a worker
drain before rollout.

Docs:
- docs/workflows-architecture.md gains a "Deploy considerations"
  section explaining the NDE risk, the drain procedure, the deferred
  workflow.patched alternative, and what replay-safety nets the
  PR2.5 code itself provides.
- backend/CLAUDE.md's Deploy section gets a callout pointing to it.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.

0 participants