@npmcli/ci-detect - npm Package Compare versions

Comparing version 3.0.1 to 3.0.2

lib/index.js

		@@ -14,3 +14,3 @@ module.exports = () =>
		: process.env.DSARI ? 'dsari'
		: process.env.GITHUB_ACTION ? 'github-actions'
		: process.env.GITHUB_ACTIONS ? 'github-actions'
		: process.env.TDDIUM ? 'tddium'
		@@ -17,0 +17,0 @@ : process.env.SCREWDRIVER ? 'screwdriver'

package.json

		{
		"name": "@npmcli/ci-detect",
		"version": "3.0.1",
		"version": "3.0.2",
		"description": "Detect what kind of CI environment the program is in",
		@@ -26,3 +26,3 @@ "author": "GitHub Inc.",
		"@npmcli/eslint-config": "^4.0.0",
		"@npmcli/template-oss": "4.6.2",
		"@npmcli/template-oss": "4.8.0",
		"tap": "^16.0.1"
		@@ -43,4 +43,4 @@ },
		"//@npmcli/template-oss": "This file is partially managed by @npmcli/template-oss. Edits may be overwritten.",
		"version": "4.6.2"
		"version": "4.8.0"
		}
		}

README.md

		@@ -5,5 +5,2 @@ # @npmcli/ci-detect

		[![Build Status](https://travis-ci.com/npm/ci-detect.svg?branch=master)](https://travis-ci.com/npm/ci-detect)
		[![Coverage Status](https://coveralls.io/repos/github/npm/ci-detect/badge.svg?branch=master)](https://coveralls.io/github/npm/ci-detect?branch=master)

		## USAGE
		@@ -31,5 +28,5 @@
		* `'buddy'` Buddy
		* `'builder'` Google Cloud Builder - This one is a bit weird. It doesn't
		really set anything that can be reliably detected except
		`BUILDER_OUTPUT`, so it can get false positives pretty easily.
		* `'builder'` Google Cloud Builder - This one is a bit weird. It
		doesn't really set anything that can be reliably detected except
		`BUILDER_OUTPUT`, so it can get false positives pretty easily.
		* `'buildkite'` Buildkite
		@@ -40,3 +37,3 @@ * `'circleci'` Circle-CI
		* `'custom'` anything else that sets `CI` environment variable to either
		`'1'` or `'true'`.
		`'1'` or `'true'`.
		* `'drone'` Drone
		@@ -68,5 +65,5 @@ * `'dsari'` dsari CI
		* `'travis-ci'` Travis-CI - A few other CI systems set `TRAVIS=1` in the
		environment, because devs use that to indicate "test mode", so this one
		can get some false positives, and is tested later in the process to
		minimize this effect.
		environment, because devs use that to indicate "test mode", so this
		one can get some false positives, and is tested later in the process
		to minimize this effect.
		* `'vercel'` Vercel
		@@ -81,13 +78,13 @@ * `'vercel-bitbucket'` Vercel Bitbucket

		Note that since any program can set or unset whatever environment variables
		they want, this is not 100% reliable.
		Since any program can set or unset whatever environment variables they
		want, this is not 100% reliable.

		Also, note that if your program does different behavior in
		CI/test/deployment than other places, then there's a good chance that
		you're doing something wrong!
		Also, if your program does different behavior in CI/test/deployment than
		other places, then there's a good chance that you're doing something
		wrong!

		But, for little niceties like setting colors or other output parameters, or
		logging and that sort of non-essential thing, this module provides a way to
		tweak without checking a bunch of things in a bunch of places. Mostly,
		it's a single place to keep a note of what CI system sets which environment
		variable.
		But, for little niceties like setting colors or other output parameters,
		or logging and that sort of non-essential thing, this module provides a
		way to tweak without checking a bunch of things in a bunch of places.
		Mostly, it's a single place to keep a note of what CI system sets which
		environment variable.

@npmcli/ci-detect - npm Package Compare versions

New alerts

Fixed alerts

Worsened metrics