Skip to content

fix(npm): pin wrapper to a published Python version that loads scenarios/ - #6

Open
sunilp wants to merge 2 commits into
mainfrom
fix-npm-wrapper-pin
Open

sunilp wants to merge 2 commits into
mainfrom
fix-npm-wrapper-pin

Conversation

@sunilp

@sunilp sunilp commented Oct 10, 2026

Copy link
Copy Markdown
Member

The npm wrapper pinned Python agentboundary==0.1.0 (derived from the npm package version), which fails to load the current scenarios/ tree (meta-schema error on scenario 13).

  • npm package version bumped to 0.2.0-alpha.1, equal to pyproject; wrapper derives the PEP 440 pin (0.2.0a1, published on PyPI) from it
  • npm/test/pin.test.js: npm version must equal pyproject version; normalization checked (mutation-checked against the old 0.1.0)
  • CI job npm-pin-loads-scenarios: installs the pinned version from PyPI and loads every scenario in the tree

Verified in scratch venvs: 0.1.0 raises on load; 0.2.0a1 loads all 40. Not published to npm.

Note: scenario 38 fails at run time on 0.2.0a1 and on main source alike (stale-approval check against wall clock, approved_at 2026-06-15 with a 3600s max age). Pre-existing, out of scope here.

🤖 Generated with Claude Code

@coderabbitai

coderabbitai Bot commented Oct 10, 2026 •

Copy link
Copy Markdown

Important

  • 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration
  • Configuration used: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 11412546-66a2-4054-8a65-47d2b3055128

  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

…stale 0.1.0

The wrapper derived its uvx/pipx pin from the npm package version (0.1.0),
and 0.1.0 cannot load the current scenarios/ tree. Bump the npm package to
0.2.0-alpha.1 (equal to pyproject), derive the PEP 440 pin from it, test
that the two stay textually equal, and add a CI job that installs the
pinned release from PyPI and loads every scenario.
@sunilp
sunilp force-pushed the fix-npm-wrapper-pin branch from 3456bbd to 9dba5ba Compare October 11, 2026 01:53
The scitt-alignment release moved pyproject to 0.2.0-alpha.2. The pin test
requires the two to agree, so the wrapper follows.

This branch has not been deployed

No deployments
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