[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-70691":3},{"id":4,"name":5,"fullName":6,"owner":5,"repo":5,"description":7,"homepage":8,"htmlUrl":9,"language":10,"languages":9,"totalLinesOfCode":9,"stars":11,"forks":12,"watchers":13,"openIssues":14,"contributorsCount":15,"subscribersCount":15,"size":15,"stars1d":16,"stars7d":17,"stars30d":18,"stars90d":15,"forks30d":15,"starsTrendScore":19,"compositeScore":20,"rankGlobal":9,"rankLanguage":9,"license":21,"archived":22,"fork":22,"defaultBranch":23,"hasWiki":22,"hasPages":22,"topics":24,"createdAt":9,"pushedAt":9,"updatedAt":25,"readmeContent":26,"aiSummary":27,"trendingCount":15,"starSnapshotCount":15,"syncStatus":28,"lastSyncTime":29,"discoverSource":30},70691,"changesets","changesets\u002Fchangesets","🦋 A tool to manage versioning and changelogs with a focus on monorepos","",null,"TypeScript",11967,788,41,306,0,26,53,149,78,43.69,"MIT License",false,"main",[],"2026-06-12 02:02:42","\u003Cp align=\"center\">\n  \u003Cpicture>\n    \u003Csource media=\"(prefers-color-scheme: dark)\" srcset=\".\u002Fassets\u002Fimages\u002Fchangesets-banner-dark.png\">\n    \u003Cimg alt=\"Changesets banner\" src=\".\u002Fassets\u002Fimages\u002Fchangesets-banner-light.png\">\n  \u003C\u002Fpicture>\n\u003C\u002Fp>\n\n\u003Cp align=\"center\">\n  A tool to manage versioning and changelogs \u003Cbr\u002F>\n  with a focus on multi-package repositories\n\u003C\u002Fp>\n\u003Cbr\u002F>\n\n[![npm package](https:\u002F\u002Fimg.shields.io\u002Fnpm\u002Fv\u002F@changesets\u002Fcli?label=%40changesets%2Fcli)](https:\u002F\u002Fnpmjs.com\u002Fpackage\u002F@changesets\u002Fcli)\n[![View changelog](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FExplore%20Changelog-brightgreen)](.\u002Fpackages\u002Fcli\u002FCHANGELOG.md)\n\nThe `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.\n\nChangesets 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.\n\n## How do we do that?\n\nA `changeset` is an intent to release a set of packages at particular [semver bump types](https:\u002F\u002Fsemver.org\u002F) with a summary of the changes made.\n\nThe **@changesets\u002Fcli** 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.\n\n## How do I get started?\n\nIf you just want to jump in to using changesets, the [Intro to using changesets](.\u002Fdocs\u002Fintro-to-using-changesets.md) and [@changesets\u002Fcli](.\u002Fpackages\u002Fcli\u002FREADME.md) docs are where you should head.\n\nIf you want a detailed explanation of the concepts behind changesets, or to understand how you would build on top\nof changesets, check out our [detailed-explanation](.\u002Fdocs\u002Fdetailed-explanation.md).\n\nWe also have a [dictionary](.\u002Fdocs\u002Fdictionary.md).\n\n## Integrating with CI\n\nWhile changesets can be an entirely manual process, we recommend integrating it with how your CI works.\n\nTo check that PRs contain a changeset, we recommend using [the changeset bot](https:\u002F\u002Fgithub.com\u002Fapps\u002Fchangeset-bot), or if you want to fail builds on a changesets failure, run `yarn changeset status` in CI.\n\nTo make releasing easier, you can use [this changesets github action](https:\u002F\u002Fgithub.com\u002Fchangesets\u002Faction) to automate creating versioning pull requests, and optionally publishing packages.\n\n## Documentation\n\n- [Intro to using changesets](.\u002Fdocs\u002Fintro-to-using-changesets.md)\n- [Detailed explanation](.\u002Fdocs\u002Fdetailed-explanation.md)\n- [Common questions](.\u002Fdocs\u002Fcommon-questions.md)\n- [Adding a changeset](.\u002Fdocs\u002Fadding-a-changeset.md)\n- [Automating changesets](.\u002Fdocs\u002Fautomating-changesets.md)\n- [Checking for changesets](.\u002Fdocs\u002Fchecking-for-changesets.md)\n- [Command line options](.\u002Fdocs\u002Fcommand-line-options.md)\n- [Config file options](.\u002Fdocs\u002Fconfig-file-options.md)\n- [Decisions](.\u002Fdocs\u002Fdecisions.md)\n- [Dictionary](.\u002Fdocs\u002Fdictionary.md)\n- [Fixed packages](.\u002Fdocs\u002Ffixed-packages.md)\n- [Linked packages](.\u002Fdocs\u002Flinked-packages.md)\n- [Modifying changelog format](.\u002Fdocs\u002Fmodifying-changelog-format.md)\n- [Prereleases](.\u002Fdocs\u002Fprereleases.md)\n- [Problems publishing in monorepos](.\u002Fdocs\u002Fproblems-publishing-in-monorepos.md)\n- [Snapshot releases](.\u002Fdocs\u002Fsnapshot-releases.md)\n- [Versioning applications and other non-npm packages](.\u002Fdocs\u002Fversioning-apps.md)\n- [Experimental Options](.\u002Fdocs\u002Fexperimental-options.md)\n\n## Cool Projects already using Changesets for versioning and changelogs\n\n- [atlaskit](https:\u002F\u002Fatlaskit.atlassian.com)\n- [emotion](https:\u002F\u002Femotion.sh\u002Fdocs\u002Fintroduction)\n- [keystone](https:\u002F\u002Fkeystonejs.com)\n- [react-select](https:\u002F\u002Freact-select.com\u002Fhome)\n- [XState](https:\u002F\u002Fxstate.js.org)\n- [pnpm](https:\u002F\u002Fpnpm.io)\n- [tinyhttp](https:\u002F\u002Fgithub.com\u002Ftalentlessguy\u002Ftinyhttp)\n- [Firebase Javascript SDK](https:\u002F\u002Fgithub.com\u002Ffirebase\u002Ffirebase-js-sdk)\n- [Formik](https:\u002F\u002Fgithub.com\u002Fjaredpalmer\u002Fformik)\n- [MobX](https:\u002F\u002Fgithub.com\u002Fmobxjs\u002Fmobx)\n- [Nhost](https:\u002F\u002Fgithub.com\u002Fnhost\u002Fnhost)\n- [verdaccio](https:\u002F\u002Fverdaccio.org)\n- [Chakra UI](https:\u002F\u002Fchakra-ui.com)\n- [Astro](https:\u002F\u002Fastro.build)\n- [Biome](https:\u002F\u002Fbiomejs.dev)\n- [SvelteKit](https:\u002F\u002Fkit.svelte.dev)\n- [Hydrogen](https:\u002F\u002Fhydrogen.shopify.dev)\n- [react-pdf](https:\u002F\u002Fgithub.com\u002Fdiegomura\u002Freact-pdf)\n- [GraphQL Code Generator](https:\u002F\u002Fgithub.com\u002Fdotansimha\u002Fgraphql-code-generator)\n- [GraphQL Yoga](https:\u002F\u002Fgithub.com\u002Fdotansimha\u002Fgraphql-yoga)\n- [GraphQL-Mesh](https:\u002F\u002Fgithub.com\u002FUrigo\u002Fgraphql-mesh)\n- [GraphiQL](https:\u002F\u002Fgithub.com\u002Fgraphql\u002Fgraphiql)\n- [wagmi](https:\u002F\u002Fgithub.com\u002Fwagmi-dev\u002Fwagmi)\n- [refine](https:\u002F\u002Fgithub.com\u002Fpankod\u002Frefine)\n- [Modern Web](https:\u002F\u002Fmodern-web.dev)\n- [Atomizer](https:\u002F\u002Fgithub.com\u002Facss-io\u002Fatomizer)\n- [Medusa](https:\u002F\u002Fgithub.com\u002Fmedusajs\u002Fmedusa)\n- [OpenZeppelin Contracts](https:\u002F\u002Fgithub.com\u002FOpenZeppelin\u002Fopenzeppelin-contracts)\n- [Block Protocol](https:\u002F\u002Fgithub.com\u002Fblockprotocol\u002Fblockprotocol)\n- [Remix](https:\u002F\u002Fremix.run\u002F)\n- [Clerk](https:\u002F\u002Fgithub.com\u002Fclerk\u002Fjavascript)\n- [Hey API](https:\u002F\u002Fgithub.com\u002Fhey-api\u002Fopenapi-ts)\n- [neverthrow](https:\u002F\u002Fgithub.com\u002Fsupermacro\u002Fneverthrow)\n- [Apollo Client](https:\u002F\u002Fgithub.com\u002Fapollographql\u002Fapollo-client)\n- [Adobe Spectrum CSS](https:\u002F\u002Fgithub.com\u002Fadobe\u002Fspectrum-css)\n- [Adobe Spectrum Web Components](https:\u002F\u002Fgithub.com\u002Fadobe\u002Fspectrum-web-components)\n- [React Email](https:\u002F\u002Freact.email)\n\n\u003C!-- NOTE: we currently only accept new entries with at least 1000 GitHub stars -->\n\n# Thanks\u002FInspiration\n\n- [bolt](https:\u002F\u002Fgithub.com\u002Fboltpkg\u002Fbolt) - 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.\n- [Atlassian](https:\u002F\u002Fwww.atlassian.com\u002F) - The original idea\u002Fsponsor of the changesets code, and where many of the ideas and processes were fermented. It was originally implemented by the team behind [atlaskit](https:\u002F\u002Fatlaskit.atlassian.com).\n- [lerna-semantic-release](https:\u002F\u002Fgithub.com\u002Fatlassian\u002Flerna-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.\n- [Thinkmill](https:\u002F\u002Fwww.thinkmill.com.au) - For sponsoring the focused open sourcing of this project, and the version two rearchitecture.\n","Changesets 是一个专注于多包仓库版本管理和变更日志的工具。它允许贡献者声明其更改应如何发布，并自动化更新包版本、变更日志以及基于提供的信息发布新版本。核心功能包括通过创建 changeset 文件来定义一组包的发布意图及其对应的语义化版本提升类型，同时处理多包仓库内的依赖关系。适合于需要维护多个相互依赖的包的项目，特别是在单体仓库中进行开发和发布的场景下使用，能够简化版本控制流程，确保依赖关系的一致性。",2,"2026-06-11 03:33:39","high_star"]