I once wrote a little script ("podbuilder") creating a .pod file for my module (and manifest, README and so on) from templates.

( because perldoc <MODULE> will show the content of <MODULE>.pod (if present) instead of <MODULE>.pm )

It also does a parsing of my module's POD for comments which are meant to be part of the interface description including $VERSION

Since the script is part of the test suite and/or commit-hook all files are automatically updated.

So instead of "reversioning" all files I only update the main code's $VERSION. ²

But I have to admit I never really used Pod::Weaver or Dist::Zilla , so I can't tell how many wheels I reinvented, BUT it has no dependencies³.

²) which shouldn't be done without running the test-suite anyway

³) which means I can distribute it with my module, without blowing up the dependencies.