@pi-harness/pi-harness 0.1.27 → 0.1.28

package/packages/api-gateway/test/release-package.test.ts

@@ -63,6 +63,14 @@ describe("release package", () => {
     expect(workflow).toContain("for package_name in @pi-harness/plugin-api @pi-harness/core @pi-harness/pi-harness; do");
   });
 
+  it("creates the GitHub Release before waiting on npm's CDN", async () => {
+    const workflow = await readFile(resolve(repositoryRoot, ".github/workflows/release.yml"), "utf8");
+
+    // Availability is CDN propagation latency, not a publish failure. Ordering the wait first made a slow tarball skip the release step outright, so the tag shipped without one.
+    expect(workflow.indexOf("- name: Create GitHub Release")).toBeLessThan(workflow.indexOf("- name: Verify package availability"));
+    expect(workflow).not.toContain("seq 1 60");
+  });
+
   it("keeps the runtimes in the core type surface as peers so a plugin author resolves one copy", async () => {
     const rootManifest = await readJson("package.json");
     const rootDependencies = rootManifest.dependencies as Record<string, string>;

package/packages/bundle-web-app/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pi-harness/web-app",
-  "version": "0.1.27",
+  "version": "0.1.28",
   "private": true,
   "description": "Patchable Web application bundle for Pi Harness",
   "homepage": "https://github.com/pi-harness/pi-harness#readme",

package/packages/cli/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pi-harness/cli",
-  "version": "0.1.27",
+  "version": "0.1.28",
   "private": true,
   "description": "Plugin-first Pi Harness CLI",
   "homepage": "https://github.com/pi-harness/pi-harness#readme",

package/packages/host-webserver/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pi-harness/host-webserver",
-  "version": "0.1.27",
+  "version": "0.1.28",
   "private": true,
   "description": "Cordis route-registration service for the Pi Harness web host",
   "homepage": "https://github.com/pi-harness/pi-harness#readme",