npmpackage.info

@changesets/assemble-release-plan

🦋 A way to manage your versioning and changelogs with a focus on monorepos

6.0.5

9,059

MIT

TypeScript

65,570,257 5.1

Installations

npm install @changesets/assemble-release-plan

Pull Requests

Open

108

Total

719

Closed

100

Merged

511

Issues

Open

345

Total

660

Closed

315

Releases

416

@changesets/release-utils@0.2.2

Published on 20 Nov 2024

@changesets/read@0.6.2

Published on 20 Nov 2024

@changesets/config@3.0.4

Published on 20 Nov 2024

@changesets/git@3.0.2

Published on 20 Nov 2024

@changesets/get-release-plan@4.0.5

Published on 20 Nov 2024

@changesets/cli@2.27.10

Published on 20 Nov 2024

View all 416 releases

Developer

changesets

Developer Guide

BETA

Module System

CommonJS, ESM

Min. Node Version

Typescript Support

Yes

Node Version

20.18.0

NPM Version

10.8.2 Statistics

9,059 Stars

593 Commits

564 Forks

34 Watching

41 Branches

140 Contributors

Updated on 28 Nov 2024

Languages

TypeScript (99.84%)

JavaScript (0.16%)

Total Downloads

Cumulative downloads

Total Downloads

65,570,257

Last day

-25%

187,042

Compared to previous day

Last week

4.1%

1,294,341

Compared to previous week

Last month

7.9%

5,251,155

Compared to previous month

Last year

119.7%

38,072,106

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

@changesets/errors @changesets/get-dependents-graph @changesets/should-skip-package @changesets/types @manypkg/get-packages semver

Dev Dependencies

@changesets/config

Versions

A tool to manage versioning and changelogs
with a focus on multi-package repositories

The changesets workflow is designed to help when people are making changes, all the way through to publishing. It lets contributors declare how their changes should be released, then we automate updating package versions, and changelogs, and publishing new versions of packages based on the provided information.

Changesets has a focus on solving these problems for multi-package repositories, and keeps packages that rely on each other within the multi-package repository up-to-date, as well as making it easy to make changes to groups of packages.

How do we do that?

A changeset is an intent to release a set of packages at particular semver bump types with a summary of the changes made.

The @changesets/cli package allows you to write changeset files as you make changes, then combine any number of changesets into a release, that flattens the bump-types into a single release per package, handles internal dependencies in a multi-package-repository, and updates changelogs, as well as release all updated packages from a mono-repository with one command.

How do I get started?

If you just want to jump in to using changesets, the Intro to using changesets and @changesets/cli docs are where you should head.

If you want a detailed explanation of the concepts behind changesets, or to understand how you would build on top of changesets, check out our detailed-explanation.

We also have a dictionary.

Integrating with CI

While changesets can be an entirely manual process, we recommend integrating it with how your CI works.

To check that PRs contain a changeset, we recommend using the changeset bot, or if you want to fail builds on a changesets failure, run yarn changeset status in CI.

To make releasing easier, you can use this changesets github action to automate creating versioning pull requests, and optionally publishing packages.

Documentation

Cool Projects already using Changesets for versioning and changelogs

Thanks/Inspiration

bolt - Brought us a strong concept of how packages in a mono-repo should be able to interconnect, and provided the initial infrastructure to get inter-package information.
Atlassian - The original idea/sponsor of the changesets code, and where many of the ideas and processes were fermented. It was originally implemented by the team behind atlaskit.
lerna-semantic-release - put down many of the initial patterns around updating packages within a multi-package-repository, and started us thinking about how to manage dependent packages.
Thinkmill - For sponsoring the focused open sourcing of this project, and the version two rearchitecture.

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

Score

5.1

/10

Last Scanned on 2024-11-25

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More