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

azp-task-bump

v0.51.0

Published

Command line utility that increases the patch number of Azure Pipelines task manifests

Downloads

29

Readme

azp-task-bump

A command line utility for increasing by one the patch number in manifest files of Azure DevOps (formerly known as Visual Studio Team System/VSTS and Team Foundation Server/TFS) custom tasks.

Setup

Run the following from the command line:

npm i -g azp-task-bump

Usage

Run the following from the command line:

azp-task-bump c:\path-to-manifest\task.json

The one and only argument is optional. If omitted, the utility will look for task.json in the current working directory. If provided, it should be either a path to a task.json file (absolute or relative), or a path to a directory where task.json can be found. Wildcard paths are not supported.

On machines with case sensitive file systems, the file name task.json is expected to be in lowercase. The encoding of the manifest is expected to be UTF-8.

Once the utility locates the task manifest, it increases the value of the patch under the version object. Like the manifest compiler in the tfx utility, it treats the manifest JSON as case insensitive - the casing of version and patch can be anything. The patch is expected to be either a number, or a string with a decimal number in it. The datatype of patch is preserved.

The rest of the manifest file is not touched.

Prior art

There are also NPM packages azp-bump and gulp-azp-bump that do the same. The former insists on reformatting the JSON top to bottom, the latter requires gulp.