Skip to content

fix: parse pyproject entry points as installed commands - #30

Merged
rogerchappel merged 3 commits into
mainfrom
agent/oss-bbf39c3f3a95-pyproject-entrypoints
Aug 23, 2026
Merged

rogerchappel merged 3 commits into
mainfrom
agent/oss-bbf39c3f3a95-pyproject-entrypoints

Conversation

@rogerchappel

Copy link
Copy Markdown
Owner

Summary

  • report [project.scripts] and [tool.poetry.scripts] keys as their installed console commands
  • retain real string command values for [tool.poe.tasks] and label their runner accurately
  • replace the invalid fixture, document the supported sections, and ignore unsupported values conservatively

Commits

  • 5f88924 test: define pyproject command semantics
  • 12f048b fix: parse pyproject entry points by section
  • 731d3d7 docs: explain pyproject command discovery

Verification

  • npm ci
  • npm test (25/25)
  • npm run check
  • npm run smoke
  • npm run package:smoke
  • git diff --check

@rogerchappel

Copy link
Copy Markdown
Owner Author

Automated merge note

Triage class: auto-merge

Summary: Parses standards-defined pyproject entry-point keys as installed runnable commands while preserving Poe task command values, with deterministic regression coverage and aligned documentation (4 files, +58/-4).

Checks run: GitHub CI Repository hygiene and Release dry-run dry-run completed SUCCESS; worker evidence records npm ci, npm test (25/25), npm run check, npm run smoke, npm run package:smoke, and git diff --check; final diff and branch protection reverified.

Rebased/CI-repaired: No.

Verified head SHA: 731d3d7330fa2e1f56f0b8279be9da738217909a.

@rogerchappel
rogerchappel merged commit 27877f6 into main Aug 23, 2026
2 checks passed
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