Skip to content

fix: require humanize1 >=0.2.0,<0.3.0 - #6

Merged
futrime merged 1 commit into
mainfrom
fix/require-humanize1-0.2
Oct 5, 2026
Merged

futrime merged 1 commit into
mainfrom
fix/require-humanize1-0.2

Conversation

@futrime

@futrime futrime commented Oct 5, 2026

Copy link
Copy Markdown
Member

humanize1 0.1.x passes the env to spawn() and fork(), which hmz no longer takes since humanfia/humanize#229; humanize1 0.2.0 passes it to Agent.run, as this flow does since #5.

  • README: the humanize1 range is >=0.2.0,<0.3.0, and both git clone --branch lines of humanize1-flow take v0.2.0.
  • CI: tests/test_humanize1_contract.py runs against humanize1-flow v0.2.0.

hmz stays locked at main, as before. The release of this flow follows in its own PR.

🤖 Generated with Claude Code

humanize1 0.1.x passes the env to spawn() and fork(), which hmz no longer
takes since humanfia/humanize#229; 0.2.0 passes it to Agent.run. The README
names the range the flow now works with, and CI and the README check the
stand-in against humanize1-flow v0.2.0.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Copilot AI balanced review requested due to automatic review settings October 5, 2026 15:05

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

@futrime
futrime merged commit ad62ffa into main Oct 5, 2026
6 checks passed
@futrime
futrime deleted the fix/require-humanize1-0.2 branch October 5, 2026 15:07
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.

2 participants