<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Bumplog — is it safe to update Headscale?</title>
    <link>https://bumplog.org/apps/headscale/</link>
    <description>Update-safety verdicts for Headscale (juanfont/headscale), traceable to the GitHub release.</description>
    <language>en</language>
    <atom:link href="https://bumplog.org/apps/headscale/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Headscale v0.29.2 — Safe to update</title>
      <link>https://bumplog.org/apps/headscale/</link>
      <guid isPermaLink="false">bumplog:app:headscale:v0.29.2:safe</guid>
      <pubDate>Fri, 24 Jul 2026 00:00:00 GMT</pubDate>
      <description>Safe to update. The release notes describe only bug fixes with no breaking changes, required migrations, or configuration changes. The standard upgrade guide is referenced, but no manual steps specific to v0.29.2 are called out. What changed: v0.29.2 is a bug-fix release addressing three reliability issues. A concurrency fix prevents mass-reconnect storms (triggered by autogroup:self, via, or relay policies) from serializing on the policy lock and stalling clients with &apos;unexpected EOF&apos; errors. The /ts2021 endpoint now correctly accepts WebSocket GET upgrade requests, restoring connectivity for Tailscale JS/WASM control clients that were previously rejected with a 405. Nodes with invalid FQDNs (empty or exceeding the hostname length limit) are now skipped gracefully during map delivery rather than causing failures, with offending names logged at startup. Source release: https://github.com/juanfont/headscale/releases/tag/v0.29.2</description>
    </item>
  </channel>
</rss>
