Skip to content

fix(packaging): reconcile component floors with normalized providers - #416

Closed
ywatanabe1989 wants to merge 112 commits into
developfrom
fix/reconcile-component-cohort-1120
Closed

ywatanabe1989 wants to merge 112 commits into
developfrom
fix/reconcile-component-cohort-1120

Conversation

@ywatanabe1989

Copy link
Copy Markdown
Member

The current public umbrella cannot join the Hub/FigRecipe development profile: SciTeX 2.30.8 pins FigRecipe 0.29.9, while Hub needs >=0.44.7. The older resolver-compatible SciTeX 2.29.3 still registers retired linter rule STX-I004.

This candidate combines the existing component-floors work (PR393) with the existing provider/interface normalization and IO contract work (PR387/PR390). It retains the normalization branch's dependency versions and changes its 94 exact component requirement occurrences to minimum floors. Existing dependency-floor regressions remain intact; no provider, audit or dependency check is disabled. Skill conflicts retain the source-backed normalized pages, and both changelog histories are preserved.

Scoped validation: three source dependency-floor checks pass (installed-metadata check awaits the candidate installation); eight optional-browser/docs error-propagation checks pass using installed Dev 0.64.1. The project audit reports zero errors, 153 warnings and one info. Static review of the three skill pages is incomplete for dynamic/external calls. The normal isolated wheel build and actual candidate installation are tracked separately; build completion alone is not documentation content acceptance.

Keep this draft held for complete original CI, artifact/docs and joint-cohort acceptance. Both original 60-second Python 3.12 failures and the original 57-error audit remain recorded; this source combination neither reruns nor erases them. No release, publication, deadline/resource change or development-service rollout is authorized by these scoped results. Private same-version wheels are NEVER_UPLOAD.

ywatanabe1989 and others added 30 commits June 20, 2026 23:52
promote(develop->main): umbrella 2.30.2 release-prep — drop 120MB blob + reconcile leaf pins
The operative legal terms (sections 0-17) already govern under AGPL-3.0;
this only removes the FSF template's generic "or any later version"
placeholder from the non-operative How-to-Apply section, matching
pyproject.toml's license = "AGPL-3.0-only" declaration.
chore(release): promote develop → main
release: promote SciTeX 2.30.9 to main
…h-1105

docs: refresh public README and umbrella skill guides
ywatanabe1989 and others added 28 commits November 9, 2026 14:10
Installing the umbrella replaced newer, already-installed components with
the old pinned wheels (scitex-io 0.3.3, scitex-dev 0.62.2, ...), and made
develop scitex-session 0.3.2 (needs scitex-dev>=0.62.28) uninstallable next
to the umbrella. Every exact component pin in core deps and extras becomes
a >= floor at the previously pinned, CI-validated version; exact versions
belong in experiment/deployment lock files.

- tests/scitex/test_dependency_floors.py: regression guard over the real
  pyproject and installed metadata (no mocks), with a positive control.
- Skills/MCP resources/docs: stx.INJECTED -> stx.session.INJECTED (the
  top-level alias is deprecated by the umbrella itself).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
CI py3.11 (tests workflow) failed at collection: with the component
floors, uv backtracked to fastmcp 2.14.1, whose open-ended
`mcp>=1.24.0` admitted mcp 2.3.0, which removed
mcp.shared.exceptions.McpError that fastmcp 2.x imports. The umbrella
imports fastmcp directly (scitex._mcp, scitex.cli.mcp) but never
declared it; fastmcp 3.0.0 is the first release declaring mcp<2.0, so
it is the lowest coherent floor. py3.11 now resolves fastmcp 4.2.0 and
the suite passes locally (444 passed, 0 failed).

Quality audit (scitex-dev 0.62.30) findings this PR introduced:
- PS-204 orphan test: move test_dependency_floors.py to tests/integration/
  (cross-cutting packaging contract, no src counterpart).
- PS-235 install-profile fallback in the legacy pytest workflow: install
  exactly one profile, [all,dev], and fail on error instead of silently
  testing a smaller dependency set.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions github-actions Bot locked and limited conversation to collaborators Nov 20, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant