@webtwizz/cloud 0.5.0 → 0.5.1

package/CHANGELOG.md

@@ -1,5 +1,11 @@
 # @webtwizz/cloud
 
+## 0.5.1
+
+### Patch Changes
+
+- d4f1dff: The npm page now covers only what sites need: the imports and the environment WebTwizz sets.
+
 ## 0.5.0
 
 ### Minor Changes

package/README.md

@@ -17,10 +17,12 @@ WebTwizz puts every setting in the site's environment, so each module works with
 | `@webtwizz/cloud/emails` | `handleSignInEmails()` for sites that send their own sign-in emails, `signInEmailCopy()` for the wording |
 | `@webtwizz/cloud/files` | `createFiles()` with `uploadUrl`, `publicUrl`, `privateUrl`, `remove` |
 
-`server`, `db`, `files` and `emails` are server-only. [AI_GUIDE.md](AI_GUIDE.md) has the full walkthrough and ships with each version.
+`server`, `db`, `files` and `emails` are server-only. [AI_GUIDE.md](AI_GUIDE.md), included in the package, has the full walkthrough.
 
 ## Environment
 
+WebTwizz sets these when a site uses WebTwizz Cloud.
+
 | Variable | Used by |
 | --- | --- |
 | `WEBTWIZZ_AUTH_URL`, `WEBTWIZZ_AUTH_SECRET` | `server` |
@@ -28,31 +30,3 @@ WebTwizz puts every setting in the site's environment, so each module works with
 | `WEBTWIZZ_STORAGE_ENDPOINT`, `WEBTWIZZ_STORAGE_REGION`, `WEBTWIZZ_STORAGE_KEY`, `WEBTWIZZ_STORAGE_SECRET` | `files` |
 | `WEBTWIZZ_STORAGE_READ_KEY`, `WEBTWIZZ_STORAGE_READ_SECRET` | `files` private links |
 | `WEBTWIZZ_FILES_URL`, `WEBTWIZZ_STORAGE_MAX_FILE_MB` | `files`, optional |
-
-## Development
-
-```sh
-npm ci
-npm test                 # unit tests
-npm run test:integration # real throwaway project, needs NEON_API_KEY
-npm run build
-```
-
-`test/fixture` is a small Next app built the way WebTwizz builds sites (the same Next and React versions, `bun install`, `next build --webpack`, the guide's code), which CI builds against the packed tarball.
-
-To try a change in the local WebTwizz preview site without publishing: `npm run preview` builds the package, puts it in the preview container's `node_modules` under a unique dev version, and restarts its dev server (about 10 seconds). `npm run dev` does the same on every save.
-
-## Releases
-
-- Add a changeset (`npx changeset`) to any PR that changes what sites get.
-- When CI passes on `main`, the Release workflow versions, tags and publishes to npm with provenance (trusted publishing, no token).
-- Dependency updates merged by Renovate ship as a patch on their own.
-- Run the Release workflow by hand to publish the current commit under the `next` tag and try it on a test site first.
-
-Sites pin an exact version, so a release never changes a live site until WebTwizz upgrades it.
-
-The WebTwizz AI builds from its own copy of AI_GUIDE.md. After a release, run `npm run cloud:sync <version>` in the ai-service so new sites get that version and its guide.
-
-## License
-
-MIT

package/package.json

@@ -1,13 +1,9 @@
 {
   "name": "@webtwizz/cloud",
-  "version": "0.5.0",
+  "version": "0.5.1",
   "description": "Sign-ins, database and file storage for sites built on WebTwizz Cloud",
   "license": "MIT",
   "type": "module",
-  "repository": {
-    "type": "git",
-    "url": "git+https://github.com/WebTwizz/webtwizz-cloud.git"
-  },
   "homepage": "https://webtwizz.com",
   "keywords": [
     "webtwizz",
@@ -63,8 +59,7 @@
     "node": ">=20"
   },
   "publishConfig": {
-    "access": "public",
-    "provenance": true
+    "access": "public"
   },
   "peerDependencies": {
     "next": ">=16.0.0",