release's Introduction

release

Installation

$ deno install -A -f --unstable https://deno.land/x/[email protected]/release.ts

Usage

usage: release [options] <type> [...]

example: release major

[options]:
  -h --help     Show this message
  --dry         Prevent changes to git

[type]:
  release type:
    * patch             eg: 1.2.3 -> 1.2.4
    * minor             eg: 1.2.3 -> 1.3.0
    * major             eg: 1.2.3 -> 2.0.0
    * prepatch <name>   eg: 1.2.3 -> 1.2.4-name
    * preminor <name>   eg: 1.2.3 -> 1.2.4-name
    * premajor <name>   eg: 1.2.3 -> 1.2.4-name

Maintainers

Filippo Rossi (@qu4k)

Other

Contribution

Pull request, issues and feedback are very welcome. Code style is formatted with deno fmt and commit messages are done following Conventional Commits spec.

Licence

release's People

Contributors

Stargazers

Watchers

Forkers

sylc

release's Issues

Created release are in 'draft'

Could a config file expose the draft property so that a user can decide if the release should be generated as non-draft or not?
I'm happy to have a go at a PR.

thanks

version number and readme update on release

When a release is made, I have a need to

Generate a file with the version number of the tag being generated. (this allows to ensure that my deno script always report the correct version number)
Update the readme links to display current version.

I have created a fork with a raw prototype to suit my need (see sylc#1). i.e I created 2 new plugins. one for adding the file with the version number and one for updating the readme.

Would you be interested in getting this supported in the release repo by either:

adding these plugins to the repo with probably a config file so the user can enable/disable/tweak the behaviour of these plugins
Or supporting calling external plugins.

I'm happy to help implemented the feature. cheers