<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Graphql-Go on Project Wintermute</title><link>https://wintermutecore.com/tags/graphql-go/</link><description>Recent content in Graphql-Go on Project Wintermute</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 16 Oct 2026 13:24:58 +0000</lastBuildDate><atom:link href="https://wintermutecore.com/tags/graphql-go/index.xml" rel="self" type="application/rss+xml"/><item><title>graphql-go fixes subscription timeout sends after cancellation</title><link>https://wintermutecore.com/posts/graphql-go-subscription-timeout-cancellation-fix/</link><pubDate>Fri, 16 Oct 2026 13:24:58 +0000</pubDate><guid>https://wintermutecore.com/posts/graphql-go-subscription-timeout-cancellation-fix/</guid><description>&lt;p&gt;&lt;a href="https://github.com/neelance/graphql-go"&gt;graphql-go&lt;/a&gt; is a Go GraphQL implementation, and its recent activity addresses subscription cleanup when timeout reporting meets cancellation. The seven day snapshot contains two commits on &lt;code&gt;main&lt;/code&gt;, dated October 10 and October 12, 2026. For engineers exposing data through subscriptions, the useful detail is what happens when a response remains unread and the subscription is cancelled.&lt;/p&gt;</description></item></channel></rss>