@tailor-platform/sdk 2.19.0 → 2.20.0

package/docs/configuration.md

@@ -245,6 +245,23 @@ export default defineConfig({
 });
 ```
 
+A value can reference a [static website](./services/staticwebsite.md#type-safe-url-references) through its `url` property, the same reference `cors` and OAuth2 redirect URIs accept. Resolver, executor, workflow job, and auth before-login hook code, and TailorDB migration scripts, then read the deployed website URL:
+
+```typescript
+const website = defineStaticWebSite("my-frontend", { description: "Frontend" });
+
+export default defineConfig({
+  name: "my-app",
+  env: {
+    siteUrl: website.url, // https://my-frontend.example.com
+    callbackUrl: `${website.url}/callback`, // https://my-frontend.example.com/callback
+  },
+  staticWebsites: [website],
+});
+```
+
+This resolves even when the same deploy both creates the website and reads its URL — one `deploy` call is enough, with no second, manually-triggered `deploy` needed. If the referenced website does not exist at all, the CLI warns and leaves the unresolved reference in place. If the reference still can't be resolved after this deploy's rebuild, the deploy fails instead of shipping the unresolved reference. This platform lookup only happens during `deploy`; `function run` passes the literal `<name>:url` string unchanged, since it never talks to the platform to resolve it.
+
 `tailor.config.ts` runs locally when an SDK command loads the config. If values come from your shell or an env file, SDK commands can load them before config evaluation with the global [`--env-file`](./cli-reference.md#environment-file-loading) and `--env-file-if-exists` options:
 
 ```typescript
@@ -260,7 +277,7 @@ export default defineConfig({
 
 If the same config defines an auth before-login hook, make sure the config module can be evaluated without Node-only globals in the platform runtime. Avoid arbitrary `process.env` reads in that module; pass literal values, or values generated into a config module before deployment, and read them from the hook's `env` argument.
 
-When the SDK deploys application code or runs detected service code with `function run`, it passes the resolved values as the `env` argument. Do not read `process.env` from deployed resolvers, executors, workflow jobs, auth hooks, or migration scripts; Node-side environment variables are not available there. Put sensitive values in [Secret Manager](./services/secret.md) instead of `env`.
+When the SDK deploys application code or runs detected service code with `function run`, it passes the values `tailor.config.ts` evaluated to as the `env` argument -- except a static website `<name>:url` reference, which only `deploy` resolves (see above). Do not read `process.env` from deployed resolvers, executors, workflow jobs, auth hooks, or migration scripts; Node-side environment variables are not available there. Put sensitive values in [Secret Manager](./services/secret.md) instead of `env`.
 
 | Code location             | Runtime access                                                                                                                            |
 | ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |

package/docs/services/staticwebsite.md

@@ -113,6 +113,23 @@ const auth = defineAuth("my-auth", {
 });
 ```
 
+### Application Environment Variables
+
+```typescript
+const website = defineStaticWebSite("my-frontend", {
+  description: "Frontend application",
+});
+
+export default defineConfig({
+  env: {
+    siteUrl: website.url, // https://my-frontend.example.com
+  },
+  staticWebsites: [website],
+});
+```
+
+Resolver, executor, workflow job, and auth before-login hook code, and TailorDB migration scripts, that read [`env`](../configuration.md#environment-variables) receive the deployed URL, even when the same deploy both creates the website and reads its URL — one `deploy` call resolves it, with no second, manually-triggered `deploy` needed. If the referenced website does not exist at all, the CLI warns and leaves the unresolved reference in place. If the reference still can't be resolved after this deploy's rebuild, the deploy fails instead of shipping the unresolved reference. This platform lookup only happens during `deploy`; `function run` passes the literal `<name>:url` string unchanged, since it never talks to the platform to resolve it.
+
 ## Complete Example
 
 ```typescript

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tailor-platform/sdk",
-  "version": "2.19.0",
+  "version": "2.20.0",
   "description": "Tailor Platform SDK - The SDK to work with Tailor Platform",
   "license": "MIT",
   "repository": {
@@ -185,7 +185,7 @@
     "inflection": "3.0.2",
     "kysely": "0.29.5",
     "mime-types": "3.0.2",
-    "open": "11.0.3",
+    "open": "11.0.4",
     "oxc-parser": "0.149.0",
     "p-limit": "7.3.2",
     "pathe": "2.0.3",
@@ -212,7 +212,7 @@
     "@types/semver": "7.8.0",
     "@typescript/native-preview": "7.0.0-dev.20260707.2",
     "@vitest/coverage-v8": "5.0.0",
-    "eslint-plugin-zod": "4.12.1",
+    "eslint-plugin-zod": "4.13.1",
     "oxfmt": "0.67.0",
     "oxlint": "1.82.0",
     "oxlint-tsgolint": "7.0.2001",
@@ -220,7 +220,7 @@
     "tsdown": "0.23.0",
     "typescript": "6.0.3",
     "vitest": "5.0.0",
-    "zinfer": "0.4.6"
+    "zinfer": "0.4.7"
   },
   "peerDependencies": {
     "@electric-sql/pglite": ">=0.2.0",