release(v4.0.0): Shade GA — V3.x consolidation + audit prep
Some checks failed
Test / test (push) Has been cancelled
Cross-platform vectors / TypeScript vectors (bun) (push) Has been cancelled
Cross-platform vectors / Kotlin vectors (gradle) (push) Has been cancelled
Docker build and publish / docker (push) Has been cancelled
Publish / publish (push) Has been cancelled

V3.1 → V3.12 consolidated and tagged for the first GA release. Wire
format unchanged from 0.4.x — 4.0 peers interoperate with 0.4.x peers
byte-for-byte. The version bump is semantic: audit-cycle complete,
opt-in surface fully exposed, threat model refreshed for every new
surface.

Highlights:
- All 24 @shade/* packages bumped to 4.0.0 in lockstep.
- CHANGELOG 4.0.0 section is the canonical manifest of what landed.
- THREAT-MODEL extended (§10 fingerprint gates, §11 WebRTC P2P, §12
  Web-Worker boundary) + residual-risks table refreshed.
- OpenAPI now covers all 27 routes: prekey, transfer, KT, inbox,
  bridge, observer, /metrics, /healthz, /ready.
- MIGRATION 0.3.x → 4.0 documented + smoke-tested against
  shade migrate-storage on a real SQLite DB.
- docs/audit/REVIEW-BUNDLE.md + SCOPE.md ready for external reviewer.
- scripts/soak.ts harness for the GA-stable 2-week soak window.
- All V*.md plans archived under docs/archive/ with Status: Done.
- Voice/Video carved out into V5.0; 4.0 audit focuses on the frozen
  non-realtime stack.

Tests: TS 1000/1000 + Kotlin 11/11 cross-platform vectors green.
Docker: gt.zyon.no/stian/shade-prekey:4.0.0 builds and reports
  version 4.0.0 on /health.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
2026-05-03 18:35:35 +02:00
parent 8b055912b7
commit e6fdf31b49
298 changed files with 37909 additions and 256 deletions

View File

@@ -16,17 +16,24 @@ import { readFileSync, writeFileSync, existsSync } from 'fs';
import { join } from 'path';
import { $ } from 'bun';
// Order matters: each package only depends on packages above it. Publishing
// in this order means a consumer fetching mid-publish never sees a manifest
// pointing at an unpublished version.
const PACKAGES = [
'shade-core',
'shade-crypto-web',
'shade-proto',
'shade-crypto-web',
'shade-storage-sqlite',
'shade-storage-postgres',
'shade-server',
'shade-observer',
'shade-streams',
'shade-transport',
'shade-widgets',
'shade-server',
'shade-transfer',
'shade-files',
'shade-recovery',
'shade-observer',
'shade-sdk',
'shade-widgets',
'shade-cli',
];
@@ -71,6 +78,8 @@ async function main() {
let published = 0;
let skipped = 0;
let alreadyPublished = 0;
let failed = 0;
for (const pkg of PACKAGES) {
const pkgDir = join(ROOT, 'packages', pkg);
@@ -97,8 +106,20 @@ async function main() {
published++;
console.log(`${dryRun ? 'packed' : 'published'}`);
} catch (err) {
console.error(` ✗ failed: ${(err as Error).message}`);
process.exitCode = 1;
const out = `${err instanceof Error ? err.message : String(err)} ${
(err as { stderr?: { toString(): string } }).stderr?.toString() ?? ''
} ${(err as { stdout?: { toString(): string } }).stdout?.toString() ?? ''}`;
// Gitea (and npm) report already-published versions as 409 / EPUBLISHCONFLICT.
// Skip silently rather than failing the whole run — bumping the version
// is the user's explicit decision via `bun run version <new>`.
if (/409|EPUBLISHCONFLICT|already exists|already been published/i.test(out)) {
alreadyPublished++;
console.log(` ⊙ already published — skipping`);
} else {
failed++;
console.error(` ✗ failed: ${(err as Error).message}`);
process.exitCode = 1;
}
} finally {
// Always restore the original package.json so the workspace stays usable
// for `bun install` after publish, regardless of success or failure.
@@ -112,7 +133,9 @@ async function main() {
} catch {}
console.log();
console.log(`Done: ${published} published, ${skipped} skipped`);
console.log(
`Done: ${published} ${dryRun ? 'packed' : 'published'}, ${alreadyPublished} already published, ${skipped} skipped, ${failed} failed`,
);
}
/**