# Releases

> shutdown-check releases: the changelog for 1.0.1 and 1.0.0, the milestones built into 1.0, and how to upgrade and check the version you have installed.

Source: https://shutdown.jscrate.dev/docs/releases
Last updated: 2026-09-23

shutdown-check 1.0.1 is the current documented release. It adds CommonJS
support and version flags to the first stable feature set released in 1.0.0.

Release notes are on GitHub: https://github.com/re-sohail/shutdown-check/releases

## Version 1.0.1

This maintenance release adds:

- a CommonJS entry point;
- matching TypeScript declarations for CommonJS;
- `shutdown-check --version`;
- the `-v` short flag;
- package metadata and documentation improvements.

CommonJS projects can now use:

```js
const { checkShutdown, defineConfig } = require("shutdown-check");
```

ESM usage remains unchanged:

```ts
import { checkShutdown, defineConfig } from "shutdown-check";
```

## Version 1.0.0

The first stable release includes:

- real process launch and cleanup;
- readiness polling;
- response-headers and probe start barriers;
- 1 to 20 active workload requests;
- `SIGTERM` delivery and optional repetition;
- readiness withdrawal and new-request rejection checks;
- response status and body verification;
- process deadline and exit-code verification;
- final port-closure verification;
- stable diagnostic codes;
- text, JSON, and JUnit output;
- CLI and typed Node.js API.

## Check the installed version

```bash
npx shutdown-check --version
```

Or inspect the local dependency:

```sh
npm list shutdown-check
```

Use the local project version in CI so the result matches development.

## Upgrade

```bash
npm install --save-dev shutdown-check@latest
```

After upgrading:

1. Run `shutdown-check --version`.
2. Run the existing shutdown test locally.
3. Review the text timeline and exit code.
4. Regenerate or inspect JUnit output if CI consumes it.
5. Commit the lockfile change.

Version 1.0.1 does not require a config migration from 1.0.0.

## Where does the changelog come from?

Release information is derived from the package's `CHANGELOG.md` and published
version metadata. The documentation keeps the supported CLI, API, and config
aligned with the installed package through build-time checks.

## Related

- [CLI reference](https://shutdown.jscrate.dev/docs/cli)
- [Node API](https://shutdown.jscrate.dev/docs/node-api)
- [Compatibility and limits](https://shutdown.jscrate.dev/docs/compatibility)
- [Quick start](https://shutdown.jscrate.dev/docs/quick-start)