Automate NPM releases on GitHub using changesets 🦋

• unpkg

  42 2,876 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": [] }

• semver

  720 7,026 0.6

  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.

• InfluxDB

  www.influxdata.com sponsored

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

• changesets

  30 8,033 5.4 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.

• changeset-bot

  2 - -

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

Suggest a related project