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

@pie-api/semantic-release-jira-releases

v0.12.0

Published

[**semantic-release**](https://github.com/semantic-release/semantic-release) plugin to publish a jira release.

Downloads

29

Readme

semantic-release-jira-releases

semantic-release plugin to publish a jira release.

Travis

npm latest version

| Step | Description | |--------------------|----------------------------------------------------------------------------| | verifyConditions | Validate the config options and checks for JIRA_EMAIL and JIRA_TOKEN in the environment | | sucess | Find all tickets from commits and add them to a new release on JIRA |

Install

$ npm install --save-dev semantic-release-jira-releases
$ yarn add --dev semantic-release-jira-releases

Configuration

The plugin should be added to your config

{
  "plugins": [
    "@semantic-release/commit-analyzer",
    "@semantic-release/release-notes-generator",
    "@semantic-release/git",
    ["semantic-release-jira-releases", {
      "projectId": "1",
      "releaseNameTemplate": "Test v${version}",
      "jiraHost": "uphabit.atlassian.net",
      "ticketPrefixes": [ "TEST", "UH"],
      "ticketRegex": "[a-zA-Z]{3,5}-\\d{3,5}"
    }]
  ]
}

Please note that `ticketRegex` cannot be used together with `ticketPrefixes`.
interface Config {
  
  /// A domain of a jira instance ie: `uphabit.atlasian.net`
  jiraHost: string;

  // A list of prefixes to match when looking for tickets in commits. Cannot be used together with ticketRegex.
  // ie. ['TEST'] would match `TEST-123` and `TEST-456`
  ticketPrefixes?: string[];

  // A unescaped regex to match tickets in commits (without slashes). Cannot be used together with ticketPrefixes.
  // ie. [a-zA-Z]{4}-\d{3,5} would match any ticket with 3 letters a dash and 3 to 5 numbers, such as `TEST-456`, `TEST-5643` and `TEST-56432`
  ticketRegex?: string;
  
  // The id for the project releases will be created in
  projectId: number;
  
  // A lodash template with a single `version` variable
  // defaults to `v${version}` which results in a version that is named like `v1.0.0`
  // ex: `Semantic Release v${version}` results in `Semantic Release v1.0.0`
  releaseNameTemplate?: string;

  // The number of maximum parallel network calls, default 10
  networkConcurrency?: number;

  // indicates if a new release created in jira should be set as released
  released?: boolean;

  // include the release date when creating a release in jira
  releaseDate?: boolean;
}