release-it CLI
release-it combines version changes, Git tags and package publishing in a configurable release workflow with a preview mode.
- 9,083 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The CLI changes versions and Git state, runs hooks and can publish packages using supplied credentials.
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/release-itDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The CLI changes versions and Git state, runs hooks and can publish packages using supplied credentials.
This is third-party code. Review the repository files before installing.
What it does
release-it coordinates a project release: version bumping, commits, tags, pushes and GitHub or GitLab releases, with npm publishing available. Project configuration and hooks define build and test steps. Interactive runs request confirmation, while CI runs without prompts. An agent can prepare configuration and preview the plan before remote changes.
Who it is for. Package release owners coordinating versions, tags and publication through one repeatable workflow.
Good fit when
- A release needs package versions and Git tags synchronized.
- Build and test steps belong at specific release stages.
- The team wants to preview actions before publication.
- Manual and CI runs should use the same configuration.
Not a fit when
- Configuration and hooks cannot be reviewed before publication access is granted.
- You expect per-step prompts in CI.
- You require an approval system beyond CLI configuration.
Example request
Prepare release-it configuration and preview the next version without publishing or pushing.Limitations
Publishing requires appropriate Git and package-registry permissions that CLI installation does not grant. CI activates non-interactive mode automatically, so approval must come from the pipeline. Custom hooks execute shell commands and need review before previewing a release. Monorepos and nonstandard version files require extra configuration or plugins; verify the selected version against project policy.
How to disable. Remove release-it from scripts and CI, then uninstall the dependency. Published versions and tags remain and need separate decisions.
FAQ
What is the primary setup method?
`npm init release-it` installs the tool with minimal configuration; manual npm installation follows.
How do I preview actions?
Use `--dry-run` after reviewing hooks, then inspect the planned commands.
Where is the current version read?
From package.json, then the latest Git tag, otherwise 0.0.0. Verify before release.
Can I print the next version without releasing?
Yes. `--release-version` prints it when available without publication.
Where is configuration stored?
Usually `.release-it.json` or package.json’s release-it section. Agree on the configuration source.
Discussion
No questions or reviews yet.
Related
CLI toolsThe CLI takes an npm package through checks, versioning and publication for a user-reviewed release prepared with an agent.
multi-gitter runs one script across multiple Git repositories and creates pull requests for the resulting file changes.
A local gate in front of git push: the branch goes through review, tests, docs and lint in a separate worktree before it reaches the remote with a PR
GitHub Actions workflows run on your machine, and a failing step pauses so the agent can fix the file and retry it.
A Kubernetes development workflow combines image builds, deployment and source synchronization in a shared team configuration.
A pattern library and skill set for recurring agent loops: issue triage, dependency cleanup, PR babysitting
README in short
Plugins add versioning and changelog policies. Integrations support releases from different CI environments.