Automate NPM releases on GitHub using changesets 🦋

1. unpkg

   1 58 3,025 0.0 JavaScript

   The CDN for everything on npm

   

   { "$schema": "https://unpkg.com/@changesets/[email protected]/schema.json", - "changelog": "@changesets/cli/changelog", + "changelog": ["@changesets/changelog-github", { + "repo": "your-org/your-repo" + }], "commit": false, "fixed": [], "linked": [], "access": "restricted", "baseBranch": "main", "updateInternalDependencies": "patch", "ignore": [] }

2. SaaSHub

   www.saashub.com featured

   SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

   

3. semver

   2 771 7,337 0.0

   Semantic Versioning Specification

   

   Changesets follow semantic versioning conventions. In a nutshell, this indicates that the version number follows the fixed format of major.minor.patch. A patch is a backwards-compatible bugfix, a minor is a feature that is backwards compatible, and a major is for any change that isn't backwards compatible.

4. changesets

   3 34 9,306 8.6 TypeScript

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

   

   Doing these tasks by hand can quickly become a hassle. If you're open to receiving contributions from others, it can be an even bigger headache. In this post we'll cover how to use changesets to automate all of these steps.

5. changeset-bot

   4 2 - -

   To remind contributors (and yourself!) to add this changeset to PRs, install the Changeset bot from the GitHub Marketplace.

Suggest a related project