@lepsto/sdk-app 118.0.0 → 118.0.2

package/CHANGELOG.md

@@ -125,43 +125,11 @@ before this point lives in that package.
 The publish pipeline appends its machine-rendered block for the release being
 built below this line. It is not committed back to the repo, so in a git
 checkout this section is empty — see the note at the top.
-## 118.0.0 (major)
+## 118.0.2 (patch)
 
 ### deployment
-- `deployment_canvas_get`: new optional field `services.appliedProbes (output)`
-- `deployment_canvas_get`: new optional field `services.startupAutomatic (output)`
-- `deployment_canvas_get`: new optional field `services.probes.startup (output)`
-- `deployment_canvas_get`: type change on `services.source (output)`
-- `deployment_events_list_by_environment`: new accepted value on `type`
-- `deployment_events_list_by_environment`: new accepted value on `type (output)`
-- `deployment_events_list_by_service`: new accepted value on `type`
-- `deployment_events_list_by_service`: new accepted value on `type (output)`
-- `deployment_service_create`: new optional field `probes.startup`
-- `deployment_service_create`: type change on `source`
-- `deployment_service_create`: new optional field `appliedProbes (output)`
-- `deployment_service_create`: new optional field `startupAutomatic (output)`
-- `deployment_service_create`: new optional field `probes.startup (output)`
-- `deployment_service_create`: type change on `source (output)`
 - `deployment_service_create`: description updated
-- `deployment_service_get`: new optional field `appliedProbes (output)`
-- `deployment_service_get`: new optional field `startupAutomatic (output)`
-- `deployment_service_get`: new optional field `probes.startup (output)`
-- `deployment_service_get`: type change on `source (output)`
 - `deployment_service_get`: description updated
-- `deployment_service_list`: new optional field `appliedProbes (output)`
-- `deployment_service_list`: new optional field `startupAutomatic (output)`
-- `deployment_service_list`: new optional field `probes.startup (output)`
-- `deployment_service_list`: type change on `source (output)`
 - `deployment_service_list`: description updated
-- `deployment_service_scale`: new optional field `appliedProbes (output)`
-- `deployment_service_scale`: new optional field `startupAutomatic (output)`
-- `deployment_service_scale`: new optional field `probes.startup (output)`
-- `deployment_service_scale`: type change on `source (output)`
-- `deployment_service_update`: new optional field `probes.startup`
-- `deployment_service_update`: type change on `source`
-- `deployment_service_update`: new optional field `appliedProbes (output)`
-- `deployment_service_update`: new optional field `startupAutomatic (output)`
-- `deployment_service_update`: new optional field `probes.startup (output)`
-- `deployment_service_update`: type change on `source (output)`
 - `deployment_service_update`: description updated
 

package/dist/_types/gen/types.gen.d.ts

@@ -369267,7 +369267,7 @@ export interface DeploymentCanvasGetOutput {
             type: "git";
             build?: {
                 /**
-                 * Names of existing secret variables to expose to a git Docker build as BuildKit secret ids KEY and lowercase(key). Values are never included in the service response. Not applied to builds yet: the selection is saved and validated, but builds do not receive these secrets until a later release.
+                 * Names of existing secret variables to expose to a git Docker build as BuildKit secret ids KEY and lowercase(key). Values are never included in the service response. In the Dockerfile a build secret is a file only: RUN --mount=type=secret,id=<key> and read /run/secrets/<key>; env= is not supported.
                  *
                  * @maxItems 20
                  */
@@ -370881,7 +370881,7 @@ export interface DeploymentServiceCreateInput {
         type: "git";
         build?: {
             /**
-             * Names of existing secret variables to expose to a git Docker build as BuildKit secret ids KEY and lowercase(key). Values are never included in the service response. Not applied to builds yet: the selection is saved and validated, but builds do not receive these secrets until a later release.
+             * Names of existing secret variables to expose to a git Docker build as BuildKit secret ids KEY and lowercase(key). Values are never included in the service response. In the Dockerfile a build secret is a file only: RUN --mount=type=secret,id=<key> and read /run/secrets/<key>; env= is not supported.
              *
              * @maxItems 20
              */
@@ -370983,7 +370983,7 @@ export interface DeploymentServiceCreateOutput {
         type: "git";
         build?: {
             /**
-             * Names of existing secret variables to expose to a git Docker build as BuildKit secret ids KEY and lowercase(key). Values are never included in the service response. Not applied to builds yet: the selection is saved and validated, but builds do not receive these secrets until a later release.
+             * Names of existing secret variables to expose to a git Docker build as BuildKit secret ids KEY and lowercase(key). Values are never included in the service response. In the Dockerfile a build secret is a file only: RUN --mount=type=secret,id=<key> and read /run/secrets/<key>; env= is not supported.
              *
              * @maxItems 20
              */
@@ -371144,7 +371144,7 @@ export interface DeploymentServiceGetOutput {
         type: "git";
         build?: {
             /**
-             * Names of existing secret variables to expose to a git Docker build as BuildKit secret ids KEY and lowercase(key). Values are never included in the service response. Not applied to builds yet: the selection is saved and validated, but builds do not receive these secrets until a later release.
+             * Names of existing secret variables to expose to a git Docker build as BuildKit secret ids KEY and lowercase(key). Values are never included in the service response. In the Dockerfile a build secret is a file only: RUN --mount=type=secret,id=<key> and read /run/secrets/<key>; env= is not supported.
              *
              * @maxItems 20
              */
@@ -371276,7 +371276,7 @@ export type DeploymentServiceListOutput = {
         type: "git";
         build?: {
             /**
-             * Names of existing secret variables to expose to a git Docker build as BuildKit secret ids KEY and lowercase(key). Values are never included in the service response. Not applied to builds yet: the selection is saved and validated, but builds do not receive these secrets until a later release.
+             * Names of existing secret variables to expose to a git Docker build as BuildKit secret ids KEY and lowercase(key). Values are never included in the service response. In the Dockerfile a build secret is a file only: RUN --mount=type=secret,id=<key> and read /run/secrets/<key>; env= is not supported.
              *
              * @maxItems 20
              */
@@ -371478,7 +371478,7 @@ export interface DeploymentServiceScaleOutput {
         type: "git";
         build?: {
             /**
-             * Names of existing secret variables to expose to a git Docker build as BuildKit secret ids KEY and lowercase(key). Values are never included in the service response. Not applied to builds yet: the selection is saved and validated, but builds do not receive these secrets until a later release.
+             * Names of existing secret variables to expose to a git Docker build as BuildKit secret ids KEY and lowercase(key). Values are never included in the service response. In the Dockerfile a build secret is a file only: RUN --mount=type=secret,id=<key> and read /run/secrets/<key>; env= is not supported.
              *
              * @maxItems 20
              */
@@ -371606,7 +371606,7 @@ export interface DeploymentServiceUpdateInput {
         type: "git";
         build?: {
             /**
-             * Names of existing secret variables to expose to a git Docker build as BuildKit secret ids KEY and lowercase(key). Values are never included in the service response. Not applied to builds yet: the selection is saved and validated, but builds do not receive these secrets until a later release.
+             * Names of existing secret variables to expose to a git Docker build as BuildKit secret ids KEY and lowercase(key). Values are never included in the service response. In the Dockerfile a build secret is a file only: RUN --mount=type=secret,id=<key> and read /run/secrets/<key>; env= is not supported.
              *
              * @maxItems 20
              */
@@ -371718,7 +371718,7 @@ export interface DeploymentServiceUpdateOutput {
         type: "git";
         build?: {
             /**
-             * Names of existing secret variables to expose to a git Docker build as BuildKit secret ids KEY and lowercase(key). Values are never included in the service response. Not applied to builds yet: the selection is saved and validated, but builds do not receive these secrets until a later release.
+             * Names of existing secret variables to expose to a git Docker build as BuildKit secret ids KEY and lowercase(key). Values are never included in the service response. In the Dockerfile a build secret is a file only: RUN --mount=type=secret,id=<key> and read /run/secrets/<key>; env= is not supported.
              *
              * @maxItems 20
              */

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@lepsto/sdk-app",
   "description": "The Lepsto SDK for App is a TypeScript SDK that provides runtime bindings and type-safe generated code for interacting with Lepsto Platform APIs and services. This package generates type definitions and client bindings from API catalogs, enabling developers to build applications that consume Lepsto platform services with full type safety and autocompletion.",
-  "version": "118.0.0",
+  "version": "118.0.2",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/lepsto/lepsto-sdk-app.git"
@@ -210,5 +210,5 @@
       }
     }
   },
-  "sdkContentHash": "sha256:f31d9c41fc49207d10d494d3724d7a97238e1c2a5c4a283e6edc64f31956d00e"
+  "sdkContentHash": "sha256:bfcd7a9affc29a90f1b53f008bf41b31bd5e1a41cc658038813ee01e53295bca"
 }

package/src/gen/types.gen.ts

@@ -362170,7 +362170,7 @@ path?: string
 type: "git"
 build?: {
 /**
- * Names of existing secret variables to expose to a git Docker build as BuildKit secret ids KEY and lowercase(key). Values are never included in the service response. Not applied to builds yet: the selection is saved and validated, but builds do not receive these secrets until a later release.
+ * Names of existing secret variables to expose to a git Docker build as BuildKit secret ids KEY and lowercase(key). Values are never included in the service response. In the Dockerfile a build secret is a file only: RUN --mount=type=secret,id=<key> and read /run/secrets/<key>; env= is not supported.
  * 
  * @maxItems 20
  */
@@ -363921,7 +363921,7 @@ path?: string
 type: "git"
 build?: {
 /**
- * Names of existing secret variables to expose to a git Docker build as BuildKit secret ids KEY and lowercase(key). Values are never included in the service response. Not applied to builds yet: the selection is saved and validated, but builds do not receive these secrets until a later release.
+ * Names of existing secret variables to expose to a git Docker build as BuildKit secret ids KEY and lowercase(key). Values are never included in the service response. In the Dockerfile a build secret is a file only: RUN --mount=type=secret,id=<key> and read /run/secrets/<key>; env= is not supported.
  * 
  * @maxItems 20
  */
@@ -364024,7 +364024,7 @@ path?: string
 type: "git"
 build?: {
 /**
- * Names of existing secret variables to expose to a git Docker build as BuildKit secret ids KEY and lowercase(key). Values are never included in the service response. Not applied to builds yet: the selection is saved and validated, but builds do not receive these secrets until a later release.
+ * Names of existing secret variables to expose to a git Docker build as BuildKit secret ids KEY and lowercase(key). Values are never included in the service response. In the Dockerfile a build secret is a file only: RUN --mount=type=secret,id=<key> and read /run/secrets/<key>; env= is not supported.
  * 
  * @maxItems 20
  */
@@ -364191,7 +364191,7 @@ path?: string
 type: "git"
 build?: {
 /**
- * Names of existing secret variables to expose to a git Docker build as BuildKit secret ids KEY and lowercase(key). Values are never included in the service response. Not applied to builds yet: the selection is saved and validated, but builds do not receive these secrets until a later release.
+ * Names of existing secret variables to expose to a git Docker build as BuildKit secret ids KEY and lowercase(key). Values are never included in the service response. In the Dockerfile a build secret is a file only: RUN --mount=type=secret,id=<key> and read /run/secrets/<key>; env= is not supported.
  * 
  * @maxItems 20
  */
@@ -364325,7 +364325,7 @@ path?: string
 type: "git"
 build?: {
 /**
- * Names of existing secret variables to expose to a git Docker build as BuildKit secret ids KEY and lowercase(key). Values are never included in the service response. Not applied to builds yet: the selection is saved and validated, but builds do not receive these secrets until a later release.
+ * Names of existing secret variables to expose to a git Docker build as BuildKit secret ids KEY and lowercase(key). Values are never included in the service response. In the Dockerfile a build secret is a file only: RUN --mount=type=secret,id=<key> and read /run/secrets/<key>; env= is not supported.
  * 
  * @maxItems 20
  */
@@ -364538,7 +364538,7 @@ path?: string
 type: "git"
 build?: {
 /**
- * Names of existing secret variables to expose to a git Docker build as BuildKit secret ids KEY and lowercase(key). Values are never included in the service response. Not applied to builds yet: the selection is saved and validated, but builds do not receive these secrets until a later release.
+ * Names of existing secret variables to expose to a git Docker build as BuildKit secret ids KEY and lowercase(key). Values are never included in the service response. In the Dockerfile a build secret is a file only: RUN --mount=type=secret,id=<key> and read /run/secrets/<key>; env= is not supported.
  * 
  * @maxItems 20
  */
@@ -364667,7 +364667,7 @@ path?: string
 type: "git"
 build?: {
 /**
- * Names of existing secret variables to expose to a git Docker build as BuildKit secret ids KEY and lowercase(key). Values are never included in the service response. Not applied to builds yet: the selection is saved and validated, but builds do not receive these secrets until a later release.
+ * Names of existing secret variables to expose to a git Docker build as BuildKit secret ids KEY and lowercase(key). Values are never included in the service response. In the Dockerfile a build secret is a file only: RUN --mount=type=secret,id=<key> and read /run/secrets/<key>; env= is not supported.
  * 
  * @maxItems 20
  */
@@ -364780,7 +364780,7 @@ path?: string
 type: "git"
 build?: {
 /**
- * Names of existing secret variables to expose to a git Docker build as BuildKit secret ids KEY and lowercase(key). Values are never included in the service response. Not applied to builds yet: the selection is saved and validated, but builds do not receive these secrets until a later release.
+ * Names of existing secret variables to expose to a git Docker build as BuildKit secret ids KEY and lowercase(key). Values are never included in the service response. In the Dockerfile a build secret is a file only: RUN --mount=type=secret,id=<key> and read /run/secrets/<key>; env= is not supported.
  * 
  * @maxItems 20
  */