@swell/swell-ui 0.1.0 → 0.1.1

package/CHANGELOG.md

@@ -4,6 +4,12 @@ All notable changes to this project are documented in this file. The format foll
 
 ## [Unreleased]
 
+## [0.1.1] - 2026-11-12
+
+### Fixed
+
+- The package carries its build: `dist`, with the elements, the React wrappers and the types, and `custom-elements.json`. 0.1.0 was published without them.
+
 ## [0.1.0] - 2026-11-12
 
 ### Added

package/README.md

@@ -156,7 +156,7 @@ A release is published from `main`:
 1. In [CHANGELOG.md](CHANGELOG.md), move the entries under `[Unreleased]` to a heading for the new version with its date, and commit.
 2. Bump the version by the rules in [ARCHITECTURE.md → Versioning](ARCHITECTURE.md#versioning): `npm version patch`, `minor` or `major`, which commits and tags it.
 3. Run the full check and pack the package: `npm run release`.
-4. Publish the packed file: `npm publish swell-swell-ui-<version>.tgz`. The package is public on npm (`publishConfig.access`), so apps and storefronts install it without a token.
+4. Publish the packed file: `npm publish swell-swell-ui-<version>.tgz`. A plain `npm publish` from the folder runs the full check first (`prepublishOnly`), which builds the package. The package is public on npm (`publishConfig.access`), so apps and storefronts install it without a token.
 5. Push the commit and the tag: `git push --follow-tags`.
 
 The Swell platform serves the kit at `/.swell/ui/v<major>/` from the version of `@swell/swell-ui` that swell-admin depends on, so a release reaches apps and storefronts once swell-admin takes the new version and deploys.