fix: Name the Pipenv source (#80)

This is now required.

fix!: Rename `CHANGES_PRERELEASE` to `CHANGES_INITIAL_DEVELOPMENT` (#75)

This is a preparatory change in advance of adding support for SemVer pre-release versioning. Since--under-the-hood--the `CHANGES_PRERELEASE` environment variable was checking to see if the major version is greater than 0, it has been renamed to 'initial development' correspond with SemVer's conventions (see https://semver.org/#spec-item-4). 'Unstable' was considered, but this seems less explicit and might not correctly represent all projects in the pre-1.0.0 state.

feat: Detect and log a descriptive error when running on shallow clon…

…es (#74)

fix: Remove useless test script (#69)

feat: Support running an executable during release (#68)

This introduces a way to call an executable during the release process (instead of running an inline script). This vastly simplifies the process of handling arguments as there's no need to delimit `"$@"` in the inline script (it's just implicit).

fix: Ensure the release command honours the legacy scope in the comma…

…nd (#62)

ci: Make the GitHub token available to the release script (#61)

fix: Relax the unbound constraint on the example GitHub release script (

#58)

This causes the array evaluation to fail if it's empty (when it's not a prerelease build) and is not as necessary as the script is fairly short and easy to audit.

fix: Honor the prerelease flag in the example GitHub release script (#57

)

fix: Correct the changes release script so it serves as a better exam…

…ple (#56)