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

semantic-release-sentry-releases

v2.0.1

Published

semantic-release plugin to create releases in sentry

Downloads

2,028

Readme

semantic-release-sentry-releases

npm Node.js CI downloads Libraries.io dependency status for latest release codecov semantic-release

semantic-release plugin to create releases in sentry

| Step | Description | | ------------------ | ------------------------------------------------------------------------------------------------------ | | verifyConditions | Verify the presence of the SENTRY_AUTH_TOKEN SENTRY_ORG and SENTRY_PROJECT environment variable. | | publish | Create release and deploy in sentry project. |

Install

npm i -D semantic-release-sentry-releases

Usage

The plugin can be configured in the semantic-release configuration file:

{
  "plugins": [
    "@semantic-release/changelog",
    "@semantic-release/npm",
    "@semantic-release/git",
    "@semantic-release/gitlab",
    "semantic-release-sentry-releases"
  ]
}

Configuration

Environment variables

| Variable | Description | | -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | SENTRY_AUTH_TOKEN | The authentication token with permission for releases created in profile or as internal integration in developer settings of organization. Need scopes release:admin. Optional org:read to get valid repository name from sentry integration | | SENTRY_ORG | The slug of the organization. | | SENTRY_PROJECT | The slug of the project. | | SENTRY_URL | The URL to use to connect to sentry. This defaults to https://sentry.io/. | | SENTRY_ENVIRONMENT | The environment to specify with this release. This defaults to production. | | DEPLOY_START | Sentry deploy start timestamp. Optional for deploy | | DEPLOY_END | Sentry deploy end timestamp. Optional for deploy |

Options

| Variable | Description | | --------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | project | The slug of the project. Optional. Required if not present in environment variables | | org | The slug of the organization. Optional. Required if not present in environment variables | | url | The URL to use to connect to sentry. Optional to set an on-premise instance | | repositoryUrl | A valid repository name for add link to commits of new release in sentry format. Optional. Ex: 'myorg / myapp'. Default repository property in package.json, or git origin url. Try recovery repository name from sentry api https://docs.sentry.io/api/organizations/list-an-organizations-repositories/ | | tagsUrl | A valid url for add link to new release. Optional. Ex: https://github.com/owner/repo/releases/tag/vx.y.z | | environment | Sentry environment. Optional for deploy. Default production | | deployName | Deploy name. Optional for deploy | | deployUrl | Deploy url. Optional for deploy | | sourcemaps | Directory with sourcemaps. Example dist. Optional for upload sourcemaps | | urlPrefix | URL prefix for sourcemaps. Example ~/dist. Optional for upload sourcemaps | | rewrite | Boolean to indicate rewrite sourcemaps. Default false. Optional for upload sourcemaps | | releasePrefix | String that is passed as prefix to the sentry release. Optional to fix the problem that releases are associated with the organization instead of the project (Read More). Ex: releasePrefix:"web1" would resolve only the sentry release to [email protected]. Important Notice: when you use this feature you also have to change the release name in your sentry client app. |

| pathToGitFolder | Path to .git folder, relative to the current working directory. Optional. Defaults to current working directory |

Examples

{
  "plugins": [
    "@semantic-release/changelog",
    "@semantic-release/npm",
    "@semantic-release/git",
    "@semantic-release/gitlab",
    [
      "semantic-release-sentry-releases",
      {
        "repositoryUrl": "myorg / myapp",
        "tagsUrl": "https://github.com/owner/repo/releases/tag/"
      }
    ]
  ]
}

Upload sourcemaps

{
  "plugins": [
    "@semantic-release/changelog",
    "@semantic-release/npm",
    "@semantic-release/git",
    "@semantic-release/gitlab",
    [
      "@semantic-release/exec",
      {
        "prepareCmd": "npm run build"
      }
    ],
    [
      "semantic-release-sentry-releases",
      {
        "repositoryUrl": "myorg / myapp",
        "tagsUrl": "https://github.com/owner/repo/releases/tag/",
        "sourcemaps": "dist",
        "urlPrefix": "~/dist"
      }
    ]
  ]
}
# .gitlab-ci.yml
release:
  image: node:alpine
  stage: release
  script:
    - npx semantic-release
  only:
    - master
# .travis.yml
language: node_js
cache:
  directories:
    - ~/.npm
node_js:
  - '18'
stages:
  - test
  - name: deploy
    if: branch = master
jobs:
  include:
    - stage: test
      script: npm t
    - stage: deploy
      script: npx semantic-release

License

MIT