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

v1.0.0

Published

A semantic-release plugin for versioning .NET core projects.

Downloads

827

Readme

semantic-release-dotnet

semantic-release-dotnet is a semantic-release plugin for setting the varions on .NET projects, in specific .csproj and Directory.Build.props. It has the ability to create property files if missing or updating existing versions in files that do exist. If an existing file does not have a version property, then one will be added to either the first <PropertyGroup/> or by creating a new property group if one is not needed.

This only implements the prepare function for semantic-release and does not have functionality for uploading NuGet packages to repositories. This follows the Single Responsibility Principle, see semantic-release-nuget for that.

Installing

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

npm install semantic-release-dotnet --only=dev
yarn add semantic-release-dotnet -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-dotnet",
    ],
};

Options can be given also:

module.exports = {
    plugins: [
        "@semantic-release/commit-analyzer",
        [
            "semantic-release-dotnet",
            {
                paths: ["src/**.csproj"],
            }
        ],
    ],
};

Options

There are only a few options for the command.

paths?: string[]

  • Default: ["Directory.Build.props"]

This is an array of paths that are passed into glob to figure out what files need to be updated. If it is not provided, then a Directory.Build.props will be created and updated at the root level of the repository. If a path does not have magic values (so src/Project A/Project A.csproj instead of **/*.csproj), then the file will be created if missing.

indent?: string | number

  • Default: `" "``

This determines the indent of the files updated. If this is zero (0) or blank (""), then no indention will be done. All files that match the pattern will be rewritten and indented.

debug?: boolean

  • Default: false

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