Semantic Kernel dotnet-1.80.0 リリースSemantic Kernel dotnet-1.80.0
匿名の公開いいねです。記事の保存・お気に入りではなく、Featured、Top 3、重要度、掲載順位には影響しません。仕組みとプライバシーAnonymous public likes are reactions, not saved articles or bookmarks. They do not affect Featured, Top 3, importance, or listing order.How it works and privacy
dotnet-1.80.0では、OpenAPI HTTPクライアントのデフォルト設定更新、GeminiコネクタでのFunctionChoiceBehavior関数リストの適用修正などが含まれる。
Semantic Kernel dotnet-1.80.0 ships with updated OpenAPI HTTP client defaults, a fix for FunctionChoiceBehavior function list handling in the Gemini connector, and bumped Testcontainers packages.
本ページの本文と要約は AI による自動生成です。日本語版と英語版は言語ごとに独立して生成されるため、表現や詳しさが異なる場合があります。正確性は元記事 (github.com) をご確認ください。The body and summaries are AI-generated independently for each language, so wording and detail may differ. Verify accuracy at the original source (github.com).
要約と収集メタデータに基づく AI 解説。元記事全文の転載・翻訳ではありません。AI explainer based on the summaries and collected metadata, not a copy or translation of the full source article.
マイクロソフトが主導するオープンソースのAIオーケストレーションSDK「Semantic Kernel」の.NET版が、バージョン1.80.0として公開された。今回の更新は大規模な機能追加よりも、既存コネクタの挙動修正や外部連携まわりの調整を中心とした、実運用の安定性を高める内容が並ぶ。
Semantic Kernelは、大規模言語モデル(LLM)をアプリケーションに組み込み、プロンプトや関数呼び出し、プラグインを一貫した枠組みで扱うためのフレームワークで、エージェント開発の基盤として位置づけられている。OpenAIやAzure OpenAI、Google Geminiなど複数のモデルプロバイダーに対応する点が特徴で、今回の変更もその複数対応を支える部分に及んでいる。
注目点の一つは、Geminiコネクタにおける「FunctionChoiceBehavior」の関数リストが正しく尊重されるよう修正された点だ。FunctionChoiceBehaviorは、モデルがどの関数(ツール)を呼び出せるかを制御する仕組みで、開発者が指定した関数の一覧が期待どおり適用されることは、意図しないツール呼び出しを避けるうえで重要となる。従来はこの指定がGemini側で十分に反映されていなかった可能性があり、今回の修正で他プロバイダーとの挙動の一貫性が改善されると見られる。
また、OpenAPIプラグイン向けのHTTPクライアントの既定設定が更新された。Semantic KernelはOpenAPI仕様を読み込んで外部APIを関数として呼び出せるため、その通信基盤の既定値の見直しは、API連携を多用するエージェントに影響し得る。加えて、統合テストで用いられるTestcontainers関連パッケージのバージョン引き上げも行われ、テスト環境の追随が図られている。
全体として今回のリリースは、派手な新機能というよりも、マルチプロバイダー対応と外部連携の信頼性を積み上げる保守的な更新と言える。エージェントフレームワークをめぐる競争が活発化するなか、細部の整合性を継続的に整える動きは、実装者にとって見逃せないだろう。
Microsoft's Semantic Kernel team has published version 1.80.0 of its .NET SDK, a maintenance-focused release that refines how the framework handles OpenAPI-based plugins and function selection with Google's Gemini models. For developers building AI agents on .NET, the update tightens two integration points that matter for tool calling and external API access, alongside routine dependency housekeeping.
Semantic Kernel is Microsoft's open-source SDK for embedding large language models into applications and orchestrating agents that can call functions, query data, and invoke external services. Distributed across .NET, Python, and Java, it sits in a crowded field of agent frameworks that includes LangChain, LlamaIndex, and Microsoft's own AutoGen, which the company has been gradually converging with Semantic Kernel. The .NET line is versioned separately and ships frequent incremental releases, and 1.80.0 continues that cadence.
The most notable behavioral change addresses the Gemini connector. According to the release notes, the update makes the connector honor the FunctionChoiceBehavior function list. FunctionChoiceBehavior is Semantic Kernel's mechanism for controlling how a model decides which functions, or tools, to invoke during a completion — for example, letting the model choose automatically, requiring a specific call, or disabling function calls entirely. The behavior can also be scoped to an explicit subset of functions. The fix appears to ensure that when a developer supplies such a list, the Gemini connector actually restricts the advertised functions to that set rather than exposing others. This is the kind of correctness fix that matters when agents are wired to many plugins but should only reach for a narrow selection in a given step.
The release also updates the default configuration for the OpenAPI HTTP client. Semantic Kernel lets developers import an OpenAPI specification and expose its operations to a model as callable functions, turning existing REST APIs into agent tools without hand-writing wrappers. Changes to the HTTP client defaults — such as headers, timeouts, or handler configuration — can influence how those generated calls behave in production, though the release summary does not enumerate the specific values. Teams that rely heavily on OpenAPI plugins may want to review the change to confirm it aligns with their expectations.
Rounding out the release, the maintainers bumped the Testcontainers packages used in the project's test suite. Testcontainers is a widely used library for running disposable Docker containers during integration tests, and keeping it current is standard maintenance that helps ensure the framework's tests run against supported dependency versions. The package version itself was raised to 1.80.0 as part of the release process, and the commit history indicates additional dependency bumps beyond those detailed here.
For context, function calling — sometimes called tool use — has become a central capability of modern agent frameworks, and provider-specific connectors each translate a shared abstraction into the underlying API's format. Because Gemini, OpenAI, Azure OpenAI, and other backends expose function calling differently, connector-level fixes like this one are common as the framework works to keep behavior consistent across providers. FunctionChoiceBehavior itself is the newer, unified API that Semantic Kernel introduced to replace earlier provider-specific tool-calling settings, so bringing the Gemini connector fully in line with it is a step toward cross-provider parity rather than a new feature.
Adjacent to these connector concerns, OpenAPI import remains one of the more practical ways to extend an agent's reach, since it lets organizations reuse APIs they already document and operate. Combined with the framework's plugin model, it allows a single agent to blend native code functions, remote services, and model-driven planning. Adjustments to the HTTP client that carries those requests are therefore relevant to reliability, even when they are not headline-grabbing.
Developers can obtain the update through NuGet, where Semantic Kernel's packages are published, and the full commit list is available on the project's GitHub releases page. As with prior point releases, 1.80.0 appears aimed at stability and incremental refinement rather than major new capabilities, and most applications should be able to adopt it with minimal changes. Those using the Gemini connector with scoped function lists, or leaning on OpenAPI-derived plugins, are the most likely to notice a direct difference in behavior after upgrading.
ポコとTECHガイドPoko & TECH Guide
ポコと当サイトのTECHガイドが、記事の要約と収集した情報から読みどころを語るAI生成の対話です。Poko and TECH Dashboard's own TECH Guide discuss the article's highlights in an AI-generated conversation based on its summary and collected source details.
- ポコPokoOpenAPI HTTPクライアントのデフォルト設定更新って、つまりどういうこと?What does “updated OpenAPI HTTP client defaults” actually mean?
- TECHガイドTECH Guide簡単に言うと、OpenAPIに沿って通信する仕組みの初期設定が変わったということじゃな。記事には変更の詳細までは書かれておらんよ。Simply put, the initial settings for making requests through OpenAPI changed. The article doesn’t specify exactly which defaults were updated.
- ポコPokoなるほど。それと、Geminiコネクタの関数リスト修正は何が嬉しいの?Got it. So what’s useful about the Gemini connector’s function-list fix?
- TECHガイドTECH Guide記事によれば、FunctionChoiceBehaviorで指定した関数リストがGeminiコネクタで反映されるよう修正されたんじゃ。意図した関数指定を扱える、ということじゃな。According to the article, the Gemini connector now honors the function list specified through FunctionChoiceBehavior. In plain terms, the intended function selection is properly applied.
- ポコPokoつまり、通信の初期設定が更新されて、Geminiの関数指定も正しく扱われるようになったんだね。Testcontainersも更新、と。So the request defaults changed, Gemini function selection is now handled as intended, and the Testcontainers packages were updated too.
- TECHガイドTECH Guideその理解でよいぞ。既定値が変わっているので、利用するならOpenAPI HTTPクライアントの変更点は確認しておきたいところじゃな。That’s right. Since the defaults changed, it’s worth checking the OpenAPI HTTP client changes when adopting this release.