@plutoframework/frontend 0.1.0 → 0.1.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +31 -2
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -165,5 +165,34 @@ Tests cover transition rejection, duplicate actions, stale callbacks, reset,
165
165
  disposal, executor failures, React Strict Mode/SSR and 1,500 deterministic property
166
166
  runs over arbitrary event sequences. Mutation smoke is a bounded set of seeded
167
167
  mutations, not a comprehensive mutation engine. CI tests React 18.3.1 and 19.3.1.
168
- The package is published manually after inspecting its tarball; no npm credentials
169
- are stored in this repository or in GitHub Actions.
168
+ Releases publish through GitHub Actions using npm trusted publishing (OIDC);
169
+ no npm credentials are stored in this repository or in GitHub Actions.
170
+
171
+ ## Publish a release
172
+
173
+ The `publish.yml` workflow publishes stable `vMAJOR.MINOR.PATCH` tags using npm
174
+ trusted publishing and provenance. It checks tag/version agreement and main-branch
175
+ ancestry, runs tests and mutation checks, and verifies packed consumers before
176
+ publishing. Prereleases are rejected. Manual dispatch accepts an existing tag for
177
+ retrying a failed publish; npm never overwrites an already published version.
178
+
179
+ After merging the intended changes into main:
180
+
181
+ ```sh
182
+ npm version patch
183
+ git push origin main --follow-tags
184
+ ```
185
+
186
+ The one-time npm trusted publisher is scoped to:
187
+
188
+ | Setting | Value |
189
+ | -------------- | ---------------- |
190
+ | Organization | `plutoframework` |
191
+ | Repository | `pluto-frontend` |
192
+ | Workflow | `publish.yml` |
193
+ | Environment | None |
194
+ | Allowed action | `npm publish` |
195
+
196
+ The workflow uses GitHub-hosted runners with `id-token: write`; npm exchanges the
197
+ workflow identity for a short-lived publish credential. No `NPM_TOKEN` secret is
198
+ needed. See [npm trusted publishing](https://docs.npmjs.com/trusted-publishers/).
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@plutoframework/frontend",
3
- "version": "0.1.0",
3
+ "version": "0.1.1",
4
4
  "description": "Explicit, typed frontend state transitions and React subscriptions for Pluto applications.",
5
5
  "type": "module",
6
6
  "license": "MIT",