Skip to content

Update changelogs from fern repo #6300

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
thesandlord merged 1 commit into from
Jul 16, 2026
Merged

Update changelogs from fern repo #6300

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 12 additions & 6 deletions fern/products/sdks/generators/csharp/changelog/2026-07-16.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,10 +1,16 @@
## 2.76.3
**`(fix):`** The README "Environments" usage example now passes the client options via the
`clientOptions:` named argument so the generated snippet compiles. The root
client constructor's first positional parameter is the auth token string, so
the previous `new Client(new ClientOptions { ... })` snippet passed
`ClientOptions` where a `string?` token was expected.


## 2.76.2
**`(fix):`** A generated nested type whose name matches the SDK's root namespace segment (e.g.
a union variant `acme` that produces a nested `Acme` struct inside
`ConnectionResponse` in the `Acme.Api` namespace) now emits `global::`-qualified
references. Previously such a nested type shadowed the namespace root within its
enclosing type's body, so references like `Acme.Api.SomeType` resolved to the
nested type and failed to compile with CS0426. The `global::` qualifier is applied
**`(fix):`** A generated nested type whose name matches the SDK's root namespace segment now emits
`global::`-qualified references. Previously such a nested type shadowed the namespace
root within its enclosing type's body, so references like `Acme.Api.SomeType` resolved to the
nested type and failed to compile. The `global::` qualifier is applied
only to references written inside the enclosing type where the shadow is visible, so
unrelated references to the same root segment elsewhere in the SDK are left
unqualified.
Expand Down
Loading