Skip to content

chore: release main#112

Open
stainless-app[bot] wants to merge 46 commits intomainfrom
release-please--branches--main--changes--next
Open

chore: release main#112
stainless-app[bot] wants to merge 46 commits intomainfrom
release-please--branches--main--changes--next

Conversation

@stainless-app
Copy link
Contributor

@stainless-app stainless-app bot commented Feb 5, 2026

✨ Stainless prepared a new release

Anthropic: 12.5.0

12.5.0 (2026-02-09)

Full Changelog: Anthropic-v12.4.0...Anthropic-v12.5.0

Features

  • api: enabling fast-mode in claude-opus-4-6 (49302d9)
  • client: streaming aggregators (#105) (2f17663)

Bug Fixes

  • client: handle edge case with renamed variable (ec8b153)
Foundry: 0.4.3

0.4.3 (2026-02-09)

Full Changelog: Foundry-v0.4.2...Foundry-v0.4.3


This pull request is managed by Stainless's GitHub App.

The semver version number is based on included commit messages. Alternatively, you can manually set the version number in the title of this pull request.

For a better experience, it is recommended to use either rebase-merge or squash-merge when merging this pull request.

🔗 Stainless website
📚 Read the docs
🙋 Reach out for help or questions

stainless-app bot and others added 30 commits January 14, 2026 20:29
* Changes from PR 55

* Lint fix

* fix: replace deprecated Assert.IsAssignableFrom with Assert.IsType
* fix: use Properties initializer for InputSchema in IChatClient extensions (#83)

* chore(ci): Add Claude Code GitHub Workflow (#273)

* "Claude PR Assistant workflow"

* "Claude Code Review workflow"

* fix: use Properties initializer for InputSchema in IChatClient extensions

The InputSchema constructor was being passed properties as rawData,
which caused them to be serialized at the top level of the JSON object
instead of under a "properties" key. This resulted in invalid JSON Schema
that failed Anthropic API validation with error:
"tools.0.custom.input_schema: JSON schema is invalid"

The fix uses property initializer syntax to correctly populate the
Properties property, ensuring the schema is valid JSON Schema draft 2020-12.

Also updates tests to expect the corrected schema format.

Fixes #82

* Remove added workflows

---------

Co-authored-by: dtmeadows <dmeadows@stainless.com>

* Add MEAI User-Agent for IChatClient implementation

* Fix failing UT for new schema properties pattern

* Add MEAI user agent + UT for betaservice

* Address PR comments

* Use FrozenDictionary for MEAI headers and fix User-Agent test assertions

* Add missing System.Linq using for ToArray extension method

* Fix User-Agent tests to verify single header with multiple values

* Fix lint issues: use collection expressions and simplify regex

---------

Co-authored-by: Matt Brailsford <me@mattbrailsford.com>
Co-authored-by: dtmeadows <dmeadows@stainless.com>
Co-authored-by: Claude Code (/Users/davidmeadows/stainless/stainless) <noreply@anthropic.com>
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch 2 times, most recently from a37567f to db823be Compare February 6, 2026 05:28
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from db823be to 28a9a73 Compare February 6, 2026 22:11
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch 2 times, most recently from 82f1cb3 to 1ac1fde Compare February 6, 2026 22:21
@sciutand
Copy link
Contributor

sciutand commented Feb 6, 2026

FYI v12.4 failed to deploy https://github.com/anthropics/anthropic-sdk-csharp/actions/runs/21724467969/job/62662729880 . Nuget is still on v12.3

@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from 1ac1fde to 9b658e4 Compare February 6, 2026 22:46
@sd-st
Copy link
Collaborator

sd-st commented Feb 6, 2026

Thanks, I just kicked it (:

* Add vertex provider
Add vertex example

Add explicit body check for vertex

Readd explicit check for model value in bedrock client

lint

reintroduce null forgiving operator as required by build

* apply review suggestions

* Update examples/MessagesExample.Vertex/Program.cs

* Apply suggestion from @sd-st

---------

Co-authored-by: Stephen <stephen@stainless.com>
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from 9b658e4 to 62036ab Compare February 6, 2026 23:31
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch 2 times, most recently from c9d15fd to 104dc86 Compare February 7, 2026 05:22
felixfbecker
felixfbecker previously approved these changes Feb 7, 2026
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from 104dc86 to b117c68 Compare February 7, 2026 17:47
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from b117c68 to f1b5d59 Compare February 7, 2026 20:56
felixfbecker
felixfbecker previously approved these changes Feb 7, 2026
@felixfbecker felixfbecker self-requested a review February 7, 2026 21:02
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from f1b5d59 to 182f121 Compare February 8, 2026 05:33
@sciutand
Copy link
Contributor

sciutand commented Feb 8, 2026

Thanks, I just kicked it (:

Thanks.. I just checked but it still didn't deploy correctly. Looking at the code of the action and the response something's gone bad. No release have been created and subsequent steps were skipped.

code needs releases

if (data?.releases?.length) {
    core.setOutput('releases_created', true);
    outputReleases(data.releases);
  }

response.data has no releases

API Response {
  message: 'Successfully updated/created 1 Release PR(s)',
  releases: [],
  pullRequests: [

@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from 182f121 to ffb8ebd Compare February 9, 2026 05:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants