Repository navigation
chore(deps): bump itis-sumo 0.1.0a10 -> 0.1.0a11 (additive report facade; zero pixel drift) - #694
JavierGOrdonnez wants to merge 2 commits into
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #694 +/- ##
============================================
+ Coverage 50.63% 85.50% +34.87%
============================================
Files 107 109 +2
Lines 5350 12978 +7628
Branches 605 1352 +747
============================================
+ Hits 2709 11097 +8388
+ Misses 2563 1770 -793
- Partials 78 111 +33
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.
Copilot review overview
🟢 Approval recommended
The dependency declaration, lockfile, and specification are consistent, with no unresolved compatibility issues found.
Review effort: Balanced
Findings: None
What changed in this PR
Updates the Flask API’s itis-sumo dependency to additive release 0.1.0a11.
Changes:
- Bumps and locks
itis-sumoto0.1.0a11. - Synchronizes the lockfile’s root package version.
- Updates the documented compute pin.
| File | Description |
|---|---|
flaskapi/pyproject.toml |
Updates the dependency pin. |
flaskapi/uv.lock |
Locks the new artifacts and synchronizes package metadata. |
flaskapi/SPEC.md |
Documents the updated compute version. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
…frozen Two sides of one trap the auto-version bot set today: - the bot stamps pyproject with PEP440 dev versions (1.6.3.dev2); a plain 'uv run' (ty hook) auto-syncs and mirrors that stamp into uv.lock -- whose project version feeds the image build's oSPARC MetadataConfig, which validates SEMVER (verify-image-build failed on #694's first push for exactly this). This commit restores the lock to 1.6.3 (as on develop) and switches the hook to 'uv run --frozen' (installs from lock as-is, mirroring the CI 'uv sync --frozen' convention), so no future flaskapi-touching PR can be forced to propagate the dev stamp into the lock.
|
Consequence: every PR branched from today's develop fails |
a11 (itis-sumo#54) promotes the incubator tooling + adds the curated itis_sumo.report facade for notebook consumers - additive to the itis_sumo.api surface flaskapi consumes. - flaskapi 582 pass/3 skip @93%; analytical (real Dakota) 2/2 - e2e in pinned playwright:v1.63.0-noble: 20/20, ZERO pixel drift (no regen needed; baselines untouched by design) - SPEC: §C compute pin line synced; §B B32gs history row left at a10 (historical record: that fix landed WITH a10) - uv.lock also syncs the stale self-version stamp (1.6.3 -> 1.6.3.dev2)
…frozen Two sides of one trap the auto-version bot set today: - the bot stamps pyproject with PEP440 dev versions (1.6.3.dev2); a plain 'uv run' (ty hook) auto-syncs and mirrors that stamp into uv.lock -- whose project version feeds the image build's oSPARC MetadataConfig, which validates SEMVER (verify-image-build failed on #694's first push for exactly this). This commit restores the lock to 1.6.3 (as on develop) and switches the hook to 'uv run --frozen' (installs from lock as-is, mirroring the CI 'uv sync --frozen' convention), so no future flaskapi-touching PR can be forced to propagate the dev stamp into the lock.
16a9534 to
def6c13
Compare
What
Bump
itis-sumo==0.1.0a10→0.1.0a11(TestPyPI). a11 (itis-sumo#54) promotes incubator tooling and lands the curateditis_sumo.reportfacade for notebook consumers — additive to theitis_sumo.apisurface this repo consumes. Follow-on tracked on the portage ledger after the backend portage (#688) landed.Syncs:
pyproject.toml,uv.lock, and theflaskapi/SPEC.md§C compute-pin line. The §BB32gsrow deliberately keepsa10(historical record — that bug's fix shipped with a10).Verification (all local, then CI)
mcr.microsoft.com/playwright:v1.63.0-noble: 20/20, zero pixel drift — no baseline regen in this PR (none needed; §C keeps baselines fixed across refactors)uv lockalso corrects a stale root-version stamp in the lockfile (1.6.3→1.6.3.dev2)Addendum: CI-hardening commits (the bump surfaced a live trap)
First push was green except
verify-image-build: myuv lockrun mirrored the auto-version bot's PEP440 stamp (pyproject = 1.6.3.dev2, stamped post-#688) intouv.lock, and the image build's oSPARCMetadataConfigvalidates the lock-derived version as semver. The lock's released1.6.3on develop is load-bearing.16a95349carries the minimal repair:uv.lockproject version to1.6.3(develop parity),uv runtouv run --frozen— without this, every future flaskapi-touching PR would face the same wall: the hook's auto-sync rewrites the lock (breaking commit/prek) or the rewritten stamp breaksverify-image-build. This alone unblocks the queue; a systemic fix for the stamp chain is filed separately.