Release history for perl-Dist-Zilla-Plugin-Manifest-Write
v0.8.1_02-TRIAL @ 2015-10-02 13:28 UTC
- `example.t` test is too sensitive: it requires the manifest samples saved in `ex/`
subdirectory, are generated with current version of the plugin, otherwise the test fails
doe to different files. The test fixed. Now change in the plugin version does not cause the
test failure.
- Bug found: when the plugin adds itself to the list of metainfo providers, it adds plugin
moniker (but should add plugin name). Fixed.
- Problem found: Dist::Zilla plugins used in tests are not included into `Meta.JSON` as
test requirements. Fixed.
v0.8.1_01-TRIAL @ 2015-10-01 22:06 UTC
- In documentation, code and comments the terms "plugin name" and "plugin moniker" used more
accurately. To the manual added a section explaining these terms.
- Options `source_providers` and `metainfo_providers` changed a bit. Now they split their
values at whitespace (`\s+`) not on plain space.
- Options `source_provider` and `metainfo_provider` introduced. Each option treats its value
as *one* plugin name. It allows to operate with plugin names containing spaces.
- Option `show_mungers` introduced. By default mungers are not shown because this information
is unreliable. See <https://github.com/rjbs/Dist-Zilla/issues/495>
- Testing improved. Added a test routine (it is used in every test) to read generated
`MANIFEST` with `ExtUtils::Manifest::maniread` and verify read content. That actually means
my manifest is tested on compatibility with `MakeMaker`.
- If filename includes hash character, filename in manifest will be written as single-quoted
string. It prevents interpreting a file which name starts with hash as a comment.
- From user point of view, this version is almost compatible with the previous (except very
minor change in `source_providers` and `metainfo_providers`). However, in class interface
there are incompatible changes. Some methods are renamed, some changed, so subclasses or
other clients should be modified to work with the new version. (Frankly, I do not think
someone uses it programmatically.)
v0.8.1 @ 2015-09-15 21:00 UTC
- Bunch of build infrastructure changes, not visible to end users.
- `ReadMe.pod` dropped.
- Version switched from old decimal style to new dotted-decimal style.
0.008 @ 2015-08-10 14:37 UTC
- Debug message improved. Old message was a caught exception and being printed with no
explanation, was a bit frightening.
- Packaging bug fixed: `Utils::fill_in` trigged creation metadata too early, even before file
gathering is complete. This breaks `MetaProvides::Package` plugin, and leads to empty
`provides` metadata, so v0.007 was not properly indexed by CPAN.
0.007 @ 2015-08-09 17:57 UTC
- A test module now explicitly requires `Moose` v2.0800. Older `Moose` versions causes test
failure.
0.006 @ 2015-07-23 19:11 UTC
- Implemented validation of `source_providers` and `metainfo_providers` options.
- Implemented option `strict` which controls strictness of checks above.
- As usual, bunch of infrastructure changes.
0.005 @ 2015-07-15 20:47 UTC
- Added support for templates with non-standard names. e. g. `[=MyLocalPlugin]`.
- Word "built" is used instead of "generated" in `MANIFEST`. It is shorter, and has the same
lengths as "added", so text now looks much better.
- Changed detection of generated files. Now the plugin checks file class — if a file is of
`Dist::Zilla::File::OnDisk` class, it is considered as added file, otherwise — -generated-,
sorry, built.
- Code reorganized for better modularity. Now it is easier to hack the plugin through
subclassing.
0.004 @ 2015-07-09 14:23 UTC
- **Incompatible change:** `dist.ini` file options `source_provider` and `metainfo_provider`
are replaced with plural counterparts: `source_providers` and `metainfo_providers`. New
options allow users to specify multiple space-separated providers in one option. Multiple
options are also allowed, as before.
- Documentation improved.
- Bunch of infrastructure changes not visible to the module users: (a) test rewritten with
`Test::Routine`, (b) documentation generation reworked, (c) added special test for
synopsis, (d) added bunch of generated tests like POD spell checking.
0.003 @ 2015-07-06 13:31 UTC
- `Dist-Zilla` older than v5.023 causes runtime error because `_added_by` field was a string,
not arrayref. Now `Write.pm` explicitly requires `Dist::Zilla::Role::File` v5.023 to avoid
this error.
- Build: `Test::PodSpelling` plugin used, few spelling errors found and fixed.
0.002 @ 2015-07-04
- `AutoPrereqs` `Dist-Zilla` plugin fails to detect some implicit prereqs in test script, it
may cause test failure. Code changed to make that hidden dependencies explicit.
0.001 @ 2015-07-03
- Initial revision