com.robotsquid.squidhub 0.5.10 → 0.5.12

package/CHANGELOG.md

@@ -1,5 +1,50 @@
 # Changelog
 
+## 0.5.12
+
+**A manifest change is a new version now — the platform changed underneath this.**
+
+Editing `manifest.json` and re-uploading used to report "these exact bytes are
+already published, nothing to upload" and discard the edit. Server migration
+0029 makes version identity `(build_hash, manifest_sha256)`, so a changed
+declaration registers a new version and takes effect.
+
+⚠️ **`manifest.json` is still excluded from the build hash and must be** — it
+CONTAINS that hash, so folding it in has no fixed point. A separate digest of
+the manifest file has no such circularity, because a manifest never contains its
+own digest. The bytes are still deduped: two versions differing only in
+declaration share one copy in R2.
+
+⚠️ **The 0.5.11 "your manifest was ignored" explanation is GONE**, because it is
+now false. That message fired when the bytes matched; the bytes matching now
+also means the manifest matched. Telling a publisher their edit was discarded at
+the one moment we know it was not is worse than saying nothing.
+
+**Requires the api deployed with migration 0029.** Against an older server this
+package still works and a manifest-only change still silently does nothing.
+
+## 0.5.11
+
+**"Nothing to upload" now says what it did to your manifest.**
+
+Editing `manifest.json` and pressing Build and Upload reported *"These exact
+bytes are already published. Nothing to upload."* and stopped — never mentioning
+that the declaration had not been applied. With a manifest editor in the package
+that is a normal thing to do, and the result was unreadable.
+
+`manifest.json` is excluded from the build hash — it CONTAINS that hash, so
+including it would have no fixed point — so a build whose only difference is its
+declaration hashes identically and matches a version already registered.
+
+⚠️ **It stops at `start`, before a byte moves, which is EARLIER than the
+server's own `manifest-ignored` warning.** That one is raised at `complete`, and
+such a build never gets there, so this message is the only thing that will ever
+say it.
+
+The dialog now names the manifest and both ways forward: change a real file and
+rebuild, or set the override in the publisher console — display settings are
+live-tunable there and need no new build at all.
+
 ## 0.5.10
 
 **Fullscreen: the check that makes it actually work.**

package/Editor/SquidHubUploader.cs

@@ -186,9 +186,26 @@ namespace SquidHub.Editor
             if (SquidHubBuildScan.JsonField(startResponse, "alreadyPublished") == "true")
             {
                 EditorUtility.ClearProgressBar();
+
+                // ⚠️ A no-op now means the BYTES AND THE DECLARATION both match.
+                // It used to mean only the bytes did, so a changed manifest.json
+                // landed here and was discarded — this dialog carried a long
+                // explanation of that trap. Migration 0029 made version identity
+                // (build_hash, manifest_sha256), so a declaration change
+                // registers a new version and never reaches this branch.
+                //
+                // ⚠️ Do NOT reinstate the old wording. Telling a publisher their
+                // manifest was ignored, at the one moment we know it was not, is
+                // worse than saying nothing.
+                var hash = SquidHubBuildScan.JsonField(startResponse, "buildHash");
+                Debug.Log("[SquidHub] " + hash + " is already published — same bytes, same " +
+                          "manifest. Nothing to upload.");
+
                 EditorUtility.DisplayDialog("SquidHub",
-                    "These exact bytes are already published as " + SquidHubBuildScan.JsonField(startResponse, "buildHash") +
-                    ". Nothing to upload.", "OK");
+                    "Already published as " + hash + ".\n\n" +
+                    "Nothing to upload: both the build and its manifest.json match what is " +
+                    "already registered.",
+                    "OK");
                 yield break;
             }
 

package/README.md

@@ -209,10 +209,14 @@ on your `AudioContext`. It works without you doing anything — but only because
 the bridge is injected ahead of the loader, which is why step 2 above is not
 merely tidy. Tick **Sound** in `SquidHub → Game Manifest…` or no button appears.
 
-⚠️ **Editing `manifest.json` alone changes nothing.** It is excluded from the
-build hash, so a manifest-only re-upload registers no new version and your edit
-is discarded — the server now says so in a warning rather than staying silent.
-Change a real file and rebuild, or set an override in the console.
+⚠️ **Editing `manifest.json` alone registers a new version.** It used not to —
+the manifest is excluded from the build hash, so the build looked identical and
+the edit was discarded. A version is now identified by its bytes *and* its
+declaration, so a manifest-only change ships. The bytes are still deduped: the
+two versions share one copy in R2.
+
+To change display on a build that is already live, the publisher console's
+override is still the faster path — it needs no upload at all.
 
 ## ⚠️ Status
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "com.robotsquid.squidhub",
-  "version": "0.5.10",
+  "version": "0.5.12",
   "displayName": "SquidHub",
   "description": "Cloud saves, analytics and the coin economy for Unity WebGL games published on SquidHub. Installs the C# wrapper, the .jslib half and the page bridge, and rewrites the exported index.html so it survives the platform's CSP.",
   "unity": "2021.3",