dzil setup

releases
Yanick Champoux 2022-07-25 13:28:29 -04:00
parent f012489e34
commit 4c315f9a04
13 changed files with 271 additions and 172 deletions

1
.gitignore vendored
View File

@ -2,3 +2,4 @@
.build
.perl-version
.pls_cache/
App-Changelord-*

17
.travis.yml Normal file
View File

@ -0,0 +1,17 @@
---
before_install:
- export HARNESS_OPTIONS=j10:c HARNESS_TIMER=1
- git config --global user.name "Dist Zilla Plugin TravisCI"
- git config --global user.email $HOSTNAME":not-for-mail@travis-ci.com"
install:
- cpanm --with-recommends --installdeps -n .
language: perl
matrix:
include:
- perl: '5.22'
- perl: '5.24'
- perl: '5.26'
- perl: '5.28'
- perl: '5.30'
script:
- prove -l t

13
AUTHOR_PLEDGE Normal file
View File

@ -0,0 +1,13 @@
# CPAN Covenant for App-Changelord
I, Yanick Champoux <yanick@babyl.ca>, hereby give modules@perl.org permission to grant co-maintainership
to App-Changelord, if all the following conditions are met:
(1) I haven't released the module for a year or more
(2) There are outstanding issues in the module's public bug tracker
(3) Email to my CPAN email address hasn't been answered after a month
(4) The requester wants to make worthwhile changes that will benefit CPAN
In the event of my death, then the time-limits in (1) and (3) do not apply.

View File

@ -1,89 +0,0 @@
---
project:
name: App::Changeman
homepage: https://git.babyl.ca/yanick/App-Changelord
releases:
- version: v3.0.2
date: 2022-06-17
changes: ~
- version: v3.0.1
date: 2022-06-17
changes: ~
- version: v3.0.0
date: 2022-06-17
changes: ~
- version: v2.0.0
date: 2022-06-17
changes: ~
- version: v1.2.3
date: 2022-01-02
changes:
- desc: doing the thing
type: feat
- |
## [2.0.0](https://github.com/yanick/json-schema-shorthand/compare/v1.0.0...v2.0.0) (2020-08-24)
### BREAKING CHANGES
* things should continue to work as normal, but since to
typescript is kinda of a big deal, I'm taking no chance.
### Features
* move project to typescript ([ca3429d](https://github.com/yanick/json-schema-shorthand/commit/ca3429db04ebc183d2b5c000e8d3d2b297a1e001))
## [1.0.0](https://github.com/yanick/json-schema-shorthand/compare/v0.3.2...v1.0.0) (2020-07-30)
### Features
* add allOf, anyOf, oneOf, not shorthands ([b47ee27](https://github.com/yanick/json-schema-shorthand/commit/b47ee27671a4861756a74f4ad6b0dc10d10f1a3c))
### [0.3.2](https://github.com/yanick/json-schema-shorthand/compare/v0.3.1...v0.3.2) (2020-01-31)
### Bug Fixes
* remove shrinkwrap.yaml from repo ([baf6ca5](https://github.com/yanick/json-schema-shorthand/commit/baf6ca5c27f9f7723afa48796da0627160579839))
## 0.3.1 (https://github.com/yanick/json-schema-shorthand/compare/v0.3.0...v0.3.1) (2020-01-31)
### Bug Fixes
* bump dependency versions to latest (685e13e (https://github.com/yanick/json-schema-shorthand/commit/685e13eba976fda5ba956a105ac2fb039e232860))
## v0.3.0 2018-02-14
## Improvements
* New shortcut: '$foo' expands to be `$ref: foo`.
* New 'range' shortcut.
* New shortcut functions for types `object`, `array`, `number`,
`integer`, and `string`.
* Add `add_definition` helper function.
### Bug Fixes
* `shorthand()` deals gracefully with `null` argument.
## 0.2.0 2017-01-03
* Properties can be made required via a '!' suffix.
* Drop Mocha and Chai for TAP for testing.
- version: 0.1.0
date: 2016-08-01
changes:
- "Recurse down 'allOf', 'oneOf', 'anyOf', 'not'."
- Add 'install' and 'synopsis' sections in doc.
- version: 0.0.1
date: 2016-07-31
changes:
- Initial release
change_types:
- feat:
level: minor
title: Features
keywords: []
- fix:
level: patch
title: Bug fixes
keywords: []

View File

@ -1,14 +0,0 @@
# Changelog for [App::Changelord][homepage]
[homepage]: https://git.babyl.ca/yanick/App-Changelord
## v0.0.1, 2022-06-25
* Initial release
### Statistics
* code churn: 27 files changed, 1281 insertions(+)

View File

@ -1,59 +0,0 @@
# Changelog
All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines.
## [2.0.0](https://github.com/yanick/json-schema-shorthand/compare/v1.0.0...v2.0.0) (2020-08-24)
### ⚠ BREAKING CHANGES
* things should continue to work as normal, but since to
typescript is kinda of a big deal, I'm taking no chance.
### Features
* move project to typescript ([ca3429d](https://github.com/yanick/json-schema-shorthand/commit/ca3429db04ebc183d2b5c000e8d3d2b297a1e001))
## [1.0.0](https://github.com/yanick/json-schema-shorthand/compare/v0.3.2...v1.0.0) (2020-07-30)
### Features
* add allOf, anyOf, oneOf, not shorthands ([b47ee27](https://github.com/yanick/json-schema-shorthand/commit/b47ee27671a4861756a74f4ad6b0dc10d10f1a3c))
### [0.3.2](https://github.com/yanick/json-schema-shorthand/compare/v0.3.1...v0.3.2) (2020-01-31)
### Bug Fixes
* remove shrinkwrap.yaml from repo ([baf6ca5](https://github.com/yanick/json-schema-shorthand/commit/baf6ca5c27f9f7723afa48796da0627160579839))
## 0.3.1 (https://github.com/yanick/json-schema-shorthand/compare/v0.3.0...v0.3.1) (2020-01-31)
### Bug Fixes
* bump dependency versions to latest (685e13e (https://github.com/yanick/json-schema-shorthand/commit/685e13eba976fda5ba956a105ac2fb039e232860))
## v0.3.0 2018-02-14
## Improvements
* New shortcut: '$foo' expands to be `$ref: foo`.
* New 'range' shortcut.
* New shortcut functions for types `object`, `array`, `number`,
`integer`, and `string`.
* Add `add_definition` helper function.
### Bug Fixes
* `shorthand()` deals gracefully with `null` argument.
## 0.2.0 2017-01-03
* Properties can be made required via a '!' suffix.
* Drop Mocha and Chai for TAP for testing.
## 0.1.0 2016-08-01
* Recurse down 'allOf', 'oneOf', 'anyOf', 'not'.
* Add 'install' and 'synopsis' sections in doc.
## 0.0.1 2016-07-31
* Initial release

128
CODE_OF_CONDUCT.md Normal file
View File

@ -0,0 +1,128 @@
# Contributor Covenant Code of Conduct
## Our Pledge
We as members, contributors, and leaders pledge to make participation in our
community a harassment-free experience for everyone, regardless of age, body
size, visible or invisible disability, ethnicity, sex characteristics, gender
identity and expression, level of experience, education, socio-economic status,
nationality, personal appearance, race, religion, or sexual identity
and orientation.
We pledge to act and interact in ways that contribute to an open, welcoming,
diverse, inclusive, and healthy community.
## Our Standards
Examples of behavior that contributes to a positive environment for our
community include:
* Demonstrating empathy and kindness toward other people
* Being respectful of differing opinions, viewpoints, and experiences
* Giving and gracefully accepting constructive feedback
* Accepting responsibility and apologizing to those affected by our mistakes,
and learning from the experience
* Focusing on what is best not just for us as individuals, but for the
overall community
Examples of unacceptable behavior include:
* The use of sexualized language or imagery, and sexual attention or
advances of any kind
* Trolling, insulting or derogatory comments, and personal or political attacks
* Public or private harassment
* Publishing others' private information, such as a physical or email
address, without their explicit permission
* Other conduct which could reasonably be considered inappropriate in a
professional setting
## Enforcement Responsibilities
Community leaders are responsible for clarifying and enforcing our standards of
acceptable behavior and will take appropriate and fair corrective action in
response to any behavior that they deem inappropriate, threatening, offensive,
or harmful.
Community leaders have the right and responsibility to remove, edit, or reject
comments, commits, code, wiki edits, issues, and other contributions that are
not aligned to this Code of Conduct, and will communicate reasons for moderation
decisions when appropriate.
## Scope
This Code of Conduct applies within all community spaces, and also applies when
an individual is officially representing the community in public spaces.
Examples of representing our community include using an official e-mail address,
posting via an official social media account, or acting as an appointed
representative at an online or offline event.
## Enforcement
Instances of abusive, harassing, or otherwise unacceptable behavior may be
reported to the community leaders responsible for enforcement at
yanick@babyl.ca.
All complaints will be reviewed and investigated promptly and fairly.
All community leaders are obligated to respect the privacy and security of the
reporter of any incident.
## Enforcement Guidelines
Community leaders will follow these Community Impact Guidelines in determining
the consequences for any action they deem in violation of this Code of Conduct:
### 1. Correction
**Community Impact**: Use of inappropriate language or other behavior deemed
unprofessional or unwelcome in the community.
**Consequence**: A private, written warning from community leaders, providing
clarity around the nature of the violation and an explanation of why the
behavior was inappropriate. A public apology may be requested.
### 2. Warning
**Community Impact**: A violation through a single incident or series
of actions.
**Consequence**: A warning with consequences for continued behavior. No
interaction with the people involved, including unsolicited interaction with
those enforcing the Code of Conduct, for a specified period of time. This
includes avoiding interactions in community spaces as well as external channels
like social media. Violating these terms may lead to a temporary or
permanent ban.
### 3. Temporary Ban
**Community Impact**: A serious violation of community standards, including
sustained inappropriate behavior.
**Consequence**: A temporary ban from any sort of interaction or public
communication with the community for a specified period of time. No public or
private interaction with the people involved, including unsolicited interaction
with those enforcing the Code of Conduct, is allowed during this period.
Violating these terms may lead to a permanent ban.
### 4. Permanent Ban
**Community Impact**: Demonstrating a pattern of violation of community
standards, including sustained inappropriate behavior, harassment of an
individual, or aggression toward or disparagement of classes of individuals.
**Consequence**: A permanent ban from any sort of public interaction within
the community.
## Attribution
This Code of Conduct is adapted from the [Contributor Covenant][homepage],
version 2.0, available at
https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
Community Impact Guidelines were inspired by [Mozilla's code of conduct
enforcement ladder](https://github.com/mozilla/diversity).
[homepage]: https://www.contributor-covenant.org
For answers to common questions about this code of conduct, see the FAQ at
https://www.contributor-covenant.org/faq. Translations are available at
https://www.contributor-covenant.org/translations.

15
Changes
View File

@ -1,5 +1,14 @@
Revision history for App-Changeman
# Changelog for [App::Changelord][homepage]
{{$NEXT}}
[homepage]: https://git.babyl.ca/yanick/App-Changelord
## v0.0.1, 2022-06-25
* Initial release
### Statistics
* code churn: 27 files changed, 1281 insertions(+)
- First version, unleashed on an unsuspecting world.

39
MANIFEST Normal file
View File

@ -0,0 +1,39 @@
AUTHOR_PLEDGE
CHANGELOG.yml
CODE_OF_CONDUCT.md
CONTRIBUTORS
Changes
INSTALL
LICENSE
MANIFEST
META.json
META.yml
Makefile.PL
README.mkdn
SIGNATURE
bin/changelord
cpanfile
doap.xml
lib/App/Changelord.pm
lib/App/Changelord/Command/Add.pm
lib/App/Changelord/Command/Bump.pm
lib/App/Changelord/Command/GitGather.pm
lib/App/Changelord/Command/Init.pm
lib/App/Changelord/Command/Print.pm
lib/App/Changelord/Command/Schema.pm
lib/App/Changelord/Command/Validate.pm
lib/App/Changelord/Command/Version.pm
lib/App/Changelord/Command/changelog-schema.yml
lib/App/Changelord/Role/ChangeTypes.pm
lib/App/Changelord/Role/Changelog.pm
lib/App/Changelord/Role/Render.pm
lib/App/Changelord/Role/Stats.pm
lib/App/Changelord/Role/Versions.pm
t/00-compile.t
t/00-report-prereqs.dd
t/00-report-prereqs.t
t/basic.t
t/render.t
t/stats.t
t/versions.t
xt/release/unused-vars.t

View File

@ -1,4 +1,6 @@
#!/usr/bin/env perl
# PODNAME: changelord
# ABSTRACT: cli tool for App::Changelord
use App::Changelord;

41
cpanfile Normal file
View File

@ -0,0 +1,41 @@
# This file is generated by Dist::Zilla::Plugin::CPANFile v6.025
# Do not edit this file directly. To change prereqs, edit the `dist.ini` file.
requires "CLI::Osprey" => "0";
requires "Git::Repository" => "0";
requires "JSON" => "0";
requires "JSON::Schema::Modern" => "0";
requires "List::AllUtils" => "0";
requires "Moo" => "0";
requires "Moo::Role" => "0";
requires "Path::Tiny" => "0";
requires "PerlX::Maybe" => "0";
requires "Version::Dotted::Semantic" => "0";
requires "YAML" => "0";
requires "YAML::XS" => "0";
requires "feature" => "0";
requires "perl" => "v5.36.0";
requires "warnings" => "0";
on 'test' => sub {
requires "ExtUtils::MakeMaker" => "0";
requires "File::Spec" => "0";
requires "IO::Handle" => "0";
requires "IPC::Open3" => "0";
requires "Test2::V0" => "0";
requires "Test::More" => "0";
requires "strict" => "0";
};
on 'test' => sub {
recommends "CPAN::Meta" => "2.120900";
};
on 'configure' => sub {
requires "ExtUtils::MakeMaker" => "0";
};
on 'develop' => sub {
requires "Test::More" => "0.96";
requires "Test::Vars" => "0";
};

View File

@ -1,7 +1,20 @@
name = App-Changeman
author = Yanick Champoux <yanick@babyl.dyndns.org>
name = App-Changelord
author = Yanick Champoux <yanick@babyl.ca>
license = Perl_5
copyright_holder = Yanick Champoux
copyright_year = 2022
[@YANICK]
version = v0.0.1
homepage=https://git.babyl.ca/yanick/App-Changelord
[@Filter]
-bundle=@YANICK
-remove=GithubMeta
-remove=ReadmeFromPod
-remove=Test::PAUSE::Permissions
-remove=PreviousVersion::Changelog
-remove=NextVersion::Semantic
-remove=ChangeStats::Git
-remove=CheckChangesHasContent
-remove=RunExtraTests
dev_branch=main

View File

@ -1,7 +1,5 @@
package App::Changelord;
# SYNOPSIS: cli-based changelog manager
# version next latest
# ABSTRACT: cli-based changelog manager
use 5.36.0;