• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

peczenyj / GDPR-IAB-TCFv2 / 25595491423
96%
main: 96%

Build:
Build:
LAST BUILD BRANCH: devel
DEFAULT BRANCH: main
Ran 09 May 2026 07:46AM UTC
Jobs 1
Files 16
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

09 May 2026 07:35AM UTC coverage: 96.256%. Remained the same
25595491423

push

github

peczenyj
chore(make): align Makefile.PL with mojo-mcp template + fix recommends

Two changes in one commit -- the structural alignment was the trigger,
the recommends fix surfaced when verifying the rendered META.

1. Structural alignment with the mojo-mcp Makefile.PL template:

   * Reorder top-level WriteMakefile keys: identification first
     (NAME, VERSION_FROM, ABSTRACT_FROM, AUTHOR, LICENSE), then
     constraints (MIN_PERL_VERSION, EXE_FILES), then deps.
   * Reorder META_MERGE keys to match mojo-mcp's idiom:
     dynamic_config, meta-spec, no_index, prereqs, provides,
     resources, x_authority.
   * Add `no_index => { directory => ['xt', 'bench', 'docs'] }` so
     PAUSE/MetaCPAN don't index dev-only dirs.
   * Add `prereqs.runtime.requires.perl => '5.008009'` -- duplicates
     the top-level MIN_PERL_VERSION but is the META-spec-canonical
     declaration that strict consumers honor.
   * Add `license => ['http://dev.perl.org/licenses/']` to resources
     so the URL form (not just the symbolic 'perl_5') is in META.
   * Comment the META_MERGE eval guard so future readers know why we
     can't unconditionally emit META v2 (Perl 5.8.9 ships EUMM 6.42).
   * Sort `resources` keys alphabetically.

2. Pre-existing bug fix: `recommends` was being silently dropped.

   The previous Makefile.PL had `recommends` as a top-level key inside
   META_MERGE. That's the META v1 shape; META v2 requires it under
   `prereqs.runtime.recommends`. EUMM's CPAN::Meta::Converter does
   not auto-relocate it, so the rendered META.json shipped with no
   recommends block at all. Verified by inspecting the rebuilt
   tarball: `META.json runtime.recommends count: 6` (was 0 prior
   to this commit).

   That means JSON::PP / Time::Piece / HTTP::Tiny / JSON / JSON::XS /
   DateTimeX::TO_JSON have never been honored by `cpanm
   --with-recommends GDPR::IAB::TCFv2` since the recommends block
   was first added. CMPValidator users had to install them by hand
   (or rely on the l... (continued)

1157 of 1202 relevant lines covered (96.26%)

8836.18 hits per line

Jobs
ID Job ID Ran Files Coverage
1 25595491423.1 09 May 2026 07:46AM UTC 16
96.26
GitHub Action Run
Source Files on build 25595491423
  • Tree
  • List 16
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • 00458eb0 on github
  • Prev Build on release/0.400 (#25595148066)
  • Next Build on release/0.400 (#25595701217)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc