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

ghactions-next-version

v0.2.0

Published

Format, bump, and update a version of Node.js and Python packages

Downloads

10

Readme

Next Version

Format, bump, and update a version of Node.js and Python packages action.

Usage

Pre-requisites

Create a workflow .yml file in your repositories .github/workflows directory. Check Examples below. For more information, reference the GitHub Help Documentation for Creating a workflow file.

Inputs

| Name | Default | Description | | - | - | - | | path | "" | Path to file that contains current version, e.g package.json, pyproject.toml, setup.cfg, version.txt | | version | "0.0.0" | Current version to bump, use path isntead if possible | | type | "semver" | Version type: semver or pep440 | | release | "stable" | Release type: stable rc, alpha or beta | | result | "patch" | Version to set as result: major, minor, patch, micro, prerelease, build, postrelease, or explicit version | | update | "" | Newline-separated paths to version files to update | | encoding | "utf-8" | Encoding for files provided in path |

Outputs

| Name | SemVer Example | PEP440 Example | Description | | - | - | - | - | | major | "2.0.0" | "2.0.0" | Next major version | | minor | "1.3.0" | "1.3.0" | Next minor version | | patch | "1.2.3" | "1.2.3" | Next patch/micro version | | micro | "1.2.3" | "1.2.3" | Next patch/micro version | | prerelease | "1.2.3-rc.2" | "1.2.3rc2" | Next prerelease version | | build | "1.2.3-rc.1+1" | "1.2.3rc1+1" | Next build/local version | | postrelease | "1.2.4" | "1.2.3.post1" | Next postrelease version (pep440 only) | | result | "1.2.3" | "1.2.3" | Next version specified in output | | is-prerelease | false | false | Whether result version is a prerelease | | input | "1.2.3-rc.1" | "1.2.3rc1" | Normalized input version | | raw-input | "v1.2.3-rc.1" | "v1.2.3rc1" | Raw input string |

Examples

Easy CI/CD for JavaScript/TypeScript and Python projects

https://github.com/vemel/github_actions_js/

Other examples

Contributing

I would love for you to contribute to actions/nextversion, pull requests are welcome! Please see the CONTRIBUTING.md for more information.

License

The scripts and documentation in this project are released under the MIT License