@arcadiasystems/morse-sdk 0.8.0 → 0.8.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 (3) hide show
  1. package/CHANGELOG.md +14 -1
  2. package/README.md +3 -2
  3. package/package.json +3 -2
package/CHANGELOG.md CHANGED
@@ -2,9 +2,22 @@
2
2
 
3
3
  All notable changes to `morse-sdk` will be documented in this file. Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) and the project follows [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
4
4
 
5
+ ## [0.8.1] - 2026-09-10
6
+
7
+ Documentation only.
8
+
9
+ ### Fixed
10
+
11
+ - Compatibility table had no `0.8.x` row and the pin example still said `~0.7.0`. The table is what people read before pinning, so a missing row tells them the newest supported version is older than the one they just installed.
12
+ - The reader table now records that `getRecipientFile` throws `ValidationError` when the id resolves to an object of another Move type, which 0.8.0 introduced and only the changelog mentioned.
13
+
14
+ ### Added
15
+
16
+ - `bun run docs-gate`, wired into `prepublishOnly`. It fails when the compatibility table has no row for the current minor, when the pin example names an older one, or when CHANGELOG's newest entry does not match `package.json`. This section had gone stale twice for exactly these reasons and nothing in lint, typecheck or the tests could notice.
17
+
5
18
  ## [0.8.0] - 2026-09-10
6
19
 
7
- Bug-hunt pass over the whole package, not a diff review.
20
+ Bug-hunt pass over the whole package, not a diff review. README gains an 0.8.x compatibility row, corrected pin advice, and a note that the recipient-file reader now rejects a wrong Move type.
8
21
 
9
22
  ### Fixed
10
23
 
package/README.md CHANGED
@@ -40,13 +40,14 @@ morse-sdk is built and tested against specific minor versions of its Mysten subs
40
40
 
41
41
  | morse-sdk | `@mysten/sui` | `@mysten/walrus` | `@mysten/seal` | Sui network | Verified |
42
42
  | --------- | ------------- | ---------------- | -------------- | ----------- | --------- |
43
+ | 0.8.x | 2.16.2-2.16.x | 1.1.6-1.1.x | 1.1.3-1.1.x | testnet | 2026-09-09 |
43
44
  | 0.7.x | 2.16.2-2.16.x | 1.1.6-1.1.x | 1.1.3-1.1.x | testnet | 2026-09-09 |
44
45
  | 0.6.x | 2.16.2-2.16.x | 1.1.6-1.1.x | 1.1.3-1.1.x | testnet | 2026-09-09 |
45
46
  | 0.5.x | 2.16.2-2.16.x | 1.1.6-1.1.x | 1.1.3-1.1.x | testnet | 2026-06-05 |
46
47
  | 0.4.x | 2.16.2-2.16.x | 1.1.6-1.1.x | 1.1.3-1.1.x | testnet | 2026-06-05 |
47
48
  | 0.1.x | 2.16.2-2.16.x | 1.1.6-1.1.x | 1.1.3-1.1.x | testnet | 2026-05-10 |
48
49
 
49
- Mysten ships breaking changes inside major version boundaries. Newer minors (e.g. `@mysten/walrus@1.2.x`, `@mysten/sui@2.17+`) are outside the verified ranges and may produce runtime errors; morse-sdk needs a coordinated bump and re-verification before a new Mysten minor is supported. Pin via `bun add @arcadiasystems/morse-sdk@~0.7.0` if you want patch updates without surprise minors.
50
+ Mysten ships breaking changes inside major version boundaries. Newer minors (e.g. `@mysten/walrus@1.2.x`, `@mysten/sui@2.17+`) are outside the verified ranges and may produce runtime errors; morse-sdk needs a coordinated bump and re-verification before a new Mysten minor is supported. Pin via `bun add @arcadiasystems/morse-sdk@~0.8.0` if you want patch updates without surprise minors.
50
51
 
51
52
  The verification protocol is documented in [`CONTRIBUTING.md`](https://github.com/arcadiasystems/morse-dcms/blob/main/morse-sdk/CONTRIBUTING.md): every Mysten dep bump runs the full `scripts/phase-N-*.ts` smoke suite before the bump lands.
52
53
 
@@ -273,7 +274,7 @@ The full public surface, grouped by concern. Every export carries a JSDoc on its
273
274
  | `reader.listPublicationsOwnedBy` / `listPublisherCapsOwnedBy` / `listEntries` | Paginated lists. |
274
275
  | `reader.scanEntries` | Async-iterator over every entry in a collection. |
275
276
  | `RpcRecipientFilesReader.fromMorseConfig(config, client)` | Construct a reader for the `recipient_file` module. |
276
- | `filesReader.getRecipientFile(id)` | Live single-object read (parses embedded `members`, blob refs). |
277
+ | `filesReader.getRecipientFile(id)` | Live single-object read (parses embedded `members`, blob refs). Throws `ValidationError` if the id resolves to an object of another Move type. |
277
278
  | `filesReader.getRecipientFileSealPrefix(id)` | The file's Seal id prefix, or `null`. The only reliable "is this encrypted" signal. Costs an extra round trip, so it is a separate call. |
278
279
  | `buildRecipientFileEventTypes(originPackageId)` | Fully-qualified event type strings for the `RecipientFile*` events; pass `config.recipientFileEventOriginPackageId`. |
279
280
  | `reconcileRecipientFilesOwnedBy(events, address, eventTypes)` / `reconcileRecipientFilesAccessibleBy(...)` | Pure event-reconciliation helpers — bring your own indexer, get current file sets back. |
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@arcadiasystems/morse-sdk",
3
- "version": "0.8.0",
3
+ "version": "0.8.1",
4
4
  "description": "TypeScript SDK for Morse dCMS on the Sui blockchain.",
5
5
  "license": "MIT",
6
6
  "type": "module",
@@ -41,9 +41,10 @@
41
41
  },
42
42
  "scripts": {
43
43
  "prebuild": "rm -rf dist",
44
- "prepublishOnly": "bun run lint && bun run typecheck && bun test && bun run build",
44
+ "prepublishOnly": "bun run lint && bun run typecheck && bun run docs-gate && bun test && bun run build",
45
45
  "build": "tsc -p tsconfig.build.json",
46
46
  "typecheck": "tsc --noEmit",
47
+ "docs-gate": "bun scripts/docs-gate.ts",
47
48
  "lint": "biome check .",
48
49
  "lint:fix": "biome check --write .",
49
50
  "test": "bun test",