@postman/sdk-config 0.4.0 → 0.5.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -73,10 +73,13 @@ if (!result.success) {
73
73
  ```
74
74
 
75
75
  SDK Config objects are strict. Unknown fields, duplicate language targets, incompatible package
76
- publication settings, and non-exact generator versions are rejected. Publishing credentials and
77
- signing material may be provided under `output.publish.credentials`, Maven
78
- `output.publish.signature`, or `output.github.credentials`; these fields can contain raw secrets and
79
- must be handled accordingly by clients and servers.
76
+ publication settings, and non-exact generator versions are rejected. npm and crates use
77
+ `output.publish.token`, PyPI and Maven use flat `username` and `password` fields, and Maven may also
78
+ use a complete `signature` object. Configure these fields with environment expressions such as
79
+ `${NPM_TOKEN}` rather than literal credentials. Clients must resolve and transport credentials using
80
+ a dedicated secret channel and remove them from generation payloads, logs, and stored artifacts.
81
+ Fern migration preserves a credential only when the raw `generators.yml` value is exactly an
82
+ environment expression; normalized, resolved, or literal values are omitted with a warning.
80
83
 
81
84
  `SdkConfigV1` accepts customer-facing local source paths and HTTP(S) source URLs, but not
82
85
  server-owned signed URLs or artifact metadata. See the