---
name: hashintel-publishing-packages
description: "Conventions for publishing npm packages from this repository, including when a PR needs a changeset and how to write one. Use when adding or editing a changeset, versioning or releasing a package, or deciding whether a change to a publishable library needs a changelog entry."
license: "NOASSERTION"
metadata:
  decimalai-skill-id: "aaa3ee0b-03f0-41ae-b846-d3b66c4f008e"
  decimalai-version-id: "344d2f0d-3a9b-4849-865f-728e745865c1"
  decimalai-version: "1"
  decimalai-body-sha256: "a025efedb69e62b213e5b645c33789749144216c7bd41fc0dea3c13b388133b6"
  decimalai-name: "hashintel/publishing-packages"
  decimalai-format: "1"
  decimalai-invocation: "model"
  decimalai-category: "devops"
  decimalai-source: "https://app.decimal.ai/s/hashintel-publishing-packages@1/SKILL.md"
---
# Publishing Packages

npm-publishable packages in this repository are versioned and released with [changesets](https://github.com/changesets/changesets). The changeset configuration, including which packages are ignored, lives in [`.changeset/config.json`](../../../.changeset/config.json).

## Changesets

A PR that changes an npm-publishable package adds a changeset file under `.changeset/`. The changeset text becomes the package's published changelog entry, so write it for the package's consumers:

- Describe the change as a consumer of the package experiences it: behaviour changes, bug fixes, and interface changes. Leave out implementation details that do not affect consumers, and do not mention this repository or its internal systems.
- Every sentence must apply to each package the changeset lists. When a PR changes several packages in different ways, write a separate changeset for each package.
- Use at most one paragraph per changeset.

A package's own `AGENTS.md` can carry further conventions, such as the bump level it accepts; check it before writing the changeset.