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

@terradatum/semver-action

v1.1.0

Published

## Workflow

Downloads

2

Readme

SemVer Action

Workflow

The semver-action GitHub Action reads and modifies semantic versions in-memory. This action does not modify files or git history. That is left to the user.

Set the various versions based on the initial version string, and based on the following:

  1. SNAPSHOTS: a. Version: the version found in the pom.xml. E.g. 1.0.0-SNAPSHOT b. Next Version: the version to use when building. This is the version without the '-SNAPSHOT' suffix. E.g. 1.0.0 c. Snapshot Version: the next SNAPSHOT version - should be checked-in to git. E.g. 1.0.1-SNAPSHOT or 1.1.0-SNAPSHOT
  2. All others a. Version: the version found in the package manager file (npm or maven). E.g. 1.0.0 b. Next Version: the version to use when building. E.g. 1.0.1

Usage

- uses: terradatum/semver-action@main
  with:
    # The current version passed as an input to the action.
    version: ''

    # The type of package manager. One of maven, npm. Used to collect the current
    # version from the package manager file associated with that package manager (e.g.
    # npm => package.json, maven = pom.xml, etc.).
    package-manager-type: ''

    # The type of version increment (e.g. patch, minor, major, prerelease, etc.). This
    # action is READ-ONLY for the filesystem.
    bump: ''
outputs:
  # Whether the version is a SNAPSHOT
  snapshot-release: ''

  # The current version.
  version: ''

  # The current MAJOR version.
  major: ''

  # The current MINOR version.
  minor: ''

  # The current PATCH version.
  patch: ''

  # The current PRE-RELEASE version.
  pre-release: ''

  # The version used to next.
  next-version: ''

  # The next MAJOR version.
  next-major: ''

  # The next MINOR version.
  next-minor: ''

  # The next PATCH version.
  next-patch: ''

  # The current PRE-RELEASE version.
  next-pre-release: ''

  # the next SNAPSHOT version to set after the build.
  next-snapshot-version: ''

  # The next SNAPSHOT MAJOR version.
  next-snapshot-major: ''

  # The next SNAPSHOT MINOR version.
  next-snapshot-minor: ''

  # The next SNAPSHOT PATCH version.
  next-snapshot-patch: ''

Basic Usage

Using an input version:

steps:
  - name: Checkout
    uses: actions/checkout@v2
  - uses: @terradatum/semver-action
    with:
      version: v1.0.0

Advanced Usage

Using an npm Package Manager Type and bump based on auto version:

steps:
  - name: Checkout
    uses: actions/checkout@v2
  - name: Get bump
    id: get_bump
    run: echo "::set-output name=bump::$(auto version)"
  - uses: @terradatum/semver-action
    with:
      package-manager-type: npm
      bump: ${{ steps.get_bump.outputs.bump }}

Changelog

See CHANGELOG.

License

This project released under the MIT License.