@postman/sdk-config 0.7.0 → 0.8.0

package/dist/{typescript-BdDv_kwT.d.cts → typescript-Chge0X4f.d.cts}

@@ -292,9 +292,9 @@ declare const pythonGenerationConfigSchema: z.ZodObject<{
     pydanticVersion: z.ZodOptional<z.ZodString>;
     pydantic: z.ZodOptional<z.ZodObject<{
         versionCompatibility: z.ZodOptional<z.ZodEnum<{
-            both: "both";
             v1: "v1";
             v2: "v2";
+            both: "both";
             "v1-on-v2": "v1-on-v2";
         }>>;
         frozen: z.ZodOptional<z.ZodBoolean>;
@@ -419,7 +419,6 @@ declare const typescriptGenerationConfigSchema: z.ZodObject<{
         pnpm: "pnpm";
         yarn: "yarn";
     }>>;
-    /** e.g. `1.22.22` — from the customer's own `config.packageJson.packageManager` (`yarn@1.22.22`). */
     packageManagerVersion: z.ZodOptional<z.ZodString>;
     testFramework: z.ZodOptional<z.ZodEnum<{
         jest: "jest";

package/dist/{typescript-BdDv_kwT.d.ts → typescript-Chge0X4f.d.ts}

@@ -292,9 +292,9 @@ declare const pythonGenerationConfigSchema: z.ZodObject<{
     pydanticVersion: z.ZodOptional<z.ZodString>;
     pydantic: z.ZodOptional<z.ZodObject<{
         versionCompatibility: z.ZodOptional<z.ZodEnum<{
-            both: "both";
             v1: "v1";
             v2: "v2";
+            both: "both";
             "v1-on-v2": "v1-on-v2";
         }>>;
         frozen: z.ZodOptional<z.ZodBoolean>;
@@ -419,7 +419,6 @@ declare const typescriptGenerationConfigSchema: z.ZodObject<{
         pnpm: "pnpm";
         yarn: "yarn";
     }>>;
-    /** e.g. `1.22.22` — from the customer's own `config.packageJson.packageManager` (`yarn@1.22.22`). */
     packageManagerVersion: z.ZodOptional<z.ZodString>;
     testFramework: z.ZodOptional<z.ZodEnum<{
         jest: "jest";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@postman/sdk-config",
-  "version": "0.7.0",
+  "version": "0.8.0",
   "description": "Shared SDK configuration contracts and transformations for Postman SDK generation",
   "license": "UNLICENSED",
   "sideEffects": false,

package/src/sdk-config/v1/README.md

@@ -63,8 +63,9 @@ severity, reason, suggested manual action, and the SDK Config destination when o
 cases. Generation must not recover omitted values from legacy configuration. Differing
 target-specific values are retained as sparse target overrides when the public shape can represent
 them. Optional `api` enrichment may be supplied after Fern's definition or IR has already been
-lowered into the public API shape. Credentials and signing material are preserved in SDK Config
-output blocks when present; callers must treat these fields as sensitive secrets.
+lowered into the public API shape. Supported registry credentials, signing material, and GitHub
+credentials are preserved in SDK Config when present; callers must treat these fields as sensitive
+secrets.
 
 ## Contract boundaries
 
@@ -88,12 +89,14 @@ server-generated artifact metadata are not valid public locators. The public sch
 no `compatibility`, source-origin, artifact ID, credential-resolution, or server-generated
 publishing control fields. Supported registry credentials are flat fields selected by the `registry`
 discriminator: npm and crates accept `token`, PyPI and Maven accept `username` and `password`, and
-Maven accepts a complete `signature` containing `keyId`, `password`, and `secretKey`. Use environment
-expressions such as `${NPM_TOKEN}` for every credential rather than literal values. Unknown fields
-are rejected at every object boundary. Fern migration copies credential fields only when their raw
-`generators.yml` values are exact environment expressions. It never treats normalized or resolved
-output as credential provenance; literals and untraceable values are omitted with credential-safe
-warnings. Portable API, client, documentation, package, source settings, and language field schemas
+Maven accepts a complete `signature` containing `keyId`, `password`, and `secretKey`. GitHub delivery
+accepts a `credentials` object containing `username`, `password`, `token`, or `apiKey`. Use
+environment expressions such as `${NPM_TOKEN}` for every credential rather than literal values.
+Unknown fields are rejected at every object boundary. Fern migration copies credential fields only
+when their raw `generators.yml` values are exact environment expressions. It never treats normalized
+or resolved output as credential provenance; literals and untraceable values are omitted with
+credential-safe warnings. Portable API, client, documentation, package, source settings, and
+language field schemas
 come from a neutral shared domain layer to prevent drift; the public and internal envelopes and
 their operational extensions remain separate explicit allowlists.
 
@@ -117,8 +120,6 @@ segments. Absolute paths and `..` traversal are rejected at validation time.
   "output": { "delivery": "zip" },
   "replay": { "enabled": false },
   "generation": {
-    "includeWatermark": true,
-    "generateFullProject": false,
     "naming": { "smartCasing": true, "smartCasingDigitWordBoundary": false }
   },
   "targets": [
@@ -213,10 +214,10 @@ while an explicitly supplied array replaces the inherited array.
 
 An integration may also supply operational values at generation time. Those request values take
 precedence over the persisted SDK Config for fields the integration exposes, such as SDK name,
-SDK version, API version, package settings, generator version, output intent, and package-building
-requests such as `generation.generateFullProject`. The SDK Config continues to provide every field
-that the request does not override. Schema/domain defaults are applied only after this merge, when
-the single-target `SdkConfigIrV1` is parsed.
+SDK version, API version, package settings, generator version, and output intent. Operational
+packaging controls remain on the generation request rather than in the customer-authored SDK
+Config. Schema/domain defaults are applied only after this merge, when the single-target
+`SdkConfigIrV1` is parsed.
 
 Package publication requirements are validated after applying package and output precedence. For
 example, a TypeScript target publishing to npm may inherit a root `packageName`, while a Python