Repository navigation
feat(flaskapi): pin itis-sumo==0.1.0a4 (Dakota 6.24) — modernization rung 2 - #559
Conversation
…rung 2 Bump the itis-sumo consume pin 0.1.0a3 -> 0.1.0a4. This pulls itis-dakota ==6.24.7 transitively (Dakota 6.20 -> 6.24 engine bump, itis-sumo T16mo rung 2). 6.24.7 is the latest 6.24.x still shipping cp311 wheels, so the Python 3.11 baseline is retained. Full CI green: flaskapi 507+15, node 160, e2e 6 (pixel snapshots vs committed baselines). The backend exercises itis-sumo a4 through real Dakota 6.24.7 subprocesses inside the e2e flow and the snapshots match.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #559 +/- ##
==========================================
Coverage ? 42.92%
==========================================
Files ? 13
Lines ? 1894
Branches ? 0
==========================================
Hits ? 813
Misses ? 1081
Partials ? 0
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Pull request overview
This PR updates the Flask API’s pinned itis-sumo dependency to the next alpha release (0.1.0a4) from the explicitly-configured TestPyPI index, which in turn updates the resolved Dakota engine dependency line to itis-dakota==6.24.7.
Changes:
- Bump
itis-sumopin from0.1.0a3to0.1.0a4inflaskapi/pyproject.toml. - Refresh
flaskapi/uv.lockto resolveitis-sumo==0.1.0a4and its transitive update toitis-dakota==6.24.7(plus updated wheel/sdist metadata).
Reviewed changes
Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| flaskapi/pyproject.toml | Updates the direct dependency pin to itis-sumo==0.1.0a4 while keeping the existing explicit TestPyPI source configuration. |
| flaskapi/uv.lock | Updates the lock resolution to match the new itis-sumo pin and the resulting Dakota engine version/wheels. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
What
flaskapi/pyproject.toml:itis-sumo==0.1.0a3→itis-sumo==0.1.0a4(TestPyPI).flaskapi/uv.lock:itis-sumo a3 → a4, transitivelyitis-dakota 1.5.11 → 6.24.7(Dakota 6.20 → 6.24 engine bump, itis-sumo T16mo rung 2).Why
Consumer side of modernization rung 2.
itis-sumo0.1.0a4 moves off the Dakota-6.20 engine line ontoitis-dakota==6.24.7(Dakota 6.24). 6.24.7 is the latest 6.24.x that still ships cp311 wheels, so the Python 3.11 baseline (parity with mmux/vite) is retained — 6.24.8+ dropped cp311 and would force a 3.12 migration (deferred).The itis-sumo-side
interface_cacheregression (SPEC §R5, broke all real-Dakota surrogate tests on 6.24.x) is shimmed inside itis-sumo, not in this repo. No mmux_vite code changes beyond the pin.Verification
Full CI green against
0.1.0a4:build-no-cache): okThe backend exercises itis-sumo a4 through real Dakota 6.24.7 subprocesses inside the e2e flow and the snapshots match.
Notes
explicit;itis-sumosourced fromtestpypi(unchanged).