npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@progresso/gitlab-release-generator

v1.1.4

Published

Creates a json document for the gitlab release api from a changelog document.

Downloads

12

Readme

gitlab-version-generator

Creates a json document for the gitlab release api from a changelog document.

Introduction

To create a new release in gitlab, it is necessary to use the release api. As seen in the documentation, you have to submit a body in json like

{
   "name":"New release",
   "tag_name":"v0.3",
   "description":"Super nice release",
   "assets":{
      "links":[
         {
            "name":"hoge",
            "url":"https://google.com"
         }
      ]
   }
}

To support our automated build process and include richer descriptions this tool was developed.

Installation

Just install via npm npm install -f @progresso/gitlab-release-generator

Usage

usage: create-release [-h] [-v] -n NAME -t TAG [-c CHANGELOG] [-a ASSETS]
                      [-f FILE]


Gitlab release generator

Optional arguments:
  -h, --help            Show this help message and exit.
  -v, --version         Show program's version number and exit.
  -n NAME, --name NAME  The name of the version
  -t TAG, --tag TAG     The name of the tag to create a release for
  -c CHANGELOG, --changelog CHANGELOG
                        The path of the changelog file. The file has to be in
                        "Keep a Changelog"-Format. See https://keepachangelog.
                        com
  -a ASSETS, --asset ASSETS
                        Assets to be added to the release. Can occur multiple
                        times and should be in format: "NAME::URL".
  -f FILE, --file FILE  The target json file

Example

create-release -n 1.1.1 -t 1.1.1 -c \path\to\changelog -f \path\to\release.json -a "npm::https://www.npmjs.com/package/@progresso/gitlab-release-generator/v/1.1.1"

Is going to create \path\to\release.json

{
   "name":"1.1.1",
   "tag_name":"1.1.1",
   "description":"### Fixed\r\n- Something has been fixed",
   "assets":{
      "links":[
         {
            "npm":"https://www.npmjs.com/package/@progresso/gitlab-release-generator/v/1.1.1"
         }
      ]
   }
}

if your \path\to\changelog is in KeepAChangelog Format (1.0.0). This tool uses regular expression to find the version specified in the tag within the changelog file. This may break easily in case the format is changed/invalid.

You can then use this json to create a version in gitlab:

curl --header 'Content-Type: application/json' --header "PRIVATE-TOKEN: gDybLx3yrUK_HLp3qPjS" \
     -d \path\to\release.json
     --request POST http://localhost:3000/api/v4/projects/24/releases