Skip to content

fix: sync cpanfile and META_MERGE dependency versions - #294

Draft
toddr-bot wants to merge 2 commits into
cpan-authors:mainfrom
toddr-bot:koan.toddr.bot/fix-cpanfile-iopty-version
Draft

fix: sync cpanfile and META_MERGE dependency versions#294
toddr-bot wants to merge 2 commits into
cpan-authors:mainfrom
toddr-bot:koan.toddr.bot/fix-cpanfile-iopty-version

Conversation

@toddr-bot

Copy link
Copy Markdown
Contributor

What

Fix dependency version mismatches between cpanfile, Makefile.PL, and META_MERGE.

Why

Two packaging inconsistencies:

  1. cpanfile IO::Pty version (1.08) doesn't match Makefile.PL (1.25). When IO::Pty 1.25 was required (commit 198fb75) for DESTROY compatibility, cpanfile wasn't updated. Users installing via cpanfile get an IO::Pty too old for the pty tests.
  2. META_MERGE lists Readonly::Array as a build dependency, but Readonly::Array is a function in the Readonly package, not a standalone CPAN module. In Readonly 2.00+, there is no Readonly/Array.pm file. The correct module name is Readonly.

How

  • cpanfile: IO::Pty 1.081.25
  • Makefile.PL META_MERGE build_requires: Readonly::ArrayReadonly, Test::More version synced to 0.47

Testing

  • make test: 863/863 pass (pty.t skips, pre-existing on this system)
  • Verified MYMETA.yml/json contain corrected Readonly (not Readonly::Array)

🤖 Generated with Claude Code

toddr-bot and others added 2 commits April 15, 2026 12:28
Makefile.PL was bumped to require IO::Pty 1.25 (commit 198fb75) to
ensure compatibility with IO::Pty DESTROY changes, but cpanfile was
not updated. Users installing via cpanfile would get 1.08, which is
too old and triggers pty test failures.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Readonly::Array is a function in the Readonly package, not a standalone
CPAN module. In Readonly 2.00+, there is no Readonly/Array.pm file at
all. Replace with the correct module name 'Readonly'.

Also sync Test::More version to '0.47' to match PREREQ_PM.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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