0.328     2026-11-18 03:01:44Z

  - The release test-installs the tarball with "cpanm --test-only" before
    the upload (Author::GETTY::InstallCheck, between TestRelease and
    ConfirmRelease): unpacked outside of the checkout, built from blib, with
    RELEASE_TESTING and AUTHOR_TESTING off, like a user and a CPAN tester
    see it. A failing install test aborts the release, so that nothing is
    uploaded. "no_installrelease" and the Alien options leave it out.

  - Requires CPAN::Meta::Merge 2.150005, so a dist with several
    binaries merges its x_binaries on older perls too.

  - "run_if_trial_<phase>" runs its command only on a trial build or
    release, "run_no_trial_<phase>" only when it is not a trial,
    "run_if_release_<phase>" only during "dzil release" and
    "run_no_release_<phase>" only outside of it. They reach the
    [Run::<Phase>] of their phase as "run_if_trial", "run_no_trial",
    "run_if_release" and "run_no_release", next to "run_<phase>" in the
    same plugin. For a "no_cpan" dist, any of the release-phase keys brings
    the Releaser, so it gets no FakeRelease.

  - The SUPPORT section is written when the dist has an issue tracker or an
    IRC resource.
  - Repository metadata comes from GithubMeta for a GitHub remote, from
    GiteaMeta for a Gitea or Forgejo remote and from [Repository] for any
    other remote; each of them reads origin, or the first remote when there
    is no origin. A repository without a remote builds without one and
    without empty bugtracker or repository entries in META.json.

  - The remote detection and GiteaMeta run git directly, without a shell,
    so GitHub, Gitea and Forgejo remotes are also recognised on native
    Windows, and a remote name reaches git as it is.

  - The prerequisites name what the bundle loads: perl 5.22, the minimum of
    Dist::Zilla and Pod::Weaver, Moose and namespace::autoclean. PAR::Packer
    1.031 is recommended for the local pp check; Module::Runtime and
    Software::License are test requirements.

  - New option family for dists that ship standalone binaries: "binary = name"
    (repeatable) with the optional "binary_modules", "binary_require",
    "binary_platforms", "binary_pp_args", "binary_verify", "binary_smoke" and
    "binary_prepare" keys adds one [@Author::GETTY::Binary / name] subsection
    per binary, and its plugin writes them as "x_binaries" into META.json.
    "binary_default = 0" leaves the subsections out. A binary release is
    published as assets of the GitHub release, so "dzil" now dies at build
    when "binary" is set together with "no_github" or "no_github_release",
    or when the dist has no GitHub remote (which makes "no_github" default
    to on). A trailing "::*" in "binary_modules" packs every module below the
    namespace at any depth, not the module itself (pp gets "-M Foo::**"), which
    is the namespace "binary_require" checks for "Foo::*".
    Dists without "binary" keys are unchanged.

  - The new plugin Author::GETTY::GitHubRelease replaces GitHub::CreateRelease
    for every dist with a GitHub remote: it creates the release as a draft,
    attaches the tarball and only then publishes it, so a release is never
    visible without its tarball. A failed upload or publish fails "dzil release"
    loudly and leaves the draft in place for inspection. The release is
    marked as latest unless the dist ships binaries.

  - A "task" dist stamps Changes with [NextRelease] in the same format and
    UTC time as the other dists, ahead of @Git, so the stamped Changes is
    committed with the release and GitHub::CreateRelease finds its notes.
    Test::ChangesHasContent checks it again (not with "no_changes").

  - A dist with "binary" keys now packs each declared binary with pp during
    "dzil build" and runs its verify and smoke commands on the result, so a
    broken binary already fails the local build. When pp cannot be started,
    the build names the reason. "dzil release" requires
    .github/workflows/binaries.yml calling the shared dzil-binary.yml and
    dies without it. The dzil-test action sets DZIL_BINARY_SKIP=1, so CI
    builds skip the pp step. On native Windows the local pp step starts pp
    with the building perl, writes the binary as NAME.exe and hands
    binary_pp_args and the verify and smoke commands to sh unchanged. The
    verify commands run without PERL5LIB, so the binary under test does not
    see the libraries of its dependencies, and get the PERL5LIB value under
    which the dependencies load as DZIL_BINARY_PERL5LIB (in the CI leg the
    local lib of the dependencies, in the local check the PERL5LIB of the
    caller, empty when there is none); a verify command that needs a perl
    loading the dist's modules runs "PERL5LIB=$DZIL_BINARY_PERL5LIB perl
    -Ilib ...". The smoke commands run without either variable. Dists
    without "binary" keys are unchanged.

  - Build-leg helper scripts for the shared binary release workflow live in
    .github/dzil-binary (plan.pl, pp-args.pl, require-gate.pl, lib-gate.pl,
    win-dlls.pl).
    They plan the platform legs, assemble the pp command line, gate the
    packed binary on its declared requirements and fail it when it links a
    shared library other than the system ones or needs a glibc newer than
    2.28. lib-gate.pl also starts each packed binary once (--help, stdin
    at EOF, a fresh PAR_GLOBAL_TEMP, 60 s bound), checks every native
    object that first start extracts (libperl, the inner executable, PAR's
    own XS) like the packed ones, and fails when no perl library was
    extracted, and a tool it runs (ldd, objdump, otool) that is killed by
    a signal now fails the gate. On Windows the pack step also links (pp -l)
    the DLLs from the packing perl's own perl\bin and c\bin that the packed
    XS needs and the gate would otherwise reject as foreign, such as
    Strawberry's OpenSSL. No effect on dists without "binary" keys.

  - The shared binary release workflow gets its publish-job helper
    .github/dzil-binary/publish.pl (render, expected, sums, check) and the
    install script templates install.sh.in and install.ps1.in. The rendered
    install scripts download the binaries of a GitHub release, verify them
    against SHA256SUMS and install them; install.ps1 defaults to
    %LOCALAPPDATA%\Programs\<dist name>. No effect on dists without "binary"
    keys.

  - The shared binary release workflow .github/workflows/dzil-binary.yml
    (workflow_call, inputs "tag" and "bundle_ref") builds the binaries a
    dist declares on every platform leg with a packing perl of its own
    (.github/dzil-binary/build-perl.sh) and the leg phases of
    .github/dzil-binary/build-leg.sh, gates and verifies them, smoke-tests
    them on clean images and runners, and attaches them with SHA256SUMS,
    install.sh and install.ps1 to the GitHub release. An empty "tag" is a
    probe run that builds the checked-out commit and touches no release;
    its version slot is "probe-<sha7>". A dist calls it from
    .github/workflows/binaries.yml at @binary-v1. No effect on dists
    without "binary" keys. Its publish job marks a release as latest only
    when there is no latest release yet or the latest one is not newer, so
    re-running an older release never rolls releases/latest back, and it
    fails on an empty list of expected binaries. .gitattributes keeps
    .github/dzil-binary at LF line endings on every checkout. Archive::Zip
    is a test requirement.
  - Requires Dist::Zilla::Plugin::Docker::API 0.107 and with it API::Docker
    0.006: when the engine rejects an image build before it has read the
    whole context, the release stops with the engine's error message.

0.327     2026-10-26 00:40:01Z

  - The CI documentation says when the "v1" tag of the dzil-test action
    moves, so it is clear that a dist pinned to "@main" gets every change at
    once while "@v1" gets it when the maintainer moves the tag.

  - A "no_cpan" dist gets [FakeRelease] in place of the removed
    UploadToCPAN, so "dzil release" no longer aborts with "can't release
    without any Releaser plugins" and still tags, bumps the version and
    pushes. It is left out when the dist has a Releaser of its own (the
    default Docker subsection or run_release).

  - Test::ChangesHasContent is no longer added with "no_changes" or "task":
    there is no version heading in Changes then, so its release test could
    only fail.

  - The documentation matches the code: the "equivalent to" listing shows
    the plugins configure() really assembles, and the Docker subsection no
    longer documents a "context" option that was never passed on. The
    cpanfile requires Dist::Zilla::Plugin::Authority 1.009, the version the
    bundle demands at build time.

  - The documented POD commands =resource and =event now work (they were
    passed through as unknown commands and broke POD on MetaCPAN), and the
    docs say that =seealso, =synopsis and =description take no argument.

  - The SUPPORT section no longer says bugs are reported "on GitHub": the
    tracker URL may be a Codeberg or Forgejo one, so the sentence just names
    the link.

  - GitHub and Gitea/Forgejo detection asks git for the remotes instead of
    parsing .git/config, so a dist checked out as a linked worktree or a
    submodule keeps GithubMeta/GiteaMeta, the bugtracker metadata and
    GitHub::CreateRelease. The host is taken from origin, as GiteaMeta does,
    not from whichever remote is listed first.

  - The link to https://raudssus.de/ is added to the COPYRIGHT AND LICENSE
    section by the weaver bundle, so copyright_holder can stay plain text and
    the generated README and LICENSE no longer print "L<...>" markup. A holder
    that still carries the link is not given it twice.

  - The option conflicts (weaver_config with task, author with no_cpan,
    no_install with no_makemaker) now abort with their own message instead
    of "Can't locate object method log_fatal".

  - The Docker subsection no longer sets build_load or passes release_load
    through: Docker::API has dropped both, as nothing ever read them, and
    would warn on every build. The platform option documents that it takes
    exactly one value.

  - New "no_license" attribute: the bundle neither generates a LICENSE nor
    demands a committed one. "no_cpan" now implies it, so a private dist no
    longer aborts with "no LICENSE in the distribution". A LICENSE that is
    committed anyway is still shipped, just no longer checked against
    dist.ini. Set "no_license = 0" to keep the check, or
    "generate_license = 1" to keep the generated file.

  - The shared dzil-test CI action installs from https://cpan.metacpan.org
    by default (same default as the SimpiCI provider). The runner needs an
    https-capable cpanm (curl, wget or IO::Socket::SSL, plus CA
    certificates); the official perl images have that. "cpanm-opts" still
    overrides the default.

  - The SimpiCI provider runs its dzil test jobs in prebuilt images,
    ghcr.io/getty/dzil-perl:<ver> (perl:<ver> with Dist::Zilla, this bundle
    and its author-test deps preinstalled), rebuilt weekly for every version
    in perl-versions, so a job no longer installs ~200 CPAN modules first.
    The job files are now named "ghcr.io+getty+dzil-perl+<ver>+test.sh": a
    dist overriding one version's job ships that name, while a
    "perl+<ver>+test.sh" of its own now runs in addition.

0.326     2026-09-29 17:20:32Z

  - Every distribution built with [@Author::GETTY] now snapshots its agent
    context (.claude/.codex, CLAUDE.md, AGENTS.md, skilletor.lock.json, ...)
    into the build under misc/agent-context/ (present in the tarball, not
    installed), via Dist::Zilla::Plugin::GatherAgentContext. This records which
    skills, agents and rules a release was built with, including
    skilletor-installed (git-ignored) ones. New prereq:
    Dist::Zilla::Plugin::GatherAgentContext.

  - Git::NextVersion version_regexp is now derived from tag_format, so a dist
    without $VERSION in its source finds its last release tag instead of
    restarting at first_version.

0.325     2026-09-22 06:46:49Z

  - Version rewriting defaults to ":InstallModules" and ":PerlExecFiles", so
    modules and Perl executables receive the release version while non-Perl
    programs under "bin/" remain installed without being parsed as Perl.

0.324     2026-09-19 01:05:02Z

  - F<.karr> is now excluded from the gathered distribution files for CPAN
    releases, so it never lands in a consuming dist's release tarball. No
    new toggle -- reuses the existing gather_exclude_filename mechanism
    alongside the README.md exclusion, and is skipped when C<no_cpan> is
    set, so a non-CPAN distribution still ships F<.karr>.

  - Fixed POD for C<alien_build>: it does not set C<no_makemaker> to 1 (that
    claim was wrong and self-contradictory -- C<Alien::Build::MM> munges the
    MakeMaker-generated Makefile.PL, so MakeMaker has to stay).

0.323     2026-09-18 02:52:39Z

  - SimpiCI provider: the generated `dzil test` job now exports
    `DZIL_DOCKER_API_SKIP=1`, so a `[@Author::GETTY::Docker]` distribution tests
    on SimpiCI without `dzil test` trying to reach a container engine and build
    an image from inside the CI perl container (its precheck would otherwise
    fail the run). Harmless for a dist without the Docker plugin.
  - SimpiCI provider: a distribution can restrict the Perl matrix with a
    `.simpici-perl` file at its root (whitespace-separated versions, `#`
    comments), overriding the baked-in default. Needed when a dist's
    `.simpici-apt` requires a Debian release the oldest `perl:<ver>` images no
    longer serve packages for. Precedence: `.simpici-perl`, then
    `SIMPICI_PROVIDER_PERL_VERSIONS`, then the default list.

0.322     2026-09-15 20:09:52Z

  - SimpiCI provider: a distribution can now ship a `.simpici-apt` file listing
    apt packages that every generated `dzil test` job installs before building
    its Perl dependencies -- so a dist needing system libraries (e.g. a libgit2-
    backed dist that builds Alien::Libgit2 from source) tests on SimpiCI without
    a hand-written .cicd job. The file is optional; pure-perl dists are unaffected.
  - Add a SimpiCI provider (simpici-provider/): a pinned OCI image that generates
    a `dzil test` job for every supported Perl version, so a distribution can run
    its tests on SimpiCI with only a workflow and no committed .cicd. Published to
    ghcr.io/getty/simpici-dzil-provider and defaulting to Perl 5.22 through 5.44.
  - bundle_config now uses a classic dereference instead of the postfix `->@*`
    form, so the bundle loads on Perl 5.22 (the previous syntax needed 5.24+).

0.321     2026-08-30 05:47:00Z

  - Require Dist::Zilla::Plugin::Docker::API 0.104, which logs the build
    output of a failed image build before aborting, so the [@Author::GETTY::Docker]
    build reports the failing step instead of only the exit status.

0.320     2026-08-19 17:31:57Z

  - LICENSE is now expected as a committed file in the repository.
    Dist::Zilla::Plugin::License is removed from @Basic and
    Dist::Zilla::Plugin::LicenseFile is added in its place, which aborts the
    build when the committed file is missing or no longer matches the dist's
    license, copyright_holder and copyright_year. Hosting platforms only
    detect a licence they can see in the repository, and a generated LICENSE
    never gets there. Write the file with "dzil genlicense" and commit it.
  - New "generate_license" attribute restores the previous behaviour for
    dists that deliberately ship no committed LICENSE.

0.319     2026-08-17 02:38:51Z

  - The commit that records the $VERSION bump after a release now picks up
    executables in "bin/" as well. @Git::VersionManager only allows
    "^lib/.*\.pm$" to be dirty in that commit, while the bump itself rewrites
    ":InstallModules" and ":ExecFiles" — so every distribution with a script
    in "bin/" left the bumped file uncommitted, and git ended up with a "bin/"
    one release behind its "lib/".

0.318     2026-08-08 23:59:18Z

  - "no_cpan" now defaults "version_finder" to ":MainModule", so a
    distribution that never reaches CPAN keeps its $VERSION in the main
    module only. Setting "version_finder" explicitly still wins.

  - Remove the share/claude-skill.yaml ShareDir. It was an outdated copy of
    the Claude skill (last touched in March, still under the old
    "dzil-author-getty" name) that nothing ever read; the skill is
    distributed via .claude/skills instead. This also drops the
    File::ShareDir::Install configure requirement.

0.317     2026-08-04 22:16:54Z

  - Add "tag_format" bundle option, forwarded to Git::Tag.tag_format (or the
    @Git bundle for task/manual_version dists). Defaults to "%v" as before;
    lets a consuming dist.ini override the release tag's format, e.g. to
    "v%v" when a tag also needs to satisfy another ecosystem's tooling (a Go
    module published from the same tag requires strict vMAJOR.MINOR.PATCH).

0.316     2026-06-19 14:52:42Z

  - Add Gitea/Forgejo repository metadata support via the new
    Dist::Zilla::Plugin::Author::GETTY::GiteaMeta (the Gitea/Forgejo counterpart
    of GithubMeta — repository/bugtracker/homepage derived offline from the git
    remote, no API token). For dists with no GitHub remote, the bundle emits
    this META when the remote host is a known Gitea host (codeberg.org and the
    author's own instance) or when the new "gitea = 1" bundle option is set
    (for any other self-hosted Gitea/Forgejo). Purely additive: GitHub-hosted
    distributions are unaffected; everything else still falls back to
    [Repository].

0.315     2026-05-27 01:49:07Z

  - Add shared composite GitHub Action (.github/actions/dzil-test) that
    centralises Dist::Zilla CI mechanics (authordeps, listdeps --author,
    dzil test) for all [@Author::GETTY] distributions. The --author flag
    installs develop-phase prereqs (e.g. Test::Pod from [PodSyntaxTests])
    so they no longer need to be faked into cpanfile's on-test block.
  - Add .github/workflows/ci.yml — the bundle's own CI dogfoods the action
    via a local path reference.
  - Add CONTINUOUS INTEGRATION section to POD: documents how to use the
    shared action for pure-Perl dists, Alien/XS dists (system libs +
    share-build job), and Forgejo/self-hosted Gitea (full HTTPS URL + probe).

0.314     2026-05-26 15:49:39Z

  - Add Dist::Zilla::Plugin::Test::ChangesHasContent to cpanfile; the
    bundle has been adding [Test::ChangesHasContent] but the prereq was
    missing.
  - [@Author::GETTY]: no_install works again. The wiring that adds
    [MakeMaker::SkipInstall] was accidentally dropped in the Dec 2014
    Git::GatherDir refactor (acc5f0e), while the option, its docs and the
    no_makemaker conflict check were all left in place.

0.313     2026-05-26 13:32:34Z

  - [@Author::GETTY]: new version_finder option restricts which files
    get a $VERSION rewrite. Forwards to PkgVersion (task/manual_version
    path) and to RewriteVersion::Transitional / BumpVersionAfterRelease
    via @Git::VersionManager. Typical use: `version_finder = :MainModule`
    to bump only the main module instead of every .pm in lib/.
  - [@Author::GETTY]: docker_image now auto-adds a single default
    [@Author::GETTY::Docker] subsection so dists without an explicit
    Docker subsection still get a working Releaser. Set
    docker_default = 0 to suppress this when configuring Docker
    builds exclusively through explicit subsections.
  - [@Author::GETTY::Docker]: forward the new build_verbose option
    to [Docker::API]. Default off — the build log shows only step
    headers, not the full per-command output.

0.312     2026-05-18 19:54:12Z

  - [@Author::GETTY::Docker]: default `tags` is now `latest %V %v`
    (was `latest %v`), matching the new Docker::API default. A
    subsection without an explicit `tags = ...` will push three tags
    by default — e.g. `latest`, `0`, and `0.402` for a `0.402`
    release.
  - [@Author::GETTY::Docker]: stop forwarding the removed `context`
    attribute to [Docker::API]; the plugin no longer accepts it.

0.311     2026-05-17 02:29:04Z

  - Add [GitHub::CreateRelease] by default when GitHub integration is active
    (i.e. no_github is not set); reads release notes from Changes file
  - New no_github_release option to opt out without disabling all GitHub integration

0.310     2026-05-17 01:37:28Z

  - Rewrite Author::GETTY::Docker from a non-functional stub into a real
    PluginBundle::Easy subsection bundle; each occurrence creates one Docker::API plugin
  - Subsections inherit image, tags, and local from docker_image / docker_tags /
    docker_local in the parent Author::GETTY section; all three can be overridden
    per subsection
  - Remove single-image Docker path from Author::GETTY: docker_image now acts
    purely as a default for subsections, not as a standalone trigger
  - Remove docker_build and docker_release attributes (were only used by the
    removed single-image path)
  - Subsection without image in either subsection or parent now dies with a
    clear error message instead of silently falling back to dist-name
  - Add comprehensive test suite for all subsection-inheritance scenarios
  - Author::GETTY::Docker now passes the single canonical `tag` attribute
    to Docker::API instead of the deprecated build_tag / release_tag pair;
    requires Docker::API 0.004

0.309     2026-05-16 01:58:24Z

0.308     2026-05-01

  - Add docker_image, docker_build, docker_release, docker_local attributes
  - docker_local=1 adds localhost:5000/ tag variant and forces release_push=0
  - Remove deprecated phase, repository, tag, push, load attributes
  - Requires Dist::Zilla::Plugin::Docker::API 0.003 (was 0.002)

0.307     2026-04-22 04:34:31Z

  - Forward commit_files_after_release option to Git::VersionManager so files
    bumped in run_before_release actually land in the release commit

0.306     2026-03-29 02:24:59Z

0.305     2026-03-28 00:00:54Z

  - Exclude README.md from gathered distribution files by default; allow opt-in with include_readme = 1
  - Add xs_alien and xs_object parameters for automatic MakeMaker::Awesome configuration
  - Add =synopsis, =description, =seealso section shortcuts (→ =head1)
  - Remove =event and =resource commands (not needed)
  - Include AI skill file (share/claude-skill.yaml) in distribution
  - Add alien_build parameter for Alien::Build-based distributions (adds AlienBuild plugin, implies no_makemaker)
  - Fix no_makemaker incorrectly implied by alien_build (AlienBuild needs MakeMaker, not replaces it)

0.304     2026-01-26 05:55:39Z

  - Add alien_build_command, alien_install_command, alien_test_command parameters
  - Add adoptme attribute to mark distributions as available for adoption
  - Add irc_user attribute for configurable IRC contact in SUPPORT section

0.303     2026-01-13 23:01:57Z

  - Add authority attribute to override x_authority metadata
  - Fix Git::Push not being added after Git::VersionManager

0.302     2026-01-13 22:58:13Z

  - Add alien_repo, alien_name, alien_bins, alien_pattern parameters for Alien distributions

0.301     2026-01-10 23:37:10Z

  - Added missing changelog entries for 0.300

0.300     2026-01-10 23:34:35Z

  - Add Pod::Elemental::Transformer::Author::GETTY for inline POD commands
  - New commands: =attr, =method, =func, =opt, =env, =event, =hook, =resource, =seealso, =example
  - Commands transform to =head2 and stay inline with code (not collected into sections)
  - SUPPORT section now shows GitHub Issues and IRC info
  - Add separate CONTRIBUTING section
  - Add irc and irc_server attributes for IRC metadata
  - Enable GithubMeta issues => 1 for automatic bugtracker URLs
  - Change default release_branch from master to main

0.204     2025-12-25 22:30:43Z

  - Removing unnecessary Moose::Autobox include

0.203     2025-12-25 19:41:43Z

  - Updated Changes file to new format.

0.202     2025-12-25 05:23:30Z

  - Switch to Dist::Zilla::PluginBundle::Git::VersionManager

0.120     2024-08-10 02:38:09Z

  - Fixing some details after hints of ether

0.117     2024-08-10 00:17:10Z

  - Adding Encoding Plugin

0.116     2024-07-03 00:59:55Z

  - Weaver Section Support added

0.115     2024-06-16 04:38:21Z

  - Removing TravisCI completely, removing BumpVersionFromGit

0.114     2023-05-22 21:45:41Z

  - Added deprecated feature

0.113     2023-05-21 18:19:59Z

  - Adapting documentation
  - Remove travis.yml, adding gather parameters

0.112     2021-10-23 14:44:59Z

  - Updated .travis.yml
  - Alien: also support the version_check attribute (Wouter Verhelst, PR #5)
  - Updated .travis.yml with newest version of TravisCI plugin
  - New travis configuration

0.111     2019-08-25 16:33:10Z

  - Remove PruneCruft, updated doc
  - Starting to add dotfiles in Git::Gathering

0.110     2015-02-05 04:36:52Z

  - New travis.yml
  - Attempt to resolve version regexp for changelog generation; permit
    tags that are versions but lack a 'v' prefix to be considered version
    tags (Kent Fredric, PR #4)
  - Add support for [Alien] bin_requires (Graham Ollis, PR #3)

0.109     2015-02-05 04:22:14Z

  - Fixed docs

0.108     2015-02-05 03:32:16Z

  - XS functionality

0.107     2014-12-31 22:32:59Z

  - GatherDir replaced with Git::GatherDir

0.106     2014-11-27 04:22:53Z

  - Fixed huge bug about travis and run integration, logical this gives
    also a new .travis.yml ;)

0.105     2014-11-25 16:13:47Z

  - Removed legacy, fixed the Repository<=>GithubMeta collide introduced
    by latest Dist::Zilla updates

0.104     2014-09-25 12:43:09Z

  - Bootstrapme! kentnl++

0.103     2014-09-22 18:11:23Z

  - Bumped requirement of dzil alien plugin
  - Support for Alien::Base 0.005 features (Graham Ollis, PR #2)

0.101     2014-07-05 19:20:21Z

  - Switched to Prereqs::FromCPANfile

0.016     2013-12-24 00:44:53Z

  - Several changes involving adding more no_ parameter for non cpan
    distributions

0.015     2013-05-02 11:55:41Z

  - Switched over to [TravisCI]

0.014     2013-04-21 00:01:41Z

  - Added switch to deactivate ChangelogFromGit in favour for NextRelease

0.013     2013-04-20 23:21:32Z

  - Now with working requirements

0.012     2013-04-20 23:19:59Z

  - Added TravisYML
  - Micro documentation flaw fixed (bad example distribution name)

0.011     2013-03-02 22:54:30Z

  - Bumped requirement versions, tuned documentation massively

0.010     2013-03-02 19:21:42Z

  - Option to directly add [Alien] for the test

0.009     2013-03-02 17:02:49Z

  - Added Test::LoadAllModules to requirement base

0.008     2013-02-26 21:26:23Z

  - Added new features to modify install release command (or deactivate
    it totally)

0.007     2013-02-26 01:46:49Z

  - Added no_makemaker flag

0.006     2013-02-08 00:20:20Z

  - Hups... fixed the new features ;)
  - Fixed small typo in SYNOPSIS

0.005     2013-02-04 02:10:04Z

  - Added several features like Dist::Zilla::Plugin::Run integration and
    duckpan / no_cpan / no_install options

0.004     2013-02-03 23:50:08Z

  - Added author and release_branch option for configuration

0.003     2012-10-01 01:37:30Z

  - Added Git::CheckFor::CorrectBranch

0.002     2012-07-05 12:37:17Z

  - Missed adding ChangelogFromGit to the POD documentation

0.001     2012-07-05 11:48:31Z

  - Initial commit, copy of old bundle + adding Changes from git
