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-nuget

v1.1.1

Published

A semantic-release plugin for building and publishing NuGet packages.

Downloads

135

Readme

semantic-release-nuget

semantic-release-nuget is a semantic-release plugin for creating NuGet packages for .NET during the release process. It uses the following steps:

  • verifyConditions: Make sure settings are right and dotnet nuget --version works.
  • publish: Publish the packages to the repository.

Installing

Depending on your package manager, you'll need to run one of the commands.

npm install semantic-release-nuget --only=dev
yarn add semantic-release-nuget -D

Typically this is only used as a development dependency.

Usage

Add the plugin into the release.config.js file or in the appropriate section of package.json. An example release.config.js:

module.exports = {
    plugins: [
        "@semantic-release/commit-analyzer",
        "semantic-release-nuget",
    ],
};

The default is to run dotnet pack and dotnet push *.nukpkg.

Options can be given also:

module.exports = {
    plugins: [
        "@semantic-release/commit-analyzer",
        [
            "semantic-release-dotnet",
            {
                packArguments: ["--include-symbols", "--include-source"],
                pushFiles: "bin/*.nupkg",
            },
        ],
    ],
};

Options

There are only a few options for the command.

pushUrl?: string

  • Required
  • Default: NUGET_PUSH_URL environment variable

This is the URL to push up the NuGet package. If it isn't set in the release configuration, then it needs to be set in the NUGET_PUSH_URL environment variable. If in neither, then the verify conditions step will fail with a message.

apiKey?: string

  • Required
  • Default: NUGET_TOKEN environment variable

This is the API key used to push the NuGet package. If it isn't set, then NUGET_TOKEN will be used, otherwise an error will be thrown and the release will fail.

packArguments?: string[]

  • Default: []

Any additional arguments to the dotnet pack command. For example, one could use ["--include-symbols"] to include symbol packages.

pushFiles?: string[]

  • Default: [*.nupkg]

A list of files to include in the push. Any globs (* in the path) will be passed directly to dotnet nuget push without translation.

debug?: boolean

  • Default: false

Turns on debugging messages. This defaults to false to avoid information overload.