Skip to content

[pull] main from fern-api:main#789

Merged
pull[bot] merged 3 commits into
code:mainfrom
fern-api:main
Jun 12, 2026
Merged

[pull] main from fern-api:main#789
pull[bot] merged 3 commits into
code:mainfrom
fern-api:main

Conversation

@pull

@pull pull Bot commented Jun 12, 2026

Copy link
Copy Markdown

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

jsklan and others added 3 commits June 11, 2026 20:53
…rator (#16339)

* feat(internal): auto-propagate Rust SDK changelog entries to CLI Generator

When the Rust SDK has unreleased changes and is released, the release
script now automatically creates a changelog entry in the CLI Generator's
unreleased folder. This ensures the CLI Generator ships a new version
whenever the embedded Rust SDK is updated, without manual duplication.

Implementation:
- Add 'propagatesTo' field to release-config.json schema
- Configure rust → cli-generator propagation
- In release.ts, write auto-propagated entry during source release commit
- In release-workflow.ts, topologically sort software list so sources
  are always processed before their dependents

Co-Authored-By: judah <jsklan.development@gmail.com>

* fix: propagate actual source type (fix→fix) and add cli-generator to docs table

Address Devin Review feedback:
- Initialize highestType from first entry instead of hardcoded chore
- Add cli-generator row to release-versioning.md mapping table

Co-Authored-By: judah <jsklan.development@gmail.com>

* fix: remove stale ruby row from release-versioning.md table

Only ruby-v2 exists in release-config.json; the ruby row was outdated.

Co-Authored-By: judah <jsklan.development@gmail.com>

* fix: include source version in propagated filename to prevent overwrites

When the source is released multiple times before the dependent,
each propagation now creates a unique file (e.g.
auto-propagated-from-rust-0.41.0.yml) so earlier higher-severity
entries are preserved.

Co-Authored-By: judah <jsklan.development@gmail.com>

---------

Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
… flattenRequestParameters (#16426)

* test(ts-sdk): add exhaustive fixture case demonstrating array body with headers bug

When flattenRequestParameters=true with a root-level array request body
and header parameters, the generated code uses spread destructuring
(`..._body`) instead of named binding (`body: _body`), wrapping the
array in an object.

Co-Authored-By: judah <jsklan.development@gmail.com>

* fix(typescript): handle non-flattenable reference bodies in hasBodyProperty

When flattenRequestParameters=true, only named object types can actually
be flattened into individual properties on the request wrapper. Non-named
types (e.g., list<string>, map<string, string>) get wrapped in a body
property and must use named binding (body: _body) instead of spread
(..._body) during destructuring.

Co-Authored-By: judah <jsklan.development@gmail.com>

* test(typescript): update exhaustive fixture output after fix

All exhaustive fixtures regenerated with the postWithArrayBodyAndHeaders
endpoint. The flatten-request-parameters fixture now correctly generates
named binding (body: _body) instead of spread destructuring (..._body).

Co-Authored-By: judah <jsklan.development@gmail.com>

* chore: lint fix

Co-Authored-By: judah <jsklan.development@gmail.com>

* chore: escape angle brackets in changelog summary

Co-Authored-By: judah <jsklan.development@gmail.com>

* fix(typescript): handle named non-object reference bodies and update IR snapshots

Also fix getFlattenedReferencedRequestBodyProperties to add body property
for named non-object types (enums, unions, aliases), matching hasBodyProperty
behavior. Regenerate exhaustive.json IR test definitions.

Co-Authored-By: judah <jsklan.development@gmail.com>

---------

Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
@pull pull Bot locked and limited conversation to collaborators Jun 12, 2026
@pull pull Bot added the ⤵️ pull label Jun 12, 2026
@pull pull Bot merged commit d03170a into code:main Jun 12, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant