Skip to content

chore: Configure Renovate#248

Merged
fergusfinn merged 1 commit into
mainfrom
renovate/configure
Nov 27, 2025
Merged

chore: Configure Renovate#248
fergusfinn merged 1 commit into
mainfrom
renovate/configure

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Nov 27, 2025

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

  • dwctl/Cargo.toml (cargo)
  • docker-compose.override.yml (docker-compose)
  • docker-compose.yml (docker-compose)
  • Dockerfile (dockerfile)
  • dashboard/Dockerfile (dockerfile)
  • .github/workflows/autolabel.yaml (github-actions)
  • .github/workflows/ci.yaml (github-actions)
  • .github/workflows/release-please.yaml (github-actions)
  • dashboard/package.json (npm)

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.

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

chore(deps): update dependency @​types/node to v24.10.1
  • Schedule: ["at any time"]
  • Branch name: renovate/node-24.x-lockfile
  • Merge into: main
  • Upgrade @types/node to 24.10.1
chore(deps): update dependency @​vitejs/plugin-react to v5.1.1
  • Schedule: ["at any time"]
  • Branch name: renovate/vitejs-plugin-react-5.x-lockfile
  • Merge into: main
  • Upgrade @vitejs/plugin-react to 5.1.1
chore(deps): update dependency msw to v2.12.3
  • Schedule: ["at any time"]
  • Branch name: renovate/msw-2.x-lockfile
  • Merge into: main
  • Upgrade msw to 2.12.3
chore(deps): update dependency react-day-picker to v9.11.2
  • Schedule: ["at any time"]
  • Branch name: renovate/react-day-picker-9.x-lockfile
  • Merge into: main
  • Upgrade react-day-picker to 9.11.2
chore(deps): update dependency react-hook-form to v7.66.1
  • Schedule: ["at any time"]
  • Branch name: renovate/react-hook-form-7.x-lockfile
  • Merge into: main
  • Upgrade react-hook-form to 7.66.1
chore(deps): update dependency react-router-dom to v7.9.6
  • Schedule: ["at any time"]
  • Branch name: renovate/react-router-monorepo
  • Merge into: main
  • Upgrade react-router-dom to 7.9.6
chore(deps): update dependency vite to v7.2.4
  • Schedule: ["at any time"]
  • Branch name: renovate/vite-7.x-lockfile
  • Merge into: main
  • Upgrade vite to 7.2.4
chore(deps): update react monorepo
  • Schedule: ["at any time"]
  • Branch name: renovate/react-monorepo
  • Merge into: main
  • Upgrade @types/react to 19.2.7
  • Upgrade @types/react-dom to 19.2.3
chore(deps): update rust crate axum to v0.8.7
  • Schedule: ["at any time"]
  • Branch name: renovate/axum-monorepo
  • Merge into: main
  • Upgrade axum to 0.8.7
chore(deps): update rust crate chrono to v0.4.42
  • Schedule: ["at any time"]
  • Branch name: renovate/chrono-0.x-lockfile
  • Merge into: main
  • Upgrade chrono to 0.4.42
chore(deps): update rust crate clap to v4.5.53
  • Schedule: ["at any time"]
  • Branch name: renovate/clap-4.x-lockfile
  • Merge into: main
  • Upgrade clap to 4.5.53
chore(deps): update rust crate lettre to v0.11.19
  • Schedule: ["at any time"]
  • Branch name: renovate/lettre-0.x-lockfile
  • Merge into: main
  • Upgrade lettre to 0.11.19
chore(deps): update rust crate tokio-util to v0.7.17
  • Schedule: ["at any time"]
  • Branch name: renovate/tokio-util-0.x-lockfile
  • Merge into: main
  • Upgrade tokio-util to 0.7.17
chore(deps): update rust crate tower-http to v0.6.7
  • Schedule: ["at any time"]
  • Branch name: renovate/tower-http-0.x-lockfile
  • Merge into: main
  • Upgrade tower-http to 0.6.7
chore(deps): update tanstack-query monorepo to v5.90.11
chore(deps): update dependency @​playwright/test to v1.57.0
  • Schedule: ["at any time"]
  • Branch name: renovate/playwright-monorepo
  • Merge into: main
  • Upgrade @playwright/test to 1.57.0
chore(deps): update dependency typescript-eslint to v8.48.0
  • Schedule: ["at any time"]
  • Branch name: renovate/typescript-eslint-monorepo
  • Merge into: main
  • Upgrade typescript-eslint to 8.48.0
chore(deps): update rust crate bon to v3.8.1
  • Schedule: ["at any time"]
  • Branch name: renovate/bon-3.x-lockfile
  • Merge into: main
  • Upgrade bon to 3.8.1
chore(deps): update rust crate bytes to v1.11.0
  • Schedule: ["at any time"]
  • Branch name: renovate/bytes-1.x-lockfile
  • Merge into: main
  • Upgrade bytes to 1.11.0
chore(deps): update rust crate criterion to 0.7
  • Schedule: ["at any time"]
  • Branch name: renovate/criterion-0.x
  • Merge into: main
  • Upgrade criterion to 0.7
chore(deps): update rust crate humantime to v2.3.0
  • Schedule: ["at any time"]
  • Branch name: renovate/humantime-2.x-lockfile
  • Merge into: main
  • Upgrade humantime to 2.3.0
chore(deps): update rust crate rust_decimal to v1.39.0
  • Schedule: ["at any time"]
  • Branch name: renovate/rust_decimal-1.x-lockfile
  • Merge into: main
  • Upgrade rust_decimal to 1.39.0
chore(deps): update rust crate serde_with to v3.16.0
  • Schedule: ["at any time"]
  • Branch name: renovate/serde_with-3.x-lockfile
  • Merge into: main
  • Upgrade serde_with to 3.16.0
chore(deps): update rust crate tokio to v1.48.0
  • Schedule: ["at any time"]
  • Branch name: renovate/tokio-1.x-lockfile
  • Merge into: main
  • Upgrade tokio to 1.48.0
chore(deps): update rust crate uuid to v1.18.1
  • Schedule: ["at any time"]
  • Branch name: renovate/uuid-1.x-lockfile
  • Merge into: main
  • Upgrade uuid to 1.18.1
chore(deps): update rust docker tag to v1.91.1
  • Schedule: ["at any time"]
  • Branch name: renovate/rust-1.x
  • Merge into: main
  • Upgrade rust to 1.91.1-slim
fix(deps): update dependency lucide-react to ^0.555.0
  • Schedule: ["at any time"]
  • Branch name: renovate/lucide-monorepo
  • Merge into: main
  • Upgrade lucide-react to ^0.555.0
fix(deps): update opentelemetry-rust monorepo to 0.31
fix(deps): update rust crate async-openai to 0.30.0
  • Schedule: ["at any time"]
  • Branch name: renovate/async-openai-0.x
  • Merge into: main
  • Upgrade async-openai to 0.30.0
fix(deps): update rust crate prometheus to 0.14
  • Schedule: ["at any time"]
  • Branch name: renovate/prometheus-0.x
  • Merge into: main
  • Upgrade prometheus to 0.14
fix(deps): update rust crate rand to 0.9
  • Schedule: ["at any time"]
  • Branch name: renovate/rand-0.x
  • Merge into: main
  • Upgrade rand to 0.9
fix(deps): update rust crate tracing-opentelemetry to 0.32
  • Schedule: ["at any time"]
  • Branch name: renovate/tracing-opentelemetry-0.x
  • Merge into: main
  • Upgrade tracing-opentelemetry to 0.32
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/setup-node action to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-setup-node-6.x
  • Merge into: main
  • Upgrade actions/setup-node to v6
chore(deps): update dependency eslint-plugin-react-hooks to v7
  • Schedule: ["at any time"]
  • Branch name: renovate/major-react-monorepo
  • Merge into: main
  • Upgrade eslint-plugin-react-hooks to ^7.0.0
chore(deps): update dependency jsdom to v27
  • Schedule: ["at any time"]
  • Branch name: renovate/jsdom-27.x
  • Merge into: main
  • Upgrade jsdom to ^27.0.0
chore(deps): update dependency node to v24
  • Schedule: ["at any time"]
  • Branch name: renovate/node-24.x
  • Merge into: main
  • Upgrade node to 24
  • Upgrade node to 24-alpine
chore(deps): update extractions/setup-just action to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/extractions-setup-just-3.x
  • Merge into: main
  • Upgrade extractions/setup-just to v3
chore(deps): update postgres docker tag to v18
  • Schedule: ["at any time"]
  • Branch name: renovate/postgres-18.x
  • Merge into: main
  • Upgrade postgres to 18
chore(deps): update vitest monorepo to v4 (major)
  • Schedule: ["at any time"]
  • Branch name: renovate/major-vitest-monorepo
  • Merge into: main
  • Upgrade @vitest/coverage-v8 to ^4.0.0
  • Upgrade vitest to ^4.0.0
fix(deps): update dependency openai to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/openai-6.x
  • Merge into: main
  • Upgrade openai to ^6.0.0
fix(deps): update dependency recharts to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/recharts-3.x
  • Merge into: main
  • Upgrade recharts to 3.5.0
fix(deps): update dependency zod to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/zod-4.x
  • Merge into: main
  • Upgrade zod to ^4.0.0
fix(deps): update rust crate axum-test to v18
  • Schedule: ["at any time"]
  • Branch name: renovate/axum-test-18.x
  • Merge into: main
  • Upgrade axum-test to 18.0
fix(deps): update rust crate brotli to v8
  • Schedule: ["at any time"]
  • Branch name: renovate/brotli-8.x
  • Merge into: main
  • Upgrade brotli to 8.0
fix(deps): update rust crate jsonwebtoken to v10
  • Schedule: ["at any time"]
  • Branch name: renovate/jsonwebtoken-10.x
  • Merge into: main
  • Upgrade jsonwebtoken to 10.0

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

@fergusfinn fergusfinn merged commit 9f3c706 into main Nov 27, 2025
6 checks passed
@renovate renovate Bot deleted the renovate/configure branch November 27, 2025 10:00
hachall pushed a commit that referenced this pull request Jan 23, 2026
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
sejori added a commit that referenced this pull request Apr 30, 2026
## Summary

Schema migration plus storage-layer bridge wiring for the multi-step
Open Responses orchestration described in [fusillade
plan](https://github.com/doublewordai/fusillade/blob/main/docs/plans/2026-04-28-multi-step-responses.md).

### Migration
- \`response_step_id\` column on \`http_analytics\` and
\`tool_call_analytics\` (nullable, partial-index).
- CHECK constraint on \`tool_sources.kind\` documenting the supported
set: \`'http'\` (default) and \`'agent'\` (sub-agent dispatch).

### Bridge wiring (\`dwctl/src/responses/store.rs\`)
- \`FusilladeResponseStore\` now holds an
\`Option<PostgresResponseStepManager>\` via a new \`with_step_manager\`
builder. Existing call-sites that don't need multi-step continue to work
unchanged.
- New \`ResponseStore\` trait methods mapped one-to-one to storage
primitives: \`record_step\`, \`mark_step_processing\`,
\`complete_step\`, \`fail_step\`, \`next_sequence\`. The other
multi-step methods (\`next_action_for\`, \`execute_model_call\`,
\`execute_tool_call\`, \`assemble_response\`) fall through to the trait
defaults — those are the heart of the Open Responses domain logic and
warrant focused review under their own follow-up issues.

### \`fail_request\` signature update
\`store::fail_response\` now passes a status code (\`500\` as the
catch-all). This picks up the signature change in fusillade #245 (\`fix:
accept status code in fail_request\`). Without this, neither this PR nor
any future fusillade bump would compile.

### Local-dev overrides (must be removed before merge)
The workspace \`Cargo.toml\` includes \`[patch.crates-io]\` entries
pointing at sibling \`../fusillade\` and \`../onwards\` checkouts. This
is so the bridge wiring can be exercised end-to-end before the upstream
releases land:

\`\`\`toml
[patch.crates-io]
fusillade = { path = "../fusillade" }
onwards = { path = "../onwards" }
\`\`\`

**Remove these before merging.** Once fusillade #248 and onwards #185
are released to crates.io, bump \`fusillade\` and \`onwards\` versions
in \`dwctl/Cargo.toml\` instead.

## Linear coverage

- Parent: [COR-330](https://linear.app/doubleword/issue/COR-330)
- Closes [COR-344](https://linear.app/doubleword/issue/COR-344) —
analytics columns + tool_sources.kind constraint
- Partial [COR-345](https://linear.app/doubleword/issue/COR-345) —
\`FusilladeResponseStore\` storage primitives wired; remaining trait
methods (transition, execution, assembly) deferred to follow-up

### Deferred to follow-ups
- **COR-346/347**: Transition function (Open Responses tool-call
semantics + sub-agent dispatch via \`tool_sources.kind\`).
- **COR-348**: Assembly logic — chain walk → OpenAI Response JSON.
- **COR-349**: \`fusillade::RequestProcessor::process\` dispatching by
endpoint.
- **COR-350**: \`GET /v1/responses/{id}/steps\` endpoint.
- **COR-351**: Extend \`/admin/api/v1/tool-sources\` to accept \`kind\`.
- **COR-352**: Replace \`create_batch_of_1\` with multi-step-capable
creation.
- **COR-353**: SIGTERM drain handler.
- **COR-354**: Surface \`max_response_step_depth\` and
\`max_response_iterations\` as config knobs.

## Validation

End-to-end with the local crate overrides:

- [x] \`cargo build --package dwctl --bin dwctl\` succeeds.
- [x] \`sqlx migrate run\` applies migration #96 cleanly against the
dwctl DB.
- [x] \`response_steps\` table exists in fusillade DB;
\`response_step_id\` columns exist on \`http_analytics\` and
\`tool_call_analytics\` in dwctl DB.
- [x] \`./target/debug/dwctl\` starts up, registers the fusillade
daemon, listens on :3001.
- [x] \`GET /healthz\` returns \`200 OK\`.
- [x] \`GET /admin/openapi.json\` serves the admin API spec.

## Test plan

- [ ] Reviewer: confirm \`[patch.crates-io]\` is removed before merge
once upstream releases land.
- [ ] After merge, follow-up PRs implement the deferred sub-issues
(transition, assembly, etc.) using the bridge wiring this PR
establishes.

---------

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.

1 participant