<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Releases on Go Micro</title><link>https://go-micro.dev/blog/releases/index.html</link><description>Recent content in Releases on Go Micro</description><generator>Hugo</generator><language>en</language><atom:link href="https://go-micro.dev/blog/releases/index.xml" rel="self" type="application/rss+xml"/><item><title>What's New in Go Micro: v6.6.0</title><link>https://go-micro.dev/blog/2026/07/11/v6-6-0.html</link><pubDate>Sat, 11 Jul 2026 00:00:00 +0000</pubDate><guid>https://go-micro.dev/blog/2026/07/11/v6-6-0.html</guid><description>&lt;p&gt;Go Micro v6.6.0 is a harness reliability release. The theme is the same services → agents → workflows lifecycle, but with more of the first-agent path covered by local checks and more recovery paths made deterministic when agents resume, retry, delegate, or notify.&lt;/p&gt;
&lt;h2 id="the-first-agent-path-is-harder-to-break"&gt;The first-agent path is harder to break&lt;a class="td-heading-self-link" href="#the-first-agent-path-is-harder-to-break" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;The README, website docs, examples, and 0→hero guide chain now have more harness coverage. The CLI and docs keep the path from install troubleshooting through &lt;code&gt;micro agent demo&lt;/code&gt;, quickcheck, examples, the smallest first-agent, debugging, and 0→hero in one consistent order.&lt;/p&gt;</description></item><item><title>What's New in Go Micro: v6.3.15</title><link>https://go-micro.dev/blog/2026/07/05/v6-3-15.html</link><pubDate>Sun, 05 Jul 2026 00:00:00 +0000</pubDate><guid>https://go-micro.dev/blog/2026/07/05/v6-3-15.html</guid><description>&lt;p&gt;Go Micro v6.3.15 is a small but useful harness release: less friction for the first agent, better streaming provider coverage, and more reliable execution when models and delegates do not behave perfectly.&lt;/p&gt;
&lt;h2 id="anthropic-now-streams"&gt;Anthropic now streams&lt;a class="td-heading-self-link" href="#anthropic-now-streams" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;The Anthropic provider now supports Messages SSE streaming and is registered as a streaming-capable provider. That means Go Micro agents can use Anthropic in the same streaming path as the other streaming-capable providers, with request/response parser coverage and provider capability docs kept in sync.&lt;/p&gt;</description></item><item><title>What's New in Go Micro: v5.15.0</title><link>https://go-micro.dev/blog/2026/02/11/v5-15-0.html</link><pubDate>Wed, 11 Feb 2026 00:00:00 +0000</pubDate><guid>https://go-micro.dev/blog/2026/02/11/v5-15-0.html</guid><description>&lt;h2 id="making-microservices-ai-native-with-mcp"&gt;Making Microservices AI-Native with MCP&lt;a class="td-heading-self-link" href="#making-microservices-ai-native-with-mcp" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;h3 id="the-vision"&gt;The Vision&lt;a class="td-heading-self-link" href="#the-vision" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;Imagine telling Claude: &lt;em&gt;&amp;ldquo;Why is user 123&amp;rsquo;s order stuck?&amp;rdquo;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Claude responds by:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Calling your &lt;code&gt;users&lt;/code&gt; service to check the account&lt;/li&gt;
&lt;li&gt;Calling your &lt;code&gt;orders&lt;/code&gt; service to inspect the order&lt;/li&gt;
&lt;li&gt;Calling your &lt;code&gt;payments&lt;/code&gt; service to verify the transaction&lt;/li&gt;
&lt;li&gt;Giving you a complete diagnosis&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;strong&gt;No API wrappers. No manual integrations. Your services just work with AI.&lt;/strong&gt;&lt;/p&gt;
&lt;h3 id="what-is-mcp"&gt;What is MCP?&lt;a class="td-heading-self-link" href="#what-is-mcp" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;&lt;a href="https://modelcontextprotocol.io"&gt;Model Context Protocol&lt;/a&gt; is Anthropic&amp;rsquo;s open standard for connecting AI models to external tools. Think of it like a microservices registry, but for AI.&lt;/p&gt;</description></item><item><title>What's New in Go Micro: v5.13.0</title><link>https://go-micro.dev/blog/2026/01/27/v5-13-0.html</link><pubDate>Tue, 27 Jan 2026 00:00:00 +0000</pubDate><guid>https://go-micro.dev/blog/2026/01/27/v5-13-0.html</guid><description>&lt;h2 id="the-problem"&gt;The Problem&lt;a class="td-heading-self-link" href="#the-problem" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Go Micro has always been great for building microservices:&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;micro new myservice
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nb"&gt;cd&lt;/span&gt; myservice
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;micro run
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;But getting those services to production? That was on you. You&amp;rsquo;d need to figure out Docker, Kubernetes, or write your own deployment scripts.&lt;/p&gt;
&lt;p&gt;We tried to solve this with Micro v3 — a full platform-as-a-service. But it was too much. Too complex. Nobody wanted another platform to manage.&lt;/p&gt;
&lt;h2 id="the-solution"&gt;The Solution&lt;a class="td-heading-self-link" href="#the-solution" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;The new approach is simple: &lt;strong&gt;systemd + SSH&lt;/strong&gt;.&lt;/p&gt;</description></item></channel></rss>