conventional-gitlab-releaser

Make a new GitLab release from git metadata.

Note You don't have to use the angular commit convention. For the best result of the tool to tokenize you commit and produce flexible output, it's recommended to use a commit convention.

Table of Contents

• Quick start
• Example output
  • Recommended workflow
• Why
  • Required GitLab CE/EE Edition
• Programmatic Usage
• API
  • conventionalGitlabReleaser(auth, [changelogOpts, [context, [gitRawCommitsOpts, [parserOpts, [writerOpts]]]]], callback)
    • auth
    • callback
      • callback(err, responses)
        • responses
    • changelogOpts
      • transform
      • releaseCount
    • gitRawCommitsOpts
      • from
      • to
    • writerOpts
      • includeDetails
      • headerPartial
• CLI
• Setup token for cli
• Related
• License
• Node Support Policy
• Contributing

Quick start

Set up a token first.

$ npm install -g conventional-gitlab-releaser
$ cd my-project
$ conventional-gitlab-releaser -p angular

The above generates a GitLab Release based on commits since the last semver tag that match the pattern of a "Feature", "Fix", "Performance Improvement" or "Breaking Changes".

If you first time use this tool and want to generate all previous releases, you could do

$ conventional-gitlab-releaser -p angular -r 0

This will not overwrite the releases you have already made. Read "Regenerate all the releases" section if you want to.

All available command line parameters can be listed using CLI : conventional-gitlab-releaser --help.

Hint: You can alias your command or add it to your package.json. EG: "gitlab-release": "conventional-gitlab-releaser -p angular -r 0".

Recommended workflow

1. Make changes
2. Commit those changes
3. Make sure GitLab CI turns green
4. Bump version in package.json
5. Commit package.json files
6. Tag
7. Push
8. conventionalGitlabReleaser

You have to have a tag on GitLab to make a release. hence gitRawCommitsOpts.to defaults to the latest semver tag.

Please use this gist to make a release or change it to your needs.

Why

• Based on conventional-changelog but GitLab releases are more elegant.
• Easy fully automate changelog generation. You could still add more points on top of it.
• Detecting prerelease based on semver, ignoring reverted commits, templating with handlebars.js and links to references, etc. Open an issue if you want more reasonable features.
• Intelligently setup defaults but yet fully configurable with presets of popular projects.
• Everything internally or externally is pluggable.
• A lot of tests and actively maintained.

Required GitLab CE/EE Edition

Version 9.0, or higher, of GitLab CE/EE is required for conventional-gitlab-releaser.

Core features used:

• GitLab release page
• API v4

This only applies to you if you're running your own instance of GitLab. GitLab.com is always the latest version of the GitLab application.

Programmatic Usage

$ npm install --save conventional-gitlab-releaser

var conventionalGitlabReleaser = require('conventional-gitlab-releaser');

var AUTH = {
  url: 'https://gitlab.com/api/v4',
  token: '0126af95c0e2d9b0a7c78738c4c00a860b04acc8'
};

conventionalGitlabReleaser(AUTH, {
  preset: 'angular'
}, callback);

API

conventionalGitlabReleaser(auth, [changelogOpts, [context, [gitRawCommitsOpts, [parserOpts, [writerOpts]]]]], callback)

auth

An authentication object containing the following:

• token - A GitLab Private Token with Developer permissions on the project to be released.
• url - The GitLab API (such as https://gitlab.com/api/v4).

For example:

{
  url: 'https://gitlab.com/api/v4',
  token: '0126af95c0e2d9b0a7c78738c4c00a860b04acc8'
}

callback

callback(err, responses)

responses

Type: array

An array of responses returned by gitlab.projects.repository.addTag calls.

Please check conventional-changelog for other arguments.

There are some changes:

changelogOpts

transform

Default: grab the whole tag for the version (including a leading v) and format date.

releaseCount

Default: 1

How many releases of changelog you want to generate. It counts from the latest semver tag. Useful when you forgot to generate any previous releases. Set to 0 to regenerate all.

gitRawCommitsOpts

from

Default: based on options.releaseCount.

to

Default: latest semver tag

writerOpts

includeDetails

It is always true.

headerPartial

Default: ''

Default header contains the version and date which are already in the release.

CLI

$ npm install --global conventional-gitlab-releaser
$ conventional-gitlab-releaser --help # for more details

You can supply your auth token by a flag -t or --token. You can also set up an environment variable CONVENTIONAL_GITLAB_RELEASER_TOKEN to avoid typing your token every time.

Note: If all results error, it will print the error messages to stderr and exit with code 1.

Setup token for cli

Get your token and set your environment variable CONVENTIONAL_GITLAB_RELEASER_TOKEN to the token you just retrieved. You can google How to set environment variable.

Related

• conventional-changelog - Generate a changelog from git metadata
• conventional-recommended-bump - Get a recommended version bump based on conventional commits
• conventional-commits-detector - Detect what commit message convention your repository is using

Debugging

To assist users of conventional-gitlab-releaser with debugging the behavior of this module we use the debug utility package to print information about the release process to the console. To enable debug message printing, the environment variable DEBUG, which is the variable used by the debug package, must be set to a value configured by the package containing the debug messages to be printed.

To print debug messages on a unix system set the environment variable DEBUG with the name of this package prior to executing conventional-gitlab-releaser:

DEBUG=conventional-gitlab-releaser conventional-gitlab-releaser

On the Windows command line you may do:

set DEBUG=conventional-gitlab-releaser
conventional-gitlab-releaser

Node Support Policy

We only support Long-Term Support versions of Node.

We specifically limit our support to LTS versions of Node, not because this package won't work on other versions, but because we have a limited amount of time, and supporting LTS offers the greatest return on that investment.

It's possible this package will work correctly on newer versions of Node. It may even be possible to use this package on older versions of Node, though that's more unlikely as we'll make every effort to take advantage of features available in the oldest LTS version we support.

As each Node LTS version reaches its end-of-life we will remove that version from the node engines property of our package's package.json file. Removing a Node version is considered a breaking change and will entail the publishing of a new major version of this package. We will not accept any requests to support an end-of-life version of Node. Any merge requests or issues supporting an end-of-life version of Node will be closed.

We will accept code that allows this package to run on newer, non-LTS, versions of Node. Furthermore, we will attempt to ensure our own changes work on the latest version of Node. To help in that commitment, our continuous integration setup runs against all LTS versions of Node in addition the most recent Node release; called current.

JavaScript package managers should allow you to install this package with any version of Node, with, at most, a warning if your version of Node does not fall within the range specified by our node engines property. If you encounter issues installing this package, please report the issue to your package manager.

Contributing

Please read our contributing guide to see how you may contribute to this project.

License

MIT © Steve Mao