@valbuild/language-server 0.146.4 → 0.148.0

package/CHANGELOG.md

@@ -1,5 +1,33 @@
 # @valbuild/language-server
 
+## 0.148.0
+
+### Patch Changes
+
+- [#818](https://github.com/valbuild/val/pull/818) [`562d032`](https://github.com/valbuild/val/commit/562d03280c3fcf97a80562e8b017dd2125ac4ad1) Thanks [@freekh](https://github.com/freekh)! - Remote files served from a project's own site (addresses like
+  `https://www.acme.no/_val/file/…`) are now checked for whether that address
+  still serves the project. When a custom domain has been removed or moved to
+  another project, the image or file is reported, and **Fix** on the Studio's
+  Validate page — or `val validate --fix` — points it at the project's permanent
+  `<id>.valstart.dev` address. Nothing is uploaded or downloaded: only the address
+  changes.
+
+  Remote file addresses with a `/_val` prefix after the host are now recognised.
+
+- Updated dependencies [[`df5544c`](https://github.com/valbuild/val/commit/df5544c6e92a4c3a52765630c9de191e854ee723), [`562d032`](https://github.com/valbuild/val/commit/562d03280c3fcf97a80562e8b017dd2125ac4ad1), [`562d032`](https://github.com/valbuild/val/commit/562d03280c3fcf97a80562e8b017dd2125ac4ad1), [`562d032`](https://github.com/valbuild/val/commit/562d03280c3fcf97a80562e8b017dd2125ac4ad1), [`562d032`](https://github.com/valbuild/val/commit/562d03280c3fcf97a80562e8b017dd2125ac4ad1), [`562d032`](https://github.com/valbuild/val/commit/562d03280c3fcf97a80562e8b017dd2125ac4ad1), [`562d032`](https://github.com/valbuild/val/commit/562d03280c3fcf97a80562e8b017dd2125ac4ad1), [`562d032`](https://github.com/valbuild/val/commit/562d03280c3fcf97a80562e8b017dd2125ac4ad1), [`562d032`](https://github.com/valbuild/val/commit/562d03280c3fcf97a80562e8b017dd2125ac4ad1)]:
+  - @valbuild/server@0.148.0
+  - @valbuild/shared@0.148.0
+  - @valbuild/core@0.148.0
+
+## 0.147.0
+
+### Patch Changes
+
+- Updated dependencies [[`2f09cd5`](https://github.com/valbuild/val/commit/2f09cd5e2f4fc37f06917899f24f9ad2ee8d3a8b), [`cb04e58`](https://github.com/valbuild/val/commit/cb04e586db1e3ffd20ec1fee744561b1c8f8cffd), [`cb04e58`](https://github.com/valbuild/val/commit/cb04e586db1e3ffd20ec1fee744561b1c8f8cffd)]:
+  - @valbuild/core@0.147.0
+  - @valbuild/shared@0.147.0
+  - @valbuild/server@0.147.0
+
 ## 0.146.4
 
 ### Patch Changes

package/dist/valbuild-language-server.cjs.dev.js

@@ -183,7 +183,7 @@ var packageJson = {
 		"lsp",
 		"language-server"
 	],
-	version: "0.146.4",
+	version: "0.148.0",
 	bin: {
 		"val-language-server": "./bin.js"
 	},
@@ -2784,7 +2784,12 @@ const LOCAL_FIXES = ["image:add-metadata", "image:check-metadata", "file:add-met
 "videos:add-metadata",
 // A view pointing at the wrong module: the schema names the right one, so the
 // fix is a value the patch already knows. Nothing read, nothing fetched.
-"view:check-module"];
+"view:check-module"
+// Not here, deliberately: `remote:rewrite-host`. The edit is local, but
+// FINDING it asks the ref's host over the network, inside `image:check-remote`'s
+// adjudication (`mediaChecks.ts`), whose findings carry no fixes -- so the
+// diagnostic says what `val validate --fix` will do, and offers no lightbulb.
+];
 
 /**
  * Fixes that are local, but are NOT a patch against the document they are

package/dist/valbuild-language-server.cjs.prod.js

@@ -183,7 +183,7 @@ var packageJson = {
 		"lsp",
 		"language-server"
 	],
-	version: "0.146.4",
+	version: "0.148.0",
 	bin: {
 		"val-language-server": "./bin.js"
 	},
@@ -2784,7 +2784,12 @@ const LOCAL_FIXES = ["image:add-metadata", "image:check-metadata", "file:add-met
 "videos:add-metadata",
 // A view pointing at the wrong module: the schema names the right one, so the
 // fix is a value the patch already knows. Nothing read, nothing fetched.
-"view:check-module"];
+"view:check-module"
+// Not here, deliberately: `remote:rewrite-host`. The edit is local, but
+// FINDING it asks the ref's host over the network, inside `image:check-remote`'s
+// adjudication (`mediaChecks.ts`), whose findings carry no fixes -- so the
+// diagnostic says what `val validate --fix` will do, and offers no lightbulb.
+];
 
 /**
  * Fixes that are local, but are NOT a patch against the document they are

package/dist/valbuild-language-server.esm.js

@@ -172,7 +172,7 @@ var packageJson = {
 		"lsp",
 		"language-server"
 	],
-	version: "0.146.4",
+	version: "0.148.0",
 	bin: {
 		"val-language-server": "./bin.js"
 	},
@@ -2773,7 +2773,12 @@ const LOCAL_FIXES = ["image:add-metadata", "image:check-metadata", "file:add-met
 "videos:add-metadata",
 // A view pointing at the wrong module: the schema names the right one, so the
 // fix is a value the patch already knows. Nothing read, nothing fetched.
-"view:check-module"];
+"view:check-module"
+// Not here, deliberately: `remote:rewrite-host`. The edit is local, but
+// FINDING it asks the ref's host over the network, inside `image:check-remote`'s
+// adjudication (`mediaChecks.ts`), whose findings carry no fixes -- so the
+// diagnostic says what `val validate --fix` will do, and offers no lightbulb.
+];
 
 /**
  * Fixes that are local, but are NOT a patch against the document they are

package/package.json

@@ -11,7 +11,7 @@
     "lsp",
     "language-server"
   ],
-  "version": "0.146.4",
+  "version": "0.148.0",
   "bin": {
     "val-language-server": "./bin.js"
   },
@@ -29,9 +29,9 @@
     "typescript": "^6.0.3",
     "vscode-languageserver": "^10.1.0",
     "vscode-languageserver-textdocument": "^1.0.14",
-    "@valbuild/core": "0.146.2",
-    "@valbuild/server": "0.146.4",
-    "@valbuild/shared": "0.146.4"
+    "@valbuild/server": "0.148.0",
+    "@valbuild/core": "0.148.0",
+    "@valbuild/shared": "0.148.0"
   },
   "devDependencies": {
     "@types/jest": "^30.0.0",