<?xml version='1.0' encoding='utf-8'?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:ore="urn:ore-news:provenance">
  <id>urn:ore-news:feed:primary</id>
  <title>ore-news canonical feed</title>
  <updated>2026-11-21T05:38:01Z</updated>
  <generator uri="https://github.com/rbcn2000/ore-news">ore-news</generator>
  <author>
    <name>ore-news</name>
  </author>
  <entry>
    <id>urn:ore-news:event:hacker-news:49aa17782ef1ea7f23effb7d293c0702</id>
    <title>ClawDOS – An AI coding agent for DOS</title>
    <updated>2026-11-21T05:38:01Z</updated>
    <published>2026-11-21T05:38:01Z</published>
    <link rel="alternate" href="http://ricapar.net/ClawDOS/" />
    <link rel="via" href="https://news.ycombinator.com/rss" />
    <category scheme="urn:ore-news:sources" term="hacker-news" label="Hacker News" />
    <author>
      <name>Hacker News</name>
    </author>
    <source>
      <id>urn:ore-news:source:hacker-news</id>
      <title>Hacker News</title>
      <link rel="alternate" href="https://news.ycombinator.com/" />
      <link rel="via" href="https://news.ycombinator.com/rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hacker-news</ore:sourceId>
      <ore:sourceName>Hacker News</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://news.ycombinator.com/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://news.ycombinator.com/rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>http://ricapar.net/ClawDOS/</ore:originalUrl>
      <ore:upstreamId>http://ricapar.net/ClawDOS/</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hatena-bookmark-technology:d55458f02682197d48437956da3ec01d</id>
    <title>みずほ銀行のシステムがハッキングされないの、開発者だけじゃなくてハッカーも仕様を把握できないから説「妙な説得力あるな」「ハッキングが先か、障害が先か…」</title>
    <updated>2026-11-21T04:00:58Z</updated>
    <published>2026-11-21T04:00:58Z</published>
    <link rel="alternate" href="https://togetter.com/li/2773158" />
    <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    <category scheme="urn:ore-news:sources" term="hatena-bookmark-technology" label="Hatena Bookmark Technology" />
    <author>
      <name>Hatena Bookmark Technology</name>
    </author>
    <source>
      <id>urn:ore-news:source:hatena-bookmark-technology</id>
      <title>Hatena Bookmark Technology</title>
      <link rel="alternate" href="https://b.hatena.ne.jp/hotentry/it" />
      <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hatena-bookmark-technology</ore:sourceId>
      <ore:sourceName>Hatena Bookmark Technology</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://b.hatena.ne.jp/hotentry/it</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://b.hatena.ne.jp/hotentry/it.rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://togetter.com/li/2773158</ore:originalUrl>
      <ore:upstreamId>https://togetter.com/li/2773158</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hacker-news:b44d4fa4e451274879cd22a320fcf926</id>
    <title>Backblaze Notice at Collection and Privacy Policy</title>
    <updated>2026-11-21T03:23:16Z</updated>
    <published>2026-11-21T03:23:16Z</published>
    <link rel="alternate" href="https://www.backblaze.com/company/policy/privacy" />
    <link rel="via" href="https://news.ycombinator.com/rss" />
    <category scheme="urn:ore-news:sources" term="hacker-news" label="Hacker News" />
    <author>
      <name>Hacker News</name>
    </author>
    <source>
      <id>urn:ore-news:source:hacker-news</id>
      <title>Hacker News</title>
      <link rel="alternate" href="https://news.ycombinator.com/" />
      <link rel="via" href="https://news.ycombinator.com/rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hacker-news</ore:sourceId>
      <ore:sourceName>Hacker News</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://news.ycombinator.com/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://news.ycombinator.com/rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://www.backblaze.com/company/policy/privacy</ore:originalUrl>
      <ore:upstreamId>https://www.backblaze.com/company/policy/privacy</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hatena-bookmark-technology:fe21923e89a545ae7b6755a1e1d7f706</id>
    <title>イーロン・マスクが金持ちでもそんなネットで嫌われてないのって「男の子がワクワクするもの」に迷わず巨額の金を突っ込むからだと思うんだよな</title>
    <updated>2026-11-21T03:06:24Z</updated>
    <published>2026-11-21T03:06:24Z</published>
    <link rel="alternate" href="https://togetter.com/li/2773122" />
    <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    <category scheme="urn:ore-news:sources" term="hatena-bookmark-technology" label="Hatena Bookmark Technology" />
    <author>
      <name>Hatena Bookmark Technology</name>
    </author>
    <source>
      <id>urn:ore-news:source:hatena-bookmark-technology</id>
      <title>Hatena Bookmark Technology</title>
      <link rel="alternate" href="https://b.hatena.ne.jp/hotentry/it" />
      <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hatena-bookmark-technology</ore:sourceId>
      <ore:sourceName>Hatena Bookmark Technology</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://b.hatena.ne.jp/hotentry/it</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://b.hatena.ne.jp/hotentry/it.rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://togetter.com/li/2773122</ore:originalUrl>
      <ore:upstreamId>https://togetter.com/li/2773122</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hacker-news:6bb07f8ccfd54734885300c6f7147043</id>
    <title>Clojure will affect the way you think about programming (2017)</title>
    <updated>2026-11-21T02:40:39Z</updated>
    <published>2026-11-21T02:40:39Z</published>
    <link rel="alternate" href="https://eli.thegreenplace.net/2017/clojure-the-perfect-language-to-expand-your-brain/" />
    <link rel="via" href="https://news.ycombinator.com/rss" />
    <category scheme="urn:ore-news:sources" term="hacker-news" label="Hacker News" />
    <author>
      <name>Hacker News</name>
    </author>
    <source>
      <id>urn:ore-news:source:hacker-news</id>
      <title>Hacker News</title>
      <link rel="alternate" href="https://news.ycombinator.com/" />
      <link rel="via" href="https://news.ycombinator.com/rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hacker-news</ore:sourceId>
      <ore:sourceName>Hacker News</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://news.ycombinator.com/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://news.ycombinator.com/rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://eli.thegreenplace.net/2017/clojure-the-perfect-language-to-expand-your-brain/</ore:originalUrl>
      <ore:upstreamId>https://eli.thegreenplace.net/2017/clojure-the-perfect-language-to-expand-your-brain/</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hatena-bookmark-technology:fcdd74ba44aedcbd5bb699951c48a77d</id>
    <title>アンソロピック研究者、数学難問「リーマン予想」をAIで解決と発表 - 日本経済新聞</title>
    <updated>2026-11-21T02:33:27Z</updated>
    <published>2026-11-21T02:33:27Z</published>
    <link rel="alternate" href="https://www.nikkei.com/article/DGXZQOSG20CQC0Q6A121C2000000/" />
    <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    <category scheme="urn:ore-news:sources" term="hatena-bookmark-technology" label="Hatena Bookmark Technology" />
    <author>
      <name>Hatena Bookmark Technology</name>
    </author>
    <source>
      <id>urn:ore-news:source:hatena-bookmark-technology</id>
      <title>Hatena Bookmark Technology</title>
      <link rel="alternate" href="https://b.hatena.ne.jp/hotentry/it" />
      <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hatena-bookmark-technology</ore:sourceId>
      <ore:sourceName>Hatena Bookmark Technology</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://b.hatena.ne.jp/hotentry/it</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://b.hatena.ne.jp/hotentry/it.rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://www.nikkei.com/article/DGXZQOSG20CQC0Q6A121C2000000/</ore:originalUrl>
      <ore:upstreamId>https://www.nikkei.com/article/DGXZQOSG20CQC0Q6A121C2000000/</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hatena-bookmark-technology:036d7ecbf9ce63d878034be49d1cc62f</id>
    <title>ボールの慣性で素早いカーソル移動！奥深きトラックボールの世界 3つのスタイルに分けて計14モデルをピックアップ text by 石川 ひさよし</title>
    <updated>2026-11-21T01:24:02Z</updated>
    <published>2026-11-21T01:24:02Z</published>
    <link rel="alternate" href="https://akiba-pc.watch.impress.co.jp/docs/sale/online_shopping/2158378.html" />
    <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    <category scheme="urn:ore-news:sources" term="hatena-bookmark-technology" label="Hatena Bookmark Technology" />
    <author>
      <name>Hatena Bookmark Technology</name>
    </author>
    <source>
      <id>urn:ore-news:source:hatena-bookmark-technology</id>
      <title>Hatena Bookmark Technology</title>
      <link rel="alternate" href="https://b.hatena.ne.jp/hotentry/it" />
      <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hatena-bookmark-technology</ore:sourceId>
      <ore:sourceName>Hatena Bookmark Technology</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://b.hatena.ne.jp/hotentry/it</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://b.hatena.ne.jp/hotentry/it.rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://akiba-pc.watch.impress.co.jp/docs/sale/online_shopping/2158378.html</ore:originalUrl>
      <ore:upstreamId>https://akiba-pc.watch.impress.co.jp/docs/sale/online_shopping/2158378.html</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:d04f07c78018971fc1d367ee5c339c53</id>
    <title>Amazon CloudWatch Omni now supports Microsoft Azure platform logs, metrics and traces</title>
    <updated>2026-11-21T01:10:00Z</updated>
    <published>2026-11-21T01:10:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/amazon-cloudwatch-omni-microsoft-azure" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;Amazon CloudWatch Omni now supports collecting Azure resource logs, Azure Monitor platform metrics, virtual network (VNet) flow logs, and traces from Application Insights. Teams that run workloads on both AWS and Azure no longer need separate monitoring tools or custom pipelines to see their whole environment. Central operations, DevOps, and site reliability engineering (SRE) teams can now view Azure telemetry alongside their AWS telemetry in one place.&lt;/p&gt; 
&lt;p&gt;To get started, connect a Microsoft Entra ID tenant to your AWS account and Region. You can choose the telemetry types, subscriptions, Azure regions, resource types, and tags to collect. Azure telemetry lands in Amazon CloudWatch, and Omni spaces can monitor applications and infrastructure across cloud providers. For example, during an incident you can trace a slow request from an Azure-hosted service to its AWS dependencies without switching consoles. You can set up the connectors in the Amazon CloudWatch Omni console or with the AWS CLI.&lt;/p&gt; 
&lt;p&gt;Azure telemetry collection is available in all Azure Public Regions and can be ingested to all regions where CloudWatch Omni is available. To get started, visit the &amp;nbsp;&lt;a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/omni-send-platform-telemetry-from-microsoft-azure.html"&gt;CloudWatch Omni User Guide&amp;nbsp;&lt;/a&gt; and for pricing visit&amp;nbsp;&lt;a href="https://aws.amazon.com/cognito/pricing/"&gt;pricing page.&lt;/a&gt;&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/amazon-cloudwatch-omni-microsoft-azure</ore:originalUrl>
      <ore:upstreamId>5773cc6c5894dd48459d77d322ea3acbae675570</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hatena-bookmark-technology:61053df85e4047c97f1f0edc584ec1d9</id>
    <title>NVIDIAグラボにて発生していた「SSD無限酷使」不具合の修正バージョンが配信。“何もしてない”のにSSDに数十GB書き込まれていた問題 - AUTOMATON</title>
    <updated>2026-11-21T00:45:41Z</updated>
    <published>2026-11-21T00:45:41Z</published>
    <link rel="alternate" href="https://automaton-media.com/articles/newsjp/20261121-480255/" />
    <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    <category scheme="urn:ore-news:sources" term="hatena-bookmark-technology" label="Hatena Bookmark Technology" />
    <author>
      <name>Hatena Bookmark Technology</name>
    </author>
    <source>
      <id>urn:ore-news:source:hatena-bookmark-technology</id>
      <title>Hatena Bookmark Technology</title>
      <link rel="alternate" href="https://b.hatena.ne.jp/hotentry/it" />
      <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hatena-bookmark-technology</ore:sourceId>
      <ore:sourceName>Hatena Bookmark Technology</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://b.hatena.ne.jp/hotentry/it</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://b.hatena.ne.jp/hotentry/it.rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://automaton-media.com/articles/newsjp/20261121-480255/</ore:originalUrl>
      <ore:upstreamId>https://automaton-media.com/articles/newsjp/20261121-480255/</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hatena-bookmark-technology:b230e407e3c8e021b2c7b2ed47e9c5e1</id>
    <title>【分析】「私はMAGAではない」　マスク氏の方向転換が発する強烈なサイン</title>
    <updated>2026-11-21T00:39:32Z</updated>
    <published>2026-11-21T00:39:32Z</published>
    <link rel="alternate" href="https://www.cnn.co.jp/usa/35255243.html" />
    <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    <category scheme="urn:ore-news:sources" term="hatena-bookmark-technology" label="Hatena Bookmark Technology" />
    <author>
      <name>Hatena Bookmark Technology</name>
    </author>
    <source>
      <id>urn:ore-news:source:hatena-bookmark-technology</id>
      <title>Hatena Bookmark Technology</title>
      <link rel="alternate" href="https://b.hatena.ne.jp/hotentry/it" />
      <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hatena-bookmark-technology</ore:sourceId>
      <ore:sourceName>Hatena Bookmark Technology</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://b.hatena.ne.jp/hotentry/it</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://b.hatena.ne.jp/hotentry/it.rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://www.cnn.co.jp/usa/35255243.html</ore:originalUrl>
      <ore:upstreamId>https://www.cnn.co.jp/usa/35255243.html</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hatena-bookmark-technology:f7e2f56c6688868cf8854c055c4d92a4</id>
    <title>ソフトウェアファクトリーとコード設計と顧客価値</title>
    <updated>2026-11-21T00:35:47Z</updated>
    <published>2026-11-21T00:35:47Z</published>
    <link rel="alternate" href="https://kosui.me/posts/2026/11/15/code-design-after-agents" />
    <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    <category scheme="urn:ore-news:sources" term="hatena-bookmark-technology" label="Hatena Bookmark Technology" />
    <author>
      <name>Hatena Bookmark Technology</name>
    </author>
    <source>
      <id>urn:ore-news:source:hatena-bookmark-technology</id>
      <title>Hatena Bookmark Technology</title>
      <link rel="alternate" href="https://b.hatena.ne.jp/hotentry/it" />
      <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hatena-bookmark-technology</ore:sourceId>
      <ore:sourceName>Hatena Bookmark Technology</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://b.hatena.ne.jp/hotentry/it</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://b.hatena.ne.jp/hotentry/it.rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://kosui.me/posts/2026/11/15/code-design-after-agents</ore:originalUrl>
      <ore:upstreamId>https://kosui.me/posts/2026/11/15/code-design-after-agents</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hacker-news:23701602ebc4ef8e826a753a163e2072</id>
    <title>I Don't Trust Visual Recordings Anymore. But One Day I Will Again</title>
    <updated>2026-11-21T00:33:40Z</updated>
    <published>2026-11-21T00:33:40Z</published>
    <link rel="alternate" href="https://spectrum.ieee.org/fighting-back-against-deep-fakes" />
    <link rel="via" href="https://news.ycombinator.com/rss" />
    <category scheme="urn:ore-news:sources" term="hacker-news" label="Hacker News" />
    <author>
      <name>Hacker News</name>
    </author>
    <source>
      <id>urn:ore-news:source:hacker-news</id>
      <title>Hacker News</title>
      <link rel="alternate" href="https://news.ycombinator.com/" />
      <link rel="via" href="https://news.ycombinator.com/rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hacker-news</ore:sourceId>
      <ore:sourceName>Hacker News</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://news.ycombinator.com/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://news.ycombinator.com/rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://spectrum.ieee.org/fighting-back-against-deep-fakes</ore:originalUrl>
      <ore:upstreamId>https://spectrum.ieee.org/fighting-back-against-deep-fakes</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:2a769565ca21d0559bd51fdff16067a0</id>
    <title>Web Search on Amazon Bedrock expands language support and country-aware search</title>
    <updated>2026-11-21T00:17:00Z</updated>
    <published>2026-11-21T00:17:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/web-search-amazon-bedrock/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;Web Search on Amazon Bedrock, the tool that grounds AI agents and applications in cited, current web information, now supports five new languages, plus non-US English, on Amazon Bedrock AgentCore and Amazon Bedrock: Spanish, French, German, Italian, and Japanese.&amp;nbsp; Agents serving users in these languages get results that draw on local-language sources.&lt;/p&gt; 
&lt;p&gt;We are also introducing a new optional country field that biases results toward sources from a specific country - just pass an ISO 3166-1 alpha-2 country code, such as “JP” or “DE”. This is useful for agents that serve users in multiple countries, for questions whose answer depends on the user's actual or preferred location (e.g., local regulations, prices or public officials), and for surfacing regional sources.&lt;/p&gt; 
&lt;p&gt;Both the expanded language support and the optional&amp;nbsp; country field are available today in every Region where Web Search is offered: US East (N. Virginia), US East (Ohio), US West (Oregon), Asia Pacific (Sydney), Asia Pacific (Tokyo), Europe (Ireland) and Europe (Frankfurt) for Web Search on Amazon Bedrock AgentCore, and US Regions for Web Search on Amazon Bedrock. Queries are processed in the Region you call, helping organizations meet data residency requirements. Existing customers get the new language capabilities automatically, with no code changes, and pricing is the same in every language.&amp;nbsp;&lt;/p&gt; 
&lt;p&gt;To get started with Web Search on Amazon Bedrock, checkout the developer &lt;a href="https://docs.aws.amazon.com/bedrock/latest/userguide/web-search.html#:~:text=User%20location,time%20zone%20identifier"&gt;guide&lt;/a&gt; and the web search product &lt;a href="https://aws.amazon.com/bedrock/grounding/web-search/"&gt;page&lt;/a&gt;.&amp;nbsp;&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/web-search-amazon-bedrock/</ore:originalUrl>
      <ore:upstreamId>e0fc98ef66b4cecc5a95d98917bfb19e3c0c5175</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hacker-news:5aed72aa6361c6de76da4bef2d3135f4</id>
    <title>Serious cyberattack thought backed by wealthy operators</title>
    <updated>2026-11-20T23:29:30Z</updated>
    <published>2026-11-20T23:29:30Z</published>
    <link rel="alternate" href="https://www.ruv.is/english/2026-11-20-serious-cyberattack-thought-backed-by-wealthy-operators-493411" />
    <link rel="via" href="https://news.ycombinator.com/rss" />
    <category scheme="urn:ore-news:sources" term="hacker-news" label="Hacker News" />
    <author>
      <name>Hacker News</name>
    </author>
    <source>
      <id>urn:ore-news:source:hacker-news</id>
      <title>Hacker News</title>
      <link rel="alternate" href="https://news.ycombinator.com/" />
      <link rel="via" href="https://news.ycombinator.com/rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hacker-news</ore:sourceId>
      <ore:sourceName>Hacker News</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://news.ycombinator.com/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://news.ycombinator.com/rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://www.ruv.is/english/2026-11-20-serious-cyberattack-thought-backed-by-wealthy-operators-493411</ore:originalUrl>
      <ore:upstreamId>https://www.ruv.is/english/2026-11-20-serious-cyberattack-thought-backed-by-wealthy-operators-493411</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hacker-news:e731726b5912b0f0d01ed699b9906548</id>
    <title>Sir Brian May adds new dimension to Hera asteroid</title>
    <updated>2026-11-20T23:19:44Z</updated>
    <published>2026-11-20T23:19:44Z</published>
    <link rel="alternate" href="https://www.esa.int/articles/about-us/directorates/operations/space-safety/hera/sir-brian-may-adds-new-dimension-to-hera-asteroid" />
    <link rel="via" href="https://news.ycombinator.com/rss" />
    <category scheme="urn:ore-news:sources" term="hacker-news" label="Hacker News" />
    <author>
      <name>Hacker News</name>
    </author>
    <source>
      <id>urn:ore-news:source:hacker-news</id>
      <title>Hacker News</title>
      <link rel="alternate" href="https://news.ycombinator.com/" />
      <link rel="via" href="https://news.ycombinator.com/rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hacker-news</ore:sourceId>
      <ore:sourceName>Hacker News</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://news.ycombinator.com/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://news.ycombinator.com/rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://www.esa.int/articles/about-us/directorates/operations/space-safety/hera/sir-brian-may-adds-new-dimension-to-hera-asteroid</ore:originalUrl>
      <ore:upstreamId>https://www.esa.int/articles/about-us/directorates/operations/space-safety/hera/sir-brian-may-adds-new-dimension-to-hera-asteroid</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hacker-news:946359f3c466ff6909dc0ba10ebcbc8f</id>
    <title>Ask HN: I have been unemployed for 2y. 15 years of experience, US. What to do?</title>
    <updated>2026-11-20T23:18:32Z</updated>
    <published>2026-11-20T23:18:32Z</published>
    <link rel="alternate" href="https://news.ycombinator.com/item?id=50583761" />
    <link rel="via" href="https://news.ycombinator.com/rss" />
    <category scheme="urn:ore-news:sources" term="hacker-news" label="Hacker News" />
    <author>
      <name>Hacker News</name>
    </author>
    <source>
      <id>urn:ore-news:source:hacker-news</id>
      <title>Hacker News</title>
      <link rel="alternate" href="https://news.ycombinator.com/" />
      <link rel="via" href="https://news.ycombinator.com/rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hacker-news</ore:sourceId>
      <ore:sourceName>Hacker News</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://news.ycombinator.com/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://news.ycombinator.com/rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://news.ycombinator.com/item?id=50583761</ore:originalUrl>
      <ore:upstreamId>https://news.ycombinator.com/item?id=50583761</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hatena-bookmark-technology:5dd0904ce84dd89ca531e65f0ddac2ef</id>
    <title>GitHub - RustWTM/RustWTM: Windows task manager and resource governor written in Rust. Monitor processes, manage resource usage, and keep your PC responsive.</title>
    <updated>2026-11-20T23:11:42Z</updated>
    <published>2026-11-20T23:11:42Z</published>
    <link rel="alternate" href="https://github.com/RustWTM/RustWTM" />
    <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    <category scheme="urn:ore-news:sources" term="hatena-bookmark-technology" label="Hatena Bookmark Technology" />
    <author>
      <name>Hatena Bookmark Technology</name>
    </author>
    <source>
      <id>urn:ore-news:source:hatena-bookmark-technology</id>
      <title>Hatena Bookmark Technology</title>
      <link rel="alternate" href="https://b.hatena.ne.jp/hotentry/it" />
      <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hatena-bookmark-technology</ore:sourceId>
      <ore:sourceName>Hatena Bookmark Technology</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://b.hatena.ne.jp/hotentry/it</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://b.hatena.ne.jp/hotentry/it.rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://github.com/RustWTM/RustWTM</ore:originalUrl>
      <ore:upstreamId>https://github.com/RustWTM/RustWTM</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hatena-bookmark-technology:eaa2886c3023d38077478d5b42c9372a</id>
    <title>Claudeを使い「リーマン予想」を証明か　Anthropic数学者が発表　Lean検証も通過、数学界が精査へ</title>
    <updated>2026-11-20T23:02:01Z</updated>
    <published>2026-11-20T23:02:01Z</published>
    <link rel="alternate" href="https://japan.cnet.com/article/35255245/" />
    <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    <category scheme="urn:ore-news:sources" term="hatena-bookmark-technology" label="Hatena Bookmark Technology" />
    <author>
      <name>Hatena Bookmark Technology</name>
    </author>
    <source>
      <id>urn:ore-news:source:hatena-bookmark-technology</id>
      <title>Hatena Bookmark Technology</title>
      <link rel="alternate" href="https://b.hatena.ne.jp/hotentry/it" />
      <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hatena-bookmark-technology</ore:sourceId>
      <ore:sourceName>Hatena Bookmark Technology</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://b.hatena.ne.jp/hotentry/it</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://b.hatena.ne.jp/hotentry/it.rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://japan.cnet.com/article/35255245/</ore:originalUrl>
      <ore:upstreamId>https://japan.cnet.com/article/35255245/</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:21e32692e51aec69ace389e735ae3bab</id>
    <title>Amazon RDS for Oracle now supports Primary Endpoint</title>
    <updated>2026-11-20T22:54:00Z</updated>
    <published>2026-11-20T22:54:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/rds-oracle-primary-endpoint-v2/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;&lt;a href="https://aws.amazon.com/rds/oracle/"&gt;Amazon Relational Database Service (Amazon RDS) for Oracle&lt;/a&gt; now provides a Primary Endpoint, a DNS name that always resolves to the current primary DB instance in a replica configuration. When you switch over to an Oracle replica, Amazon RDS points the Primary Endpoint to the new primary DB instance, so you don't need to change your application connection strings. Previously, after each switchover, you had to update connection strings or DNS records to point to the new primary DB instance, which often required change approvals and coordination across teams.&lt;/p&gt; 
&lt;p&gt;With Primary Endpoint, you can run planned switchovers, such as disaster recovery drills, to replicas in the same AWS Region or to cross-Region replicas without changing your application configuration. If your applications connect through the Primary Endpoint, you don't need to update their connection strings after the switchover.&lt;/p&gt; 
&lt;p&gt;Every RDS for Oracle Enterprise Edition DB instance has a Primary Endpoint at no additional charge, and you don't have to create it. The Primary Endpoint is provided in addition to the instance endpoint, so your existing applications aren't affected.&lt;/p&gt; 
&lt;p&gt;Primary Endpoint is available in all commercial AWS Regions where Amazon RDS for Oracle is available. To learn more, see &lt;a href="https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/oracle-primary-endpoint.html" target="_blank" rel="noopener noreferrer"&gt;Using the Primary Endpoint for Amazon RDS for Oracle&lt;/a&gt; in the Amazon RDS User Guide.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/rds-oracle-primary-endpoint-v2/</ore:originalUrl>
      <ore:upstreamId>34ca12b0edf222dced19882c6e5df11e7aef2df3</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:a28eea9175dc5ec2148a90724755c5d0</id>
    <title>AWS Lambda now publishes Event Function state change events to Amazon EventBridge</title>
    <updated>2026-11-20T22:40:00Z</updated>
    <published>2026-11-20T22:40:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/aws-lambda-function-state-events/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;&lt;a href="https://aws.amazon.com/lambda/" target="_blank" rel="noopener noreferrer"&gt;AWS Lambda&lt;/a&gt;&amp;nbsp;now publishes Event Function state change events to &lt;a href="https://aws.amazon.com/eventbridge/" target="_blank" rel="noopener noreferrer"&gt;Amazon EventBridge&lt;/a&gt;. Lambda emits an event each time an Event Function version changes state because of a customer action, such as creating, updating, publishing, or deleting a function. These events help platform and DevOps teams to trigger automation as soon as a function becomes ready to invoke, an update finishes, or an operation fails, without polling the&amp;nbsp;&lt;a href="https://docs.aws.amazon.com/lambda/latest/api/API_GetFunction.html" target="_blank" rel="noopener noreferrer"&gt;GetFunction&lt;/a&gt; API.&lt;/p&gt; 
&lt;p&gt;Customers use Lambda Event Functions to build APIs, event processing workloads, multi-step workflows, and data pipelines. As organizations grow to thousands of functions, platform teams need to know when a function changes state so they can take the next step. For example, a deployment pipeline can run integration tests and then shift alias traffic once a new version becomes active.&amp;nbsp;Until now, these tools had to poll the GetFunction&amp;nbsp;API to track state changes. Polling consumed API quota, slowed down pipelines, and required custom retry logic, which added operational overhead. With this launch, you can create &lt;a href="https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-rules.html" target="_blank" rel="noopener noreferrer"&gt;EventBridge rules&lt;/a&gt;&amp;nbsp;that match on fields such as the function ARN, detail type, or state, and route matched events to targets such as &lt;a href="https://aws.amazon.com/step-functions/" target="_blank" rel="noopener noreferrer"&gt;AWS Step Functions&lt;/a&gt;, AWS Lambda, &lt;a href="https://aws.amazon.com/sns/" target="_blank" rel="noopener noreferrer"&gt;Amazon SNS&lt;/a&gt;, or &lt;a href="https://aws.amazon.com/sqs/" target="_blank" rel="noopener noreferrer"&gt;Amazon SQS&lt;/a&gt;. This helps you build reliable, event-driven deployment pipelines across all of your functions, without writing or maintaining custom polling logic.&lt;/p&gt; 
&lt;p&gt;This feature is available in all commercial &lt;a href="https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/" target="_blank"&gt;AWS Regions&lt;/a&gt;. You can create rules by using the EventBridge console, AWS Command Line Interface (AWS CLI), AWS SDKs, AWS CloudFormation, AWS Cloud Development Kit (AWS CDK), or AWS Serverless Application Model (AWS SAM). Lambda publishes these events automatically at no additional cost. Standard pricing applies to the targets that your EventBridge rules invoke. To learn more, see the &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/monitoring-eventbridge-function-state.html" target="_blank" rel="noopener noreferrer"&gt;AWS Lambda Developer Guide&lt;/a&gt;&amp;nbsp;and the &lt;a href="https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-what-is.html" target="_blank"&gt;Amazon EventBridge User Guide.&lt;/a&gt;&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/aws-lambda-function-state-events/</ore:originalUrl>
      <ore:upstreamId>c0e711c8e0f6af456df22b477ce4e7d1954cfe73</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:d21718c8529547941098207bb13d7581</id>
    <title>AWS Network Firewall introduces automated Internet firewall in public preview</title>
    <updated>2026-11-20T22:38:00Z</updated>
    <published>2026-11-20T22:38:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/network-firewall-automated-internet/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;AWS Network Firewall announces the public preview of automated Internet firewall, a new centralized control that allows you to configure Network Firewall, with native network address translation (NAT) capability, on the internet gateways of all the Virtual Private Clouds (VPCs) in your environment. Using automated Internet firewall mode, you can centrally define your Network Firewall security rules and enforce them on all inbound and outbound traffic across the internet gateways of your VPCs. You are not required to make routing or architectural changes to deploy automated Internet firewall. You can deploy it across select VPCs or your entire account, organization or organization unit.&lt;/p&gt; 
&lt;p&gt;AWS Network Firewall is a stateful, managed, network firewall and intrusion detection and prevention service for your VPC. Customers use it to inspect their traffic and secure AWS resources. Prior to this launch, customers would configure AWS Network Firewalls inside their VPCs in the traffic path of all internet communication to achieve thorough security coverage against the threats on the internet. They deployed Network Firewall endpoints in dedicated subnets and made route updates for every subnet that needed internet access across all their VPCs. In addition, they monitored the environment to ensure that no new internet network paths bypassed these security controls. Automated Internet firewall makes this deployment and management simpler. You just define and maintain filtering rules, and AWS enforces it directly at the internet gateway of every VPC in scope, ensuring that all intended traffic entering or leaving your VPCs via the internet gateway is inspected. Automated Internet firewall comes with built-in NAT functionality for your egress-only internet connectivity needs. You can use it to filter traffic, perform NAT and log all internet activity across all internet gateways. You don't need to make architectural changes inside every VPC or monitor every internet network path. Automated Internet firewall allows you the option to automatically extend your organization's security policy to all future VPCs and subnets at creation.&lt;/p&gt; 
&lt;p&gt;To help you get started quickly, automated Internet firewall comes with a default security policy, which uses Amazon managed rule groups including active threat defense that uses AWS unique threat intelligence to protect your workloads against evolving threats on the internet. You can also create your own custom rule groups or use any of the managed rule groups from AWS Marketplace with automated Internet firewall.&lt;/p&gt; 
&lt;p&gt;AWS Network Firewall operating in automated Internet firewall mode is available in preview in all AWS Regions except AWS GovCloud and China. To learn more, visit the &lt;a href="https://docs.aws.amazon.com/network-firewall/"&gt;Network Firewall documentation&lt;/a&gt; and see the &lt;a href="https://aws.amazon.com/network-firewall/pricing"&gt;AWS Network Firewall pricing page&lt;/a&gt;. To get started, visit the Amazon VPC or Network Security Manager console.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/network-firewall-automated-internet/</ore:originalUrl>
      <ore:upstreamId>d0ec8f682174ffe2e30deb3b6bb329765f689425</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hacker-news:7a6825ee45ceebfe5b4f4b7f5108788c</id>
    <title>NINLIVE: The Nine Inch Nails live archive</title>
    <updated>2026-11-20T22:30:47Z</updated>
    <published>2026-11-20T22:30:47Z</published>
    <link rel="alternate" href="https://ninlive.com/" />
    <link rel="via" href="https://news.ycombinator.com/rss" />
    <category scheme="urn:ore-news:sources" term="hacker-news" label="Hacker News" />
    <author>
      <name>Hacker News</name>
    </author>
    <source>
      <id>urn:ore-news:source:hacker-news</id>
      <title>Hacker News</title>
      <link rel="alternate" href="https://news.ycombinator.com/" />
      <link rel="via" href="https://news.ycombinator.com/rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hacker-news</ore:sourceId>
      <ore:sourceName>Hacker News</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://news.ycombinator.com/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://news.ycombinator.com/rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://ninlive.com/</ore:originalUrl>
      <ore:upstreamId>https://ninlive.com/</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hacker-news:b5b1b7f066a84a979f641e032439abaa</id>
    <title>The Hungry Butler Effect: Concealed Commercial Incentives in LLMs</title>
    <updated>2026-11-20T22:18:20Z</updated>
    <published>2026-11-20T22:18:20Z</published>
    <link rel="alternate" href="https://www.researchgate.net/publication/418143113_The_Hungry_Butler_Effect_Concealed_Commercial_Incentives_and_the_Erosion_of_Epistemic_Rigour_in_Large_Language_Models" />
    <link rel="via" href="https://news.ycombinator.com/rss" />
    <category scheme="urn:ore-news:sources" term="hacker-news" label="Hacker News" />
    <author>
      <name>Hacker News</name>
    </author>
    <source>
      <id>urn:ore-news:source:hacker-news</id>
      <title>Hacker News</title>
      <link rel="alternate" href="https://news.ycombinator.com/" />
      <link rel="via" href="https://news.ycombinator.com/rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hacker-news</ore:sourceId>
      <ore:sourceName>Hacker News</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://news.ycombinator.com/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://news.ycombinator.com/rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://www.researchgate.net/publication/418143113_The_Hungry_Butler_Effect_Concealed_Commercial_Incentives_and_the_Erosion_of_Epistemic_Rigour_in_Large_Language_Models</ore:originalUrl>
      <ore:upstreamId>https://www.researchgate.net/publication/418143113_The_Hungry_Butler_Effect_Concealed_Commercial_Incentives_and_the_Erosion_of_Epistemic_Rigour_in_Large_Language_Models</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:9928084ff33ac5f9d6bc5b9bb73b834c</id>
    <title>Amazon RDS for Oracle now supports Replica First Patching for reduced downtime</title>
    <updated>2026-11-20T22:00:00Z</updated>
    <published>2026-11-20T22:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/rds-oracle-replica-first-patching/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;&lt;a href="https://aws.amazon.com/rds/oracle/"&gt;Amazon Relational Database Service (Amazon RDS) for Oracle&lt;/a&gt; now supports Replica First Patching, which reduces downtime during minor version upgrades. Replica First Patching is available for Enterprise Edition DB instances. With Replica First Patching, you apply a minor version upgrade to a replica in the same AWS Region first while your primary DB instance continues to serve traffic, and then switch over to the replica when you're ready to complete the upgrade. If the replica is in read-only mode, you can validate the new minor engine version with your read traffic.&lt;/p&gt; 
&lt;p&gt;Replica First Patching helps you keep mission-critical Oracle workloads current on minor versions with less disruption. You choose when to switch over within the switchover window, for example during a low-traffic period. If you don't switch over within the window, Amazon RDS rolls back the replica to its original minor engine version. After the switchover, Amazon RDS completes the upgrade on the new primary DB instance. Amazon RDS then upgrades your other replicas, including your former primary DB instance, to the same minor engine version.&lt;/p&gt; 
&lt;p&gt;We recommend that you connect your applications through the &lt;a href="https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/oracle-primary-endpoint.html" target="_blank" rel="noopener noreferrer"&gt;Primary Endpoint&lt;/a&gt; when you use Replica First Patching. The Primary Endpoint is a DNS name that resolves to the current primary DB instance, so your applications reach the new primary DB instance after the switchover without connection string changes.&lt;/p&gt; 
&lt;p&gt;Replica First Patching is available at no additional charge in all commercial AWS Regions where Amazon RDS for Oracle is available. Standard pricing applies to the replica DB instance. To learn more, see &lt;a href="https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/oracle-upgrade-replica-first.html" target="_blank" rel="noopener noreferrer"&gt;Upgrading with Replica First Patching&lt;/a&gt; in the Amazon RDS User Guide.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/rds-oracle-replica-first-patching/</ore:originalUrl>
      <ore:upstreamId>6a2cebc4340117ae8e0d31d42a5786d069bff421</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:4b4cfc0c6d1582a1dffaa1376e4e097b</id>
    <title>Amazon Cognito extends multi-Region replication to additional AWS Regions</title>
    <updated>2026-11-20T22:00:00Z</updated>
    <published>2026-11-20T22:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/cognito-mrr-opt-in-regions/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;&lt;a href="https://aws.amazon.com/cognito/"&gt;Amazon Cognito&lt;/a&gt; multi-Region replication (MRR) now supports additional AWS Regions, extending the resilience benefits of MRR to more workloads. Amazon Cognito helps you implement secure sign-in and access control for users, AI agents, and microservices in minutes, and MRR lets you synchronize user and machine identity data, including credentials, user pool configurations, and federation setups, to a secondary user pool in a standby Region you designate in near real-time. With user data in the standby Region, you can redirect traffic and keep authentication available if there is a disruption in your primary Region.&lt;/p&gt;
&lt;p&gt;Previously, MRR was available in 16 commercial Regions and the AWS GovCloud (US) Regions. You can now also use MRR to replicate your user data to Asia Pacific (Hyderabad, Hong Kong, Jakarta, Malaysia, Melbourne, New Zealand, Osaka, Taipei, Thailand), Canada West (Calgary), Europe (Milan, Spain, Zurich), Israel (Tel Aviv), Mexico (Central), Africa (Cape Town) Regions, helping you meet resilience, data residency, and compliance requirements in the Regions that best align with your needs.&lt;/p&gt;
&lt;p&gt;MRR is available as an add-on for user pools on the Essentials or Plus feature plans, and requires a multi-Region &lt;a href="https://aws.amazon.com/kms/"&gt;AWS KMS&lt;/a&gt; customer managed key (CMK). For the full list of AWS Regions where Amazon Cognito is available, see &lt;a href="https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/"&gt;AWS Capabilities by Region&lt;/a&gt;. To get started, visit the &lt;a href="https://docs.aws.amazon.com/cognito/latest/developerguide/user-pool-multi-region.html" target="_blank"&gt;developer guide&lt;/a&gt; for instructions and the &lt;a href="https://aws.amazon.com/cognito/pricing/"&gt;pricing page&lt;/a&gt; for pricing details.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/cognito-mrr-opt-in-regions/</ore:originalUrl>
      <ore:upstreamId>864da979c045b5e595db76e05e9889d0a540dd00</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:ff013895c5b71e13a6c04703adf81212</id>
    <title>Amazon Neptune Serverless now delivers up to 30% better performance and smarter scaling</title>
    <updated>2026-11-20T21:50:00Z</updated>
    <published>2026-11-20T21:50:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/aws-neptune-serverless-r8g-generally-available" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;&lt;span style="color: inherit;"&gt;&lt;span style="color: inherit;"&gt;&lt;span style="color: inherit;"&gt;&lt;a target="_blank" href="https://docs.aws.amazon.com/neptune/latest/userguide/neptune-serverless.html" style="color: rgb(18,100,163); text-decoration: none;" rel="noopener noreferrer"&gt;Amazon Neptune Serverless&lt;/a&gt;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt; now delivers up to 30% better performance at the same price per Neptune Capacity Unit, running on AWS Graviton4 processors. The new Graviton4-based platform also brings an improved scaling algorithm that adjusts Neptune Capacity Units (NCUs) more closely to your workload. This especially helps applications with many concurrent graph queries, such as real-time fraud detection, recommendation engines and generative AI applications that run graph lookups on every request.&lt;br&gt; Neptune Serverless scales database capacity automatically as your application’s demand changes, so you can run graph applications with spiky or unpredictable traffic, such as fraud detection, recommendation engines, and generative AI applications, without provisioning for peak capacity. You pay only for the capacity you use. All newly created Neptune Serverless instances will be using AWS Graviton4 processors.&lt;br&gt; &lt;br&gt; You can create new Neptune Serverless instances using &lt;span style="color: inherit;"&gt;&lt;span style="color: inherit;"&gt;&lt;span style="color: inherit;"&gt;&lt;a target="_blank" href="https://console.aws.amazon.com/neptune/" style="color: rgb(18,100,163); text-decoration: none;" rel="noopener noreferrer"&gt;AWS Management Console&lt;/a&gt;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt; or the &lt;span style="color: inherit;"&gt;&lt;span style="color: inherit;"&gt;&lt;span style="color: inherit;"&gt;&lt;a target="_blank" style="color: rgb(18,100,163); text-decoration: none;"&gt;AWS CLI&lt;/a&gt;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;. You can upgrade existing clusters to the latest version in the next release. For more information on pricing and regional availability, refer to the &lt;span style="color: inherit;"&gt;&lt;span style="color: inherit;"&gt;&lt;span style="color: inherit;"&gt;&lt;a target="_blank" style="color: rgb(18,100,163); text-decoration: none;"&gt;Amazon Neptune pricing page&lt;/a&gt;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt; and &lt;span style="color: inherit;"&gt;&lt;span style="color: inherit;"&gt;&lt;span style="color: inherit;"&gt;&lt;a target="_blank" style="color: rgb(18,100,163); text-decoration: none;"&gt;Neptune Serverless documentation&lt;/a&gt;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/aws-neptune-serverless-r8g-generally-available</ore:originalUrl>
      <ore:upstreamId>6e00c22c337f31343b32e730d59d47b7dbcfbbfe</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hatena-bookmark-technology:b43c7c657dfc1fcd928162a4ca9486a6</id>
    <title>トランプ氏、データセンター国外建設認めず　米中でAI安全策検討 - 日本経済新聞</title>
    <updated>2026-11-20T21:44:32Z</updated>
    <published>2026-11-20T21:44:32Z</published>
    <link rel="alternate" href="https://www.nikkei.com/article/DGXZQOGN20CXV0Q6A121C2000000/" />
    <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    <category scheme="urn:ore-news:sources" term="hatena-bookmark-technology" label="Hatena Bookmark Technology" />
    <author>
      <name>Hatena Bookmark Technology</name>
    </author>
    <source>
      <id>urn:ore-news:source:hatena-bookmark-technology</id>
      <title>Hatena Bookmark Technology</title>
      <link rel="alternate" href="https://b.hatena.ne.jp/hotentry/it" />
      <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hatena-bookmark-technology</ore:sourceId>
      <ore:sourceName>Hatena Bookmark Technology</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://b.hatena.ne.jp/hotentry/it</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://b.hatena.ne.jp/hotentry/it.rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://www.nikkei.com/article/DGXZQOGN20CXV0Q6A121C2000000/</ore:originalUrl>
      <ore:upstreamId>https://www.nikkei.com/article/DGXZQOGN20CXV0Q6A121C2000000/</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:511f5a5f0be566ffb693b94a25cf3ffa</id>
    <title>Amazon CloudWatch extends the PromQL query window to 30 days</title>
    <updated>2026-11-20T21:23:00Z</updated>
    <published>2026-11-20T21:23:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/cloudwatch-promql-query-30days/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;Amazon CloudWatch now supports a 30-day query window for PromQL queries against OpenTelemetry metrics, up from 7 days. You can query a month of data in a single request, chart month-over-month and week-over-week trends on one dashboard, and alarm on a 30-day baseline.&lt;/p&gt; 
&lt;p&gt;Teams typically define service level objectives (SLOs) over a 30-day rolling window, longer than a 7-day query can measure. You can now calculate availability and remaining error budget for a full SLO period in one query, and alarm when a service is on track to exhaust its budget. A month of history also makes capacity forecasts more reliable, because a 7-day baseline skews to a single busy weekend.&lt;/p&gt; 
&lt;p&gt;This feature is available at no additional cost in all AWS Regions where PromQL queries against OpenTelemetry metrics in Amazon CloudWatch are available.&lt;/p&gt; 
&lt;p&gt;To get started, see Query OpenTelemetry metrics with PromQL in the Amazon CloudWatch &lt;a title="CloudWatch PromQL queries" href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-PromQL.html"&gt;User Guide&lt;/a&gt;.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/cloudwatch-promql-query-30days/</ore:originalUrl>
      <ore:upstreamId>3a44c1a96340154fd49bfc7ddd110c254f93484b</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:fe6b3622683cd0dec1a43f4f59a7e0b5</id>
    <title>Account Mapping and Planning now available in AWS Partner Central</title>
    <updated>2026-11-20T21:00:00Z</updated>
    <published>2026-11-20T21:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/account-mapping-and-planning/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;AWS Partners can now map their target accounts against AWS records and find where to collaborate with AWS on joint go-to-market before an opportunity exists. Account Mapping and Planning in AWS Partner Central replaces manual, spreadsheet-based account mapping. Upload a target account list through CSV, API, or CRM integration, and accounts are matched automatically against AWS records, including accounts without an ACE opportunity and in any country.&lt;/p&gt;
&lt;p&gt;Partners can use Account Mapping and Planning to enrich matched accounts with AWS Marketplace propensity insights, solution-level purchase likelihood, and eligibility for programs such as the Partner Greenfield Program and the Partner-Led Sales Motion. This helps Partners prioritize high-propensity and program-eligible accounts for go-to-market activity. Eligible Partners can also request joint account planning with AWS sales on accounts marked Qualified, so AWS and Partner teams can align on an account strategy earlier. Account planning is available to Consulting Partners that are ACE-eligible, Premier tier and managed by an AWS Partner Development Manager (PDM), and to ISVs that are ACE-eligible, enrolled in the SaaS Co-sell Benefit program and PDM-managed.&lt;/p&gt;
&lt;p&gt;Account Mapping and Planning is available under the Sell tab in AWS Partner Central, and account matching and enrichment are open to all ACE-eligible Partners. Partners can work in the Partner Central console, through the API and SDK, through the Partner Central MCP server, or through an integration Partner to connect results to their CRM.&lt;/p&gt;
&lt;p&gt;To get started, sign in to AWS Partner Central, go to the Account Mapping page under the Sell tab, and upload a target account list.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/account-mapping-and-planning/</ore:originalUrl>
      <ore:upstreamId>f153ada87741a768bccaae4b9523d9090e89d683</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:6e62631038e936e03ad28c56f315382b</id>
    <title>Lead groups and channel recommendations now available in AWS Partner Central</title>
    <updated>2026-11-20T21:00:00Z</updated>
    <published>2026-11-20T21:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/partner-central-lead-groups/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;AWS Partners can now organize enriched leads and plan outreach with lead groups and channel recommendations in AWS Partner Central. Enriched leads are automatically grouped by solution area and segmented into sales-ready, marketing-ready, and limited-potential groups, so you no longer have to segment leads by hand. Limited-potential leads help you avoid spending time and budget on leads unlikely to convert, lowering your cost of acquiring new customers. For each enriched lead, you also get guidance on whether phone or email may be more effective, along with AI-generated call scripts and email scripts to act on it.&lt;/p&gt;
&lt;p&gt;Marketing-ready lead groups can be sent to Demand Center to create assets and launch targeted campaigns. Sales-ready leads can be exported to the Partner's CRM for direct outreach.&lt;/p&gt;
&lt;p&gt;Lead groups and channel recommendations are available to ACE-eligible Partners on the Leads page in AWS Partner Central and through the AWS Partner Central Selling API.&lt;/p&gt;
&lt;p&gt;To get started, sign in to AWS Partner Central and go to the Leads page.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/partner-central-lead-groups/</ore:originalUrl>
      <ore:upstreamId>5c86b319c2bf1abbca4ee58acfbd48e7e46eaf8b</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:2645417d625d4a38472fb5d2f2e92fd4</id>
    <title>Demand Center now available in AWS Partner Central</title>
    <updated>2026-11-20T21:00:00Z</updated>
    <published>2026-11-20T21:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/demand-center-partner-central/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;AWS Partners can now plan, launch, fund, and measure demand generation campaigns in one AI-powered experience. Demand Center in AWS Partner Central succeeds Marketing Central and brings together Marketing Central and MDF capabilities, letting you work in Partner Central, in your CRM, or in your AI agents.&lt;/p&gt;
&lt;p&gt;Create hero and distribution assets in multiple languages in minutes with AI campaign creation. Generate content from reference materials, a URL, or a description, and launch it across email, social, and banner ads. Upload leads to get them enriched with propensity signals and recommended next actions. Choose from ready-to-run Partner Ready Campaign kits or connect with AWS-vetted agencies through Agency Connect.&lt;/p&gt;
&lt;p&gt;Generate case studies with AI from ACE closed-won opportunities, and tailor campaign content to the leads included in each campaign. Connect your CRM or marketing automation tool agent-to-agent, or use Demand Center inside agents such as AWS Quick through the Partner Central MCP server. Track campaign-to-revenue performance in Partner Analytics.&lt;/p&gt;
&lt;p&gt;To get started, sign in to AWS Partner Central and select Demand Center.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/demand-center-partner-central/</ore:originalUrl>
      <ore:upstreamId>34345fb38770408032c115f1a4191e05c4320a9b</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:fb7506a78a2ef70be284f32e78673468</id>
    <title>Amazon CloudWatch EKS Container Insights now offers built-in monitoring for open source Kubernetes tools</title>
    <updated>2026-11-20T20:47:00Z</updated>
    <published>2026-11-20T20:47:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/cloudwatch-eks-kubernetes-tools/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;Today, Amazon CloudWatch announces built-in monitoring for open source tools running on your Amazon EKS clusters, including Karpenter, KEDA, vLLM, KServe, SGLang, Ray and Knative Serving. You get dashboards for the tools you already use without running Prometheus or Grafana yourself.&lt;/p&gt; 
&lt;p&gt;Monitoring starts automatically when you enable OTel Container Insights. For your AI inference workloads, you can see queued requests, time to first token, and KV cache usage for each model server. For autoscaling, you can see which scalers are failing and how long your scale loop takes. CloudWatch tags every metric with its pod, workload, and node, so you can trace a slow model server to the node it runs on.&lt;/p&gt; 
&lt;p&gt;These EKS solutions are available in version 8.0.0 and later of the add-on and Helm chart, in all AWS Regions where CloudWatch supports OpenTelemetry metrics. Metrics are charged at the Amazon EKS OpenTelemetry ingestion rate of $0.08 per GB. For details, see Amazon CloudWatch &lt;a title="CloudWatch EKS insights pricing" href="https://aws.amazon.com/cloudwatch/pricing/"&gt;insights pricing&lt;/a&gt;.&amp;nbsp;&lt;/p&gt; 
&lt;p&gt;To get started, see Solutions in the Amazon CloudWatch &lt;a title="CloudWatch EKS OTel Container Insights" href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/container-insights-eks-otel.html"&gt;User Guide.&lt;/a&gt;&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/cloudwatch-eks-kubernetes-tools/</ore:originalUrl>
      <ore:upstreamId>38f3a462608c5989d35d6f4b6b0028e8482a3542</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:bd4c397d147666e73b56dfd65f22b8f5</id>
    <title>AWS Quick now supports group assignments for custom permissions and limit profiles</title>
    <updated>2026-11-20T20:42:00Z</updated>
    <published>2026-11-20T20:42:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/aws-quick-group-assignments-custom-permissions-limit-profiles/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;AWS Quick now supports assignments for custom permissions and limit profiles to groups from your enterprise identity provider (IdP).&amp;nbsp;Administrators can now apply feature restrictions and per-user resource limits to IdP groups, in addition to the existing user, role, and account assignments. Organizations can align governance with their enterprise identity structure without maintaining assignments for individual users.&lt;br&gt; &lt;br&gt; Administrators manage user, account or group assignments in the Quick administration console or through new policy assignment APIs. For example, an organization can assign its finance group a custom permissions profile that blocks members from creating agents, or apply Deny by Default so that, within selected feature categories, the group can use only capabilities an administrator explicitly allows. Administrators can also assign a limit profile to a group to set each member’s index capacity and agent hours. Quick enforces these limits automatically as users consume resources.&lt;br&gt; &lt;br&gt; When group-level assignments apply to a user who belongs to multiple groups, Quick resolves overlapping assignments as follows: for custom permissions, a capability denied by any group stays denied, and for limit profiles, the user receives the highest value for each limit type across those groups.&lt;br&gt; &lt;br&gt; Group assignments are available in Quick for Professional and Enterprise plans. For feature availability by AWS Region, see AWS &lt;a href="https://docs.aws.amazon.com/quick/latest/userguide/regions.html#regions-qs" target="_blank" rel="noopener noreferrer"&gt;Quick Regions&lt;/a&gt;. To learn more, see the &lt;a href="https://docs.aws.amazon.com/quick/latest/userguide/custom-permissions.html" target="_blank" rel="noopener noreferrer"&gt;custom permissions&lt;/a&gt; and &lt;a href="https://docs.aws.amazon.com/quick/latest/userguide/limit-profiles.html" target="_blank" rel="noopener noreferrer"&gt;limit profiles&lt;/a&gt; documentation.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/aws-quick-group-assignments-custom-permissions-limit-profiles/</ore:originalUrl>
      <ore:upstreamId>d3a7913b0a10e68a2b59de8728a363e0c03208f6</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:b370bf1d9a0f701a8b8e9b141ea4273d</id>
    <title>AWS announces Data Hub in AWS Billing and Cost Management (preview)</title>
    <updated>2026-11-20T20:30:00Z</updated>
    <published>2026-11-20T20:30:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/data-hub-billing-cost-management-preview/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;Today, AWS announces the preview of Data Hub in AWS Billing and Cost Management, a managed data layer that enables AWS FinOps Agent to query cost and usage data with SQL. In preview, Data Hub is available to AWS FinOps Agent, so the agent can identify the individual resources behind a cost change, break down spend by team or cost allocation tag, and show how a resource's cost and usage change hour by hour. With AWS FinOps Agent and Data Hub, customers get these answers without setting up a data export or building and maintaining a cost data pipeline.&lt;/p&gt; 
&lt;p&gt;Data Hub provides 13 months of hourly, resource-level cost and usage data in the published CUR 2.0 schema, including resource identifiers and cost allocation tags. AWS provisions the data, refreshes data daily, and maintains the schema as new services, commitments, and charge types are added. When set up from the management account, Data Hub covers cost and usage data across the accounts in your organization.&lt;/p&gt; 
&lt;p&gt;Data Hub (preview) is available in the US East (N. Virginia) Region and covers cost and usage data across regions. There is no charge for Data Hub during preview.&lt;/p&gt; 
&lt;p&gt;To learn more about Data Hub, see the &lt;a href="https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/data-hub.html" target="_blank" rel="noopener noreferrer"&gt;AWS Billing and Cost Management User Guide&lt;/a&gt; and the &lt;a href="https://aws.amazon.com/blogs/aws-cloud-financial-management/ask-aws-finops-agent-resource-level-cost-questions-with-aws-billing-and-cost-management-data-hub-preview" target="_blank" rel="noopener noreferrer"&gt;launch blog&lt;/a&gt;. You can get started from the &lt;a href="https://us-east-1.console.aws.amazon.com/costmanagement/home?region=us-east-1" target="_blank" rel="noopener noreferrer"&gt;Data Hub page&lt;/a&gt; in the AWS Billing and Cost Management console or from the &lt;a href="https://aws.amazon.com/finops-agent/" target="_blank" rel="noopener noreferrer"&gt;AWS FinOps Agent&lt;/a&gt; console.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/data-hub-billing-cost-management-preview/</ore:originalUrl>
      <ore:upstreamId>e042d7326c974818ccd9ca045bedab32281193d4</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:5268086850049301d2679e5fc9ed3d97</id>
    <title>AWS Quick introduces enterprise guardrails (preview)</title>
    <updated>2026-11-20T20:30:00Z</updated>
    <published>2026-11-20T20:30:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/aws-quick-enterprise-guardrails-preview/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;AWS Quick now includes enterprise guardrails, giving administrators configurable content safety and sensitive-information controls for user prompts. Administrators can apply guardrail policies to individual users or enterprise identity provider (IdP) groups or set a policy as the account default. User-level policies take precedence over group policies and account defaults. When multiple group policies apply, Quick combines their content restrictions, using the stricter setting when controls overlap.&lt;br&gt; &lt;br&gt; Administrators create guardrail policies in the Quick administration console using content filters, denied topics, blocked words and phrases, prompt-attack detection, and controls for selected types of personally identifiable information (PII). For example, an administrator can create a policy that blocks prompts containing confidential project names and assign it to an IdP group.&lt;br&gt; &lt;br&gt; Detect-only mode lets administrators test prompt-filtering rules against real production traffic before enforcing them. In this mode, Quick evaluates user prompts and logs policy matches without blocking requests, so administrators can assess the impact on business workflows and refine policies. When administrators enable enforcement, Quick blocks matching prompts and displays a message to the user. Administrators can review detected and blocked events in Amazon CloudWatch Logs.&lt;br&gt; &lt;br&gt; Enterprise guardrails are available in preview for select Quick customers with Professional and Enterprise plans. For feature availability by AWS Region, see &lt;a href="https://docs.aws.amazon.com/quick/latest/userguide/regions.html#regions-qs" target="_blank"&gt;AWS Quick Regions&lt;/a&gt;. To learn more, see the &lt;a href="https://docs.aws.amazon.com/quick/latest/userguide/guardrails.html" target="_blank"&gt;enterprise guardrails documentation&lt;/a&gt;.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/aws-quick-enterprise-guardrails-preview/</ore:originalUrl>
      <ore:upstreamId>95b93fff19edab6a6dff4b5b1acedb5a0a54d223</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:cloudflare-blog:1c46150cbbd76b027a95cc553c2a12f1</id>
    <title>How Cloudflare WAF protects against ruby2shell (CVE-2026-132825)</title>
    <updated>2026-11-20T20:24:38Z</updated>
    <published>2026-11-20T20:24:38Z</published>
    <link rel="alternate" href="https://blog.cloudflare.com/ruby2shell-waf-protection/" />
    <link rel="via" href="https://blog.cloudflare.com/rss/" />
    <category scheme="urn:ore-news:sources" term="cloudflare-blog" label="Cloudflare Blog" />
    <author>
      <name>Cloudflare Blog</name>
    </author>
    <source>
      <id>urn:ore-news:source:cloudflare-blog</id>
      <title>Cloudflare Blog</title>
      <link rel="alternate" href="https://blog.cloudflare.com/" />
      <link rel="via" href="https://blog.cloudflare.com/rss/" />
    </source>
    <content type="html">&lt;p&gt;On November 19, 2026, the Ruby team disclosed ruby2shell (&lt;a href="https://github.com/ruby/ruby/security/advisories/GHSA-34m4-m9fh-gqp5"&gt;&lt;span style="text-decoration:underline"&gt;CVE-2026-132825&lt;/span&gt;&lt;/a&gt;), a heap buffer overflow in the way Ruby changes the case of strings. Ruby rates the flaw Critical and says it is aware of proofs of concept that achieve remote code execution in some scenarios. Fixes shipped in &lt;a href="https://www.ruby-lang.org/en/news/2026/11/18/multiple-vulnerabilities-in-regexp-and-string/"&gt;&lt;span style="text-decoration:underline"&gt;Ruby 3.3.14, 3.4.13, and 4.0.10&lt;/span&gt;&lt;/a&gt;.&lt;/p&gt;&lt;p&gt;The reach is wide. Veria Labs reports that Ruby on Rails and classic-style Sinatra applications reach the bug in their default configuration, before any authentication. Self-hosted products that bundle Ruby, including GitLab, GitHub Enterprise Server, Mastodon, OpenProject, Discourse and Chatwoot, shipped an affected Ruby in their latest release at the time of disclosure.&lt;/p&gt;&lt;p&gt;Cloudflare WAF blocks ruby2shell for all customers, including those on the Free plan. We have added two rules to both the Cloudflare Free Managed Ruleset and the Cloudflare Managed Ruleset, with Block as the default action: one for ruby2shell and one for GHSA-87fm-7w84-j2px, a related integer overflow in Ruby string case conversion fixed in the same releases.&lt;/p&gt;&lt;p&gt;The WAF is a compensating control, not a replacement for patching. Exploits can reach the bug through paths a WAF does not see, and the only complete fix is to upgrade Ruby. Our team continues to monitor attack traffic and will update the rules as new techniques appear. You can track rule changes in the &lt;a href="https://developers.cloudflare.com/waf/change-log/changelog/"&gt;&lt;span style="text-decoration:underline"&gt;WAF changelog&lt;/span&gt;&lt;/a&gt; and get the latest on the vulnerability in the &lt;a href="https://radar.cloudflare.com/zero-wire/ruby2shell"&gt;&lt;span style="text-decoration:underline"&gt;Cloudflare Zero Wire briefing&lt;/span&gt;&lt;/a&gt;.&lt;/p&gt;&lt;p&gt;Cloudflare has patched its own systems that use Ruby, and we have found no indication of compromise.&lt;/p&gt;&lt;h2&gt;What we know about ruby2shell&lt;/h2&gt;&lt;p&gt;Ruby strings carry an encoding, and Ruby still supports many legacy single-byte encodings, such as ISO-8859-1 (Latin-1) and Windows-1252, alongside UTF-8. In a single-byte encoding each character takes one byte, so changing the case of a string usually produces output of the same length.&lt;/p&gt;&lt;p&gt;The German sharp s (ß) breaks that assumption. Its uppercase form is two characters, SS. In 14 ISO-8859 and Windows-125x encodings, Ruby writes those two bytes but checks for room for only one. According to Veria Labs, a string with 21 sharp s characters overflows the output buffer by one byte. The methods that reach the bug are &lt;code&gt;upcase&lt;/code&gt;, &lt;code&gt;swapcase&lt;/code&gt;, &lt;code&gt;downcase(:fold)&lt;/code&gt; and &lt;code&gt;casecmp?&lt;/code&gt;. UTF-8 strings take a different code path and are not affected.&lt;/p&gt;&lt;p&gt;A one-byte overflow can look harmless. In a memory-corruption exploit, though, a single byte written past the end of a heap buffer can be enough to corrupt an adjacent object or allocator metadata. Ruby says it is aware of proofs of concept that turn this flaw into code execution, and Veria Labs says it will publish its own proof of concept about a week after disclosure. We expect scanning to start soon after.&lt;/p&gt;&lt;h3&gt;Why default Rails and Sinatra apps are exposed&lt;/h3&gt;&lt;p&gt;HTML forms can only send GET and POST requests. To simulate PUT, PATCH, or DELETE, many web frameworks accept a &lt;code&gt;_method&lt;/code&gt; parameter in a POST request. Rack, the interface most Ruby web frameworks build on, implements this in its MethodOverride middleware, which converts the value of &lt;code&gt;_method&lt;/code&gt; to uppercase. Rails includes this middleware by default, and classic-style Sinatra applications enable it. An attacker can send a multipart POST request whose &lt;code&gt;_method&lt;/code&gt; part declares a legacy character set and contains a run of sharp s characters. The framework upcases the value while it is still routing the request, before any application code or authentication check runs.&lt;/p&gt;&lt;p&gt;Veria Labs reports that other frameworks and plain Rack applications are not exposed by default. Application code that changes the case of strings received in a legacy encoding may still be affected, wherever the string comes from.&lt;/p&gt;&lt;h3&gt;Who is affected&lt;/h3&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;Condition&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;Details&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;Ruby version&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Ruby 3.3.13 and earlier, 3.4.0 through 3.4.12, and 4.0.0 through 4.0.9. Veria Labs reports the bug has been present since Ruby 2.4.0. Ruby 3.2 and earlier have reached end of life and will not receive the fix.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;Framework&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Rails and classic-style Sinatra in their default configuration. Any other code that changes the case of attacker-controlled strings in a legacy single-byte encoding.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;Bundled software&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;As of November 19, 2026, Veria Labs lists GitLab 19.6.0, GitHub Enterprise Server 3.22.5, Mastodon 4.7.5, OpenProject 17.9.7, Discourse 2026.10.1 and Chatwoot 4.20.0 as bundling an affected Ruby in their latest release. Discourse moved its Docker base image to Ruby 4.0.10 on November 19, so rebuilding a Docker install picks up the fix.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;Distribution packages can backport fixes without changing the Ruby version number, so check the full package version against your distribution&amp;#x27;s advisory.&lt;/p&gt;&lt;h3&gt;Six more Ruby flaws in the same release&lt;/h3&gt;&lt;p&gt;Ruby 3.3.14, 3.4.13, and 4.0.10 also fix &lt;a href="https://www.ruby-lang.org/en/news/2026/11/18/multiple-vulnerabilities-in-regexp-and-string/"&gt;&lt;span style="text-decoration:underline"&gt;six other memory safety flaws&lt;/span&gt;&lt;/a&gt;, and Ruby says several of them can lead to code execution. One, GHSA-87fm-7w84-j2px, is an integer overflow in the same string case conversion code, and our second WAF rule covers it. The other five are in Ruby&amp;#x27;s regular expression engine. Most of them require the application to compile or match a regular expression pattern supplied by the attacker. That is uncommon in web applications, but it does happen in search features, filtering rules and admin tools.&lt;/p&gt;&lt;h2&gt;How Cloudflare WAF protects you&lt;/h2&gt;&lt;p&gt;Upgrading every Ruby runtime takes time, especially when Ruby is bundled inside self-hosted products and container images. Cloudflare WAF reduces your exposure while you patch.&lt;/p&gt;&lt;h3&gt;New managed rules, on for every customer&lt;/h3&gt;&lt;p&gt;Both rules are part of the Cloudflare Free Managed Ruleset and the Cloudflare Managed Ruleset (Ruleset ID efb7b8c949ac4650a09736fc376e9aee), with Block as the default action.&lt;/p&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;Rule description&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;Rule ID&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;Ruleset&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;Default action&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;Ruby - Heap Overflow - CVE:CVE-2026-132825&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;7328f23691e44b07892ebd25b19210f1&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Cloudflare Free Managed Ruleset (Free plan)&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Block&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;Ruby - Heap Overflow - CVE:CVE-2026-132825&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;1afa543a1ed84893b01df04c34402c88&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Cloudflare Managed Ruleset (Pro, Business and Enterprise plans)&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Block&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;Ruby - Integer Overflow - GHSA-87fm-7w84-j2px&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;8660e37e86444f9f9267ba22e9855f05&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Cloudflare Free Managed Ruleset (Free plan)&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Block&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;Ruby - Integer Overflow - GHSA-87fm-7w84-j2px&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;6defac6a52334542adf4a162daf25922&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Cloudflare Managed Ruleset (Pro, Business and Enterprise plans)&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Block&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;On the Free plan, the Cloudflare Free Managed Ruleset runs automatically, so there is nothing to turn on. On paid plans, the rules are active wherever the Cloudflare Managed Ruleset is deployed. Because paid plans give you more control over how rulesets are deployed, the Cloudflare Managed Ruleset may not be active on every zone. We recommend checking its status to confirm that it is running. You can use the links in the &lt;a href="https://radar.cloudflare.com/zero-wire/ruby2shell#cloudflare-coverage"&gt;&lt;span style="text-decoration:underline"&gt;Zero Wire briefing&lt;/span&gt;&lt;/a&gt; to go straight to the rules in your dashboard.&lt;/p&gt;&lt;h3&gt;What the WAF cannot see&lt;/h3&gt;&lt;p&gt;A WAF can block an exploit when the malicious input arrives in an HTTP request that passes through Cloudflare. It cannot block every path to the vulnerable code:&lt;/p&gt;&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Traffic that bypasses Cloudflare.&lt;/strong&gt; Requests sent directly to your origin IP address, and traffic between internal services, never reach the WAF. Configure your origin to accept traffic only from Cloudflare, for example with &lt;a href="https://developers.cloudflare.com/tunnel/"&gt;&lt;span style="text-decoration:underline"&gt;Cloudflare Tunnel&lt;/span&gt;&lt;/a&gt; or &lt;a href="https://developers.cloudflare.com/ssl/origin-configuration/authenticated-origin-pull/"&gt;&lt;span style="text-decoration:underline"&gt;Authenticated Origin Pulls&lt;/span&gt;&lt;/a&gt;.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Other entry points into the same code.&lt;/strong&gt; Ruby code that changes the case of strings from email, file imports, message queues or background jobs can reach ruby2shell without an HTTP request.&lt;/li&gt;&lt;/ul&gt;&lt;h3&gt;Adding defense in depth with WAF attack score&lt;/h3&gt;&lt;p&gt;Memory corruption is usually only the first step. To run commands, an attacker still has to deliver a second-stage payload, such as shell commands or a reverse shell, and then interact with the compromised server. &lt;a href="https://developers.cloudflare.com/waf/detections/attack-score/"&gt;&lt;span style="text-decoration:underline"&gt;WAF attack score&lt;/span&gt;&lt;/a&gt; uses machine learning to score each request for remote code execution payloads, which helps catch exploit variations and post-exploitation traffic that signature-based rules can miss. Create a custom rule that blocks or challenges requests with &lt;code&gt;cf.waf.score.rce le 20&lt;/code&gt; on Enterprise plans, or &lt;code&gt;cf.waf.score.class eq &amp;quot;attack&amp;quot;&lt;/code&gt; on Business plans.&lt;/p&gt;&lt;h2&gt;Impact on Cloudflare infrastructure&lt;/h2&gt;&lt;p&gt;Cloudflare has patched its systems that use Ruby against ruby2shell. We have found no indication of compromise and continue to monitor.&lt;/p&gt;&lt;h2&gt;Patch now&lt;/h2&gt;&lt;p&gt;ruby2shell turns a one-byte miscalculation in string case conversion into a pre-authentication path to code execution in default Rails and Sinatra apps. With a public proof of concept expected within days, the window to patch is short. Here is what to do:&lt;/p&gt;&lt;ol&gt;&lt;li&gt;&lt;strong&gt;Check your WAF coverage.&lt;/strong&gt; On the Free plan, the ruby2shell rules are already blocking. On paid plans, confirm the Cloudflare Managed Ruleset is deployed and the rules have not been overridden.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Upgrade Ruby&lt;/strong&gt; to 3.3.14, 3.4.13 or 4.0.10 and restart every Ruby process, including background workers. Rebuild container images. Move applications on Ruby 3.2 or earlier to a supported series.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Update self-hosted products&lt;/strong&gt; that bundle Ruby, such as GitLab, GitHub Enterprise Server, Mastodon, OpenProject and Chatwoot, as each vendor releases a fix. Rebuild Discourse Docker installs now.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Inventory your runtimes.&lt;/strong&gt; The &lt;a href="https://radar.cloudflare.com/zero-wire/ruby2shell"&gt;&lt;span style="text-decoration:underline"&gt;Zero Wire briefing&lt;/span&gt;&lt;/a&gt; includes a prompt you can give an AI agent to find every affected Ruby runtime in your infrastructure.&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;Our WAF analysts will keep updating protections as new techniques appear. Follow the &lt;a href="https://developers.cloudflare.com/waf/change-log/changelog/"&gt;&lt;span style="text-decoration:underline"&gt;WAF changelog&lt;/span&gt;&lt;/a&gt; for rule updates.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>cloudflare-blog</ore:sourceId>
      <ore:sourceName>Cloudflare Blog</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://blog.cloudflare.com/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://blog.cloudflare.com/rss/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://blog.cloudflare.com/ruby2shell-waf-protection/</ore:originalUrl>
      <ore:upstreamId>01M7X91JJQ5CWGQ65DZBAHW4Q9</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hacker-news:a0899dd3bac28c7ccbcdfeba4744040a</id>
    <title>Show HN: OpenComputer – an open source alternative to Devin</title>
    <updated>2026-11-20T20:19:56Z</updated>
    <published>2026-11-20T20:19:56Z</published>
    <link rel="alternate" href="https://github.com/diggerhq/opencomputer" />
    <link rel="via" href="https://news.ycombinator.com/rss" />
    <category scheme="urn:ore-news:sources" term="hacker-news" label="Hacker News" />
    <author>
      <name>Hacker News</name>
    </author>
    <source>
      <id>urn:ore-news:source:hacker-news</id>
      <title>Hacker News</title>
      <link rel="alternate" href="https://news.ycombinator.com/" />
      <link rel="via" href="https://news.ycombinator.com/rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hacker-news</ore:sourceId>
      <ore:sourceName>Hacker News</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://news.ycombinator.com/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://news.ycombinator.com/rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://github.com/diggerhq/opencomputer</ore:originalUrl>
      <ore:upstreamId>https://github.com/diggerhq/opencomputer</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hacker-news:9f5c41972f0e6bdb3b9bffffd0280dd2</id>
    <title>Inkling 2 Mini</title>
    <updated>2026-11-20T20:12:19Z</updated>
    <published>2026-11-20T20:12:19Z</published>
    <link rel="alternate" href="https://thinkingmachines.ai/news/inkling-2-mini/" />
    <link rel="via" href="https://news.ycombinator.com/rss" />
    <category scheme="urn:ore-news:sources" term="hacker-news" label="Hacker News" />
    <author>
      <name>Hacker News</name>
    </author>
    <source>
      <id>urn:ore-news:source:hacker-news</id>
      <title>Hacker News</title>
      <link rel="alternate" href="https://news.ycombinator.com/" />
      <link rel="via" href="https://news.ycombinator.com/rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hacker-news</ore:sourceId>
      <ore:sourceName>Hacker News</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://news.ycombinator.com/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://news.ycombinator.com/rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://thinkingmachines.ai/news/inkling-2-mini/</ore:originalUrl>
      <ore:upstreamId>https://thinkingmachines.ai/news/inkling-2-mini/</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hacker-news:10fed32b83048e591815c44059e2dc6b</id>
    <title>And yet, it moves</title>
    <updated>2026-11-20T20:07:55Z</updated>
    <published>2026-11-20T20:07:55Z</published>
    <link rel="alternate" href="https://signoregalilei.com/2026/11/20/and-yet-it-moves/" />
    <link rel="via" href="https://news.ycombinator.com/rss" />
    <category scheme="urn:ore-news:sources" term="hacker-news" label="Hacker News" />
    <author>
      <name>Hacker News</name>
    </author>
    <source>
      <id>urn:ore-news:source:hacker-news</id>
      <title>Hacker News</title>
      <link rel="alternate" href="https://news.ycombinator.com/" />
      <link rel="via" href="https://news.ycombinator.com/rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hacker-news</ore:sourceId>
      <ore:sourceName>Hacker News</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://news.ycombinator.com/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://news.ycombinator.com/rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://signoregalilei.com/2026/11/20/and-yet-it-moves/</ore:originalUrl>
      <ore:upstreamId>https://signoregalilei.com/2026/11/20/and-yet-it-moves/</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:e39db928e772aca9d706dc2f35aeb502</id>
    <title>Amazon CloudWatch Observability EKS add-on now supports custom OpenTelemetry and Prometheus telemetry</title>
    <updated>2026-11-20T20:05:00Z</updated>
    <published>2026-11-20T20:05:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/cloudwatch-eks-addon-custom-telemetry/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;Today, Amazon CloudWatch announces support for your own application telemetry in the CloudWatch Observability EKS add-on. The CloudWatch agent you already run now accepts metrics, traces, and logs from your applications, so you don't deploy and operate a separate collector to get them into CloudWatch.&lt;/p&gt; 
&lt;p&gt;Applications instrumented with an OpenTelemetry SDK send to an OTLP endpoint that the agent serves on every node, on by default. Metrics arrive as CloudWatch metrics you query with PromQL, traces go to AWS X-Ray and Transaction Search, and logs go to CloudWatch Logs.&lt;/p&gt; 
&lt;p&gt;For Prometheus metrics, the agent scrapes the targets described by standard ServiceMonitor and PodMonitor objects, with no Prometheus operator to run and no change to your scrape configuration. Each team defines its own targets alongside its application rather than in one central add-on configuration. Label selectors let you choose which monitors CloudWatch scrapes.&lt;/p&gt; 
&lt;p&gt;Both sources carry the same Kubernetes, host, cloud, and service attributes the add-on applies to the pod they came from, so you can join application telemetry to your cluster metrics.&lt;/p&gt; 
&lt;p&gt;Custom telemetry is available in version 8.0.0 and later of the EKS add-on and Helm chart, in all AWS Regions where CloudWatch supports OpenTelemetry metrics. Telemetry is charged at the Amazon EKS OpenTelemetry ingestion rate of $0.08 per GB. For details, see Amazon CloudWatch &lt;a title="CloudWatch insights pricing" href="https://aws.amazon.com/cloudwatch/pricing/"&gt;insights pricing&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;To get started, see &lt;a title="CloudWatch EKS addon custom telemetry" href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/eks-observability-addon-custom-telemetry.html"&gt;Custom telemetry&lt;/a&gt; in the Amazon CloudWatch User Guide.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/cloudwatch-eks-addon-custom-telemetry/</ore:originalUrl>
      <ore:upstreamId>73a0ac376f9ac5409c2559aefcfb50e0589fe9e2</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hatena-bookmark-technology:32a6ea7ba08ae7982c6b048a90c5f11c</id>
    <title>Anthropicの人がClaudeと数学界のラスボス「リーマン予想」の証明を発見したらしい | ギズモード・ジャパン</title>
    <updated>2026-11-20T20:04:54Z</updated>
    <published>2026-11-20T20:04:54Z</published>
    <link rel="alternate" href="https://www.gizmodo.jp/article/2611-claude-riemann-hypothesis-proof/" />
    <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    <category scheme="urn:ore-news:sources" term="hatena-bookmark-technology" label="Hatena Bookmark Technology" />
    <author>
      <name>Hatena Bookmark Technology</name>
    </author>
    <source>
      <id>urn:ore-news:source:hatena-bookmark-technology</id>
      <title>Hatena Bookmark Technology</title>
      <link rel="alternate" href="https://b.hatena.ne.jp/hotentry/it" />
      <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hatena-bookmark-technology</ore:sourceId>
      <ore:sourceName>Hatena Bookmark Technology</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://b.hatena.ne.jp/hotentry/it</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://b.hatena.ne.jp/hotentry/it.rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://www.gizmodo.jp/article/2611-claude-riemann-hypothesis-proof/</ore:originalUrl>
      <ore:upstreamId>https://www.gizmodo.jp/article/2611-claude-riemann-hypothesis-proof/</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hacker-news:03497889f680fe858ef2463ceb432904</id>
    <title>DreamCoder: Coding harness and IDE from the author of Mastering Emacs</title>
    <updated>2026-11-20T20:03:59Z</updated>
    <published>2026-11-20T20:03:59Z</published>
    <link rel="alternate" href="https://www.masteringemacs.org/article/announcing-dreamcoder" />
    <link rel="via" href="https://news.ycombinator.com/rss" />
    <category scheme="urn:ore-news:sources" term="hacker-news" label="Hacker News" />
    <author>
      <name>Hacker News</name>
    </author>
    <source>
      <id>urn:ore-news:source:hacker-news</id>
      <title>Hacker News</title>
      <link rel="alternate" href="https://news.ycombinator.com/" />
      <link rel="via" href="https://news.ycombinator.com/rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hacker-news</ore:sourceId>
      <ore:sourceName>Hacker News</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://news.ycombinator.com/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://news.ycombinator.com/rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://www.masteringemacs.org/article/announcing-dreamcoder</ore:originalUrl>
      <ore:upstreamId>https://www.masteringemacs.org/article/announcing-dreamcoder</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hacker-news:9b20cd160e6856998a6b14204432fb53</id>
    <title>The stochastic parrots have apparently proved the Riemann Hypothesis</title>
    <updated>2026-11-20T20:03:07Z</updated>
    <published>2026-11-20T20:03:07Z</published>
    <link rel="alternate" href="https://scottaaronson.blog/?p=10344" />
    <link rel="via" href="https://news.ycombinator.com/rss" />
    <category scheme="urn:ore-news:sources" term="hacker-news" label="Hacker News" />
    <author>
      <name>Hacker News</name>
    </author>
    <source>
      <id>urn:ore-news:source:hacker-news</id>
      <title>Hacker News</title>
      <link rel="alternate" href="https://news.ycombinator.com/" />
      <link rel="via" href="https://news.ycombinator.com/rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hacker-news</ore:sourceId>
      <ore:sourceName>Hacker News</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://news.ycombinator.com/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://news.ycombinator.com/rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://scottaaronson.blog/?p=10344</ore:originalUrl>
      <ore:upstreamId>https://scottaaronson.blog/?p=10344</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:cloudflare-blog:3fe8ff2a1e33d2f4e2aae93fb2ec9896</id>
    <title>How Cloudflare WAF helps protect against phpAfterShell and other critical PHP flaws</title>
    <updated>2026-11-20T20:00:45Z</updated>
    <published>2026-11-20T20:00:45Z</published>
    <link rel="alternate" href="https://blog.cloudflare.com/phpaftershell-waf-protection/" />
    <link rel="via" href="https://blog.cloudflare.com/rss/" />
    <category scheme="urn:ore-news:sources" term="cloudflare-blog" label="Cloudflare Blog" />
    <author>
      <name>Cloudflare Blog</name>
    </author>
    <source>
      <id>urn:ore-news:source:cloudflare-blog</id>
      <title>Cloudflare Blog</title>
      <link rel="alternate" href="https://blog.cloudflare.com/" />
      <link rel="via" href="https://blog.cloudflare.com/rss/" />
    </source>
    <content type="html">&lt;p&gt;On November 19, 2026, the security research company depthfirst disclosed &lt;a href="https://depthfirst.com/research/phpaftershell"&gt;&lt;span style="text-decoration:underline"&gt;phpAfterShell (CVE-2026-126714)&lt;/span&gt;&lt;/a&gt;, a vulnerability in PHP&amp;#x27;s default file-based session handler that can lead to remote code execution. Under the Common Vulnerability Scoring System (CVSS) 4.0, it scores 9.2 out of 10 (Critical). The PHP project fixed it the same day in versions 8.2.36, 8.3.37, 8.4.28, 8.5.13, and 8.6.0. These releases fix 16 other security vulnerabilities, six of them also rated critical.&lt;/p&gt;&lt;p&gt;Cloudflare’s &lt;a href="https://developers.cloudflare.com/waf/"&gt;&lt;span style="text-decoration:underline"&gt;web application firewall (WAF)&lt;/span&gt;&lt;/a&gt; blocks known phpAfterShell attack patterns, including for customers on the Free plan. The protection comes from a PHP remote code execution rule we first deployed in October 2026 for the php2shell vulnerabilities. That rule already detected part of the phpAfterShell attack pattern before the vulnerability was disclosed, and on November 19 we updated its detection logic to cover phpAfterShell. The rule is part of both the Cloudflare Free Managed Ruleset and the Cloudflare Managed Ruleset, is enabled by default, and its default action is Block.&lt;/p&gt;&lt;p&gt;In the same WAF release, we added three new rules to the Cloudflare Managed Ruleset for paid plans: one for a request smuggling flaw in PHP-FPM (CVE-2026-129289), and two for flaws in PHP&amp;#x27;s SOAP extension (CVE-2026-15353 and CVE-2026-129506) that PHP fixed in the same releases. These rules are enabled by default with the Log action, because the request patterns they look for can also appear in legitimate traffic, and blocking by default could disrupt it. Customers can review matching requests in Security Events now and change the action to Block once they confirm the rules do not affect legitimate traffic.&lt;/p&gt;&lt;p&gt;The WAF is an additional layer of defense, not a replacement for the patch. Several of the critical flaws depend on server configuration or can be reached through paths a WAF does not see, and the only complete fix is to upgrade PHP and restart every worker. Our analysts continue to monitor attack activity and will update the rules as new techniques and variations appear. You can track rule changes in the &lt;a href="https://developers.cloudflare.com/waf/change-log/changelog/"&gt;&lt;span style="text-decoration:underline"&gt;WAF changelog&lt;/span&gt;&lt;/a&gt; and follow how the vulnerabilities develop in the dedicated &lt;a href="https://radar.cloudflare.com/zero-wire/php-november-2026-security-release-phpaftershell"&gt;&lt;span style="text-decoration:underline"&gt;Cloudflare Zero Wire briefing&lt;/span&gt;&lt;/a&gt;.&lt;/p&gt;&lt;p&gt;There appears to be no indication so far that these vulnerabilities have been exploited. As of November 19, 2026, none of the 17 vulnerabilities was listed in CISA&amp;#x27;s &lt;a href="https://www.cisa.gov/known-exploited-vulnerabilities-catalog"&gt;&lt;span style="text-decoration:underline"&gt;Known Exploited Vulnerabilities catalog&lt;/span&gt;&lt;/a&gt;, and no source we reviewed reports exploitation in the wild.&lt;/p&gt;&lt;h2&gt;What we know about phpAfterShell&lt;/h2&gt;&lt;p&gt;PHP stores session data in files by default. When an application calls session_start(), PHP reads the session file and deserializes its content into the $_SESSION array. When the request ends, PHP writes the updated session back to the same file.&lt;/p&gt;&lt;p&gt;phpAfterShell is triggered when that write is interrupted. The session file can then hold the beginning of the new session data followed by the end of the old one. On the next request, session_start() deserializes this mixed content. If an attacker controlled the old data, PHP can end up deserializing objects of the attacker&amp;#x27;s choice.&lt;/p&gt;&lt;p&gt;An attacker trying to exploit the flaw is likely to first search for a way to place controlled data in the session. PHP&amp;#x27;s &lt;a href="https://github.com/php/php-src/security/advisories/GHSA-fm2m-fjf5-v3cp"&gt;&lt;span style="text-decoration:underline"&gt;advisory&lt;/span&gt;&lt;/a&gt; names two:&lt;/p&gt;&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Session upload progress&lt;/strong&gt;, a PHP feature that writes information about a running file upload into the session. A remote client can use it to shape the stored data.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Applications that store large user-controlled strings in the session&lt;/strong&gt;.&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;According to PHP, code execution also requires an interruption at a useful point in the write and a suitable deserialization gadget chain in the application. depthfirst reports that it reached code execution without an application gadget by chaining a second, undisclosed memory-corruption bug in a PHP-native class. The sources we reviewed do not establish whether that second bug is fixed in the November 19 releases.&lt;/p&gt;&lt;p&gt;depthfirst says it discovered and reported phpAfterShell. The CVE record credits Leo Lin and Asahi as reporters.&lt;/p&gt;&lt;h3&gt;The other critical flaws&lt;/h3&gt;&lt;p&gt;The same releases fix six more critical vulnerabilities. Each one needs a specific configuration to be exploitable:&lt;/p&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;CVE&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;Component&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;Impact&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;Conditions&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;CVE-2026-129289&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;PHP-FPM&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;An unauthenticated attacker can smuggle a second FastCGI request into PHP-FPM and run PHP code as the worker.&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;A front end that reuses backend FastCGI connections (nginx with fastcgi_keep_conn on, Apache mod_proxy_fcgi with enablereuse=on, or HAProxy), an application path that opens php://input without reading it to the end, and the path of an existing PHP script.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;CVE-2026-115560&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Session serializer&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Object injection through a mismatch between session serializers. First covered in our php2shell briefing, now fixed.&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Session upload progress enabled. PHP widened the scope: applications, pools or command-line jobs that use different serializers and share a session store are affected.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;CVE-2026-129496&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Timezone cache&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Use-after-free that can crash a fresh worker and possibly run code. PHP demonstrated code execution locally with known memory addresses.&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Non-thread-safe builds where a startup diagnostic has been written to a PHP error log file.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;CVE-2026-129481&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Session shutdown&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Use-after-free, described by PHP as an incomplete fix for CVE-2026-109619. No code execution demonstrated.&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;PHP 8.3 and later.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;CVE-2026-129474&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Fatal error backtraces&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Use-after-free in magic method backtraces.&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;PHP 8.5 and later, where fatal error backtraces are enabled by default. Setting zend.exception_ignore_args=1, the php.ini-production default, blocks the demonstrated attack.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;CVE-2026-129182&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Fatal error backtraces&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Use-after-free. No code execution demonstrated.&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;PHP 8.5, specific path-level settings, and an Apache per-directory configuration or front end that produces an early diagnostic.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;h3&gt;Who is affected&lt;/h3&gt;&lt;p&gt;The vulnerable versions are PHP 8.2 before 8.2.36, 8.3 before 8.3.37, 8.4 before 8.4.28, 8.5 before 8.5.13, and the 8.6.0 release candidates. Whether a deployment is exposed depends on the conditions of each flaw.&lt;/p&gt;&lt;p&gt;PHP 8.1 and earlier are end-of-life. depthfirst says the official 7.4, 8.0 and 8.1 end-of-life mitigation branches are not affected by phpAfterShell, but PHP says CVE-2026-129289 was introduced in PHP 5.6.0 and that releases older than 8.2 may also be affected by CVE-2026-115560.&lt;/p&gt;&lt;p&gt;Linux distributions often backport fixes without changing the PHP version number. Check the full package version against your distribution&amp;#x27;s advisory.&lt;/p&gt;&lt;h2&gt;How Cloudflare WAF protects you&lt;/h2&gt;&lt;p&gt;PHP runs a large share of the web, often inside content management systems, plugins, and container images that teams do not update directly. Patching every PHP runtime takes time. Cloudflare WAF reduces your exposure while you patch.&lt;/p&gt;&lt;h3&gt;phpAfterShell: protection on every plan&lt;/h3&gt;&lt;p&gt;We released the original PHP remote code execution rules in an emergency release on October 21, 2026, after the php2shell vulnerabilities (CVE-2026-109618 and CVE-2026-109619) were disclosed. We extended them to CVE-2026-115560 on October 23 and refined them several times in the following weeks, based in part on reports from security researchers who took part in a &lt;a href="https://blog.cloudflare.com/php-ctf"&gt;&lt;span style="text-decoration:underline"&gt;PHP Capture the Flag (CTF) challenge&lt;/span&gt;&lt;/a&gt;.&lt;/p&gt;&lt;p&gt;phpAfterShell shares an attack technique with php2shell: an attacker plants serialized PHP data in session storage and waits for PHP to deserialize it. Because of that overlap, the existing rule already matched part of the phpAfterShell attack pattern before disclosure. On November 19, we updated the rule&amp;#x27;s detection logic to cover phpAfterShell and added CVE-2026-126714 to its description.&lt;/p&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;Rule description&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;Rule ID&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;Ruleset&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;Default action&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;PHP Remote Code Execution Attack (CVE-2026-109618, CVE-2026-109619, CVE-2026-115560, CVE-2026-126714) #6&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;19373a83abb840e18ab3ce5a7975ce1b&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Cloudflare Free Managed Ruleset (Free plan)&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Block&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;PHP Remote Code Execution Attack (CVE-2026-109618, CVE-2026-109619, CVE-2026-115560, CVE-2026-126714) #6&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;4148ae686fdb4d01be673fab9d9c073d&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Cloudflare Managed Ruleset (Pro, Business and Enterprise plans)&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Block&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;Free plan customers do not need to take any action. On paid plans, the rule is active wherever the Cloudflare Managed Ruleset is deployed. You can use the &lt;a href="https://radar.cloudflare.com/zero-wire/php-november-2026-security-release-phpaftershell#cloudflare-coverage"&gt;&lt;span style="text-decoration:underline"&gt;links in the Zero Wire briefing&lt;/span&gt;&lt;/a&gt; to go straight to the rules in your dashboard.&lt;/p&gt;&lt;h3&gt;New rules for PHP-FPM and SOAP flaws&lt;/h3&gt;&lt;p&gt;The three new rules are part of the Cloudflare Managed Ruleset (Ruleset ID efb7b8c949ac4650a09736fc376e9aee) and are available on Pro, Business and Enterprise plans.&lt;/p&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;Rule description&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;Rule ID&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;Default action&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;PHP-FPM - CVE:CVE-2026-129289&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;8ef1c34a424b4ccfa6f6fe186c6f42b2&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Log&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;PHP SOAP - CVE:CVE-2026-15353&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;5c5a9d6397e44837a3214b5ba54028d4&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Log&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;PHP SOAP - CVE:CVE-2026-129506&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;00a23de67a684876ba67c5d44521b819&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Log&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;To review their matches, go to Security &amp;gt; Analytics &amp;gt; Events and filter by rule ID. If the matches are not legitimate traffic, change the rule action to Block: go to Security &amp;gt; Settings, edit the Cloudflare Managed Ruleset, search for the CVE identifier and set the rule action to Block, or you can refer to the &lt;a href="https://radar.cloudflare.com/zero-wire/php-november-2026-security-release-phpaftershell#cloudflare-coverage"&gt;&lt;span style="text-decoration:underline"&gt;links in the Zero Wire briefing&lt;/span&gt;&lt;/a&gt; to go straight to the rules configuration.&lt;/p&gt;&lt;h3&gt;What the WAF cannot see&lt;/h3&gt;&lt;p&gt;A WAF can block an exploit when the malicious data arrives in an HTTP request that passes through Cloudflare. It cannot block every path to these vulnerabilities, including:&lt;/p&gt;&lt;ul&gt;&lt;li&gt;&lt;strong&gt;The deserialization step.&lt;/strong&gt; phpAfterShell&amp;#x27;s final step happens inside PHP, when it reads a corrupted session file. The WAF can block the requests that plant the payload, not the read itself.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Session data from other sources.&lt;/strong&gt; If an application copies user-controlled data into the session from a database, a queue or an upstream API, that data may never cross the WAF in a recognizable form.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Flaws triggered by server state.&lt;/strong&gt; CVE-2026-129496, CVE-2026-129481, CVE-2026-129474 and CVE-2026-129182 depend on error logs, diagnostics and worker lifecycle. They do not have dedicated WAF rules, and the patch and the configuration changes below are the way to address them.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Traffic that bypasses Cloudflare.&lt;/strong&gt; This includes internal traffic between services and PHP-FPM listeners exposed directly to a network.&lt;/li&gt;&lt;/ul&gt;&lt;h3&gt;Adding defense in depth with WAF attack score&lt;/h3&gt;&lt;p&gt;&lt;a href="https://developers.cloudflare.com/waf/detections/attack-score/"&gt;&lt;span style="text-decoration:underline"&gt;WAF attack score&lt;/span&gt;&lt;/a&gt; adds a machine learning layer that scores each request for attack payloads. It is available on Business plans (cf.waf.score.class) and, with a dedicated remote code execution sub-score (cf.waf.score.rce) along with an overall score (cf.waf.score), on Enterprise plans.&lt;/p&gt;&lt;p&gt;Attack score complements the managed rules. It will not recognize every serialized object or smuggled FastCGI record on its own, but a working exploit chain usually needs more than one request, and the later stages carry payloads the model is trained to score:&lt;/p&gt;&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Second-stage payloads.&lt;/strong&gt; Once an attacker can run code, they still need to send commands: shell execution primitives (/bin/sh -c, system(), passthru()), PHP code evaluation (eval(), assert()) or reverse-shell strings in headers, query parameters or request bodies.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Webshell traffic.&lt;/strong&gt; Attackers often drop a small PHP webshell after the initial compromise. Requests that pass operating system commands to that webshell remain visible to attack score.&lt;/li&gt;&lt;/ul&gt;&lt;h2&gt;Deploy protections and patch&lt;/h2&gt;&lt;p&gt;You can find more information on how to deploy managed rules and attack score in &lt;a href="https://developers.cloudflare.com/waf/get-started/"&gt;&lt;span style="text-decoration:underline"&gt;our WAF guide&lt;/span&gt;&lt;/a&gt;. In short:&lt;/p&gt;&lt;ol&gt;&lt;li&gt;&lt;strong&gt;Check that phpAfterShell protection is active.&lt;/strong&gt; On the Free plan, no action is needed. On paid plans, make sure the Cloudflare Managed Ruleset is deployed and that the PHP Remote Code Execution Attack #6 rule is set to Block.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Review the new rules and switch them to Block.&lt;/strong&gt; The CVE-2026-129289, CVE-2026-15353 and CVE-2026-129506 rules are in Log mode by default. Review their matches in Security Events, then change their action to Block.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Layer &lt;a href="https://developers.cloudflare.com/waf/get-started/#2-create-custom-rule-based-on-waf-attack-score"&gt;&lt;span style="text-decoration:underline"&gt;attack score&lt;/span&gt;&lt;/a&gt;.&lt;/strong&gt; Create a custom rule that blocks or challenges requests with a low remote code execution score, for example cf.waf.score.rce le 20 on Enterprise plans, or cf.waf.score.class eq &amp;quot;attack&amp;quot; on Business plans.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Upgrade PHP.&lt;/strong&gt; Move to 8.2.36, 8.3.37, 8.4.28, 8.5.13 or 8.6.0. Rebuild container images and restart the PHP-FPM master or Apache so every worker loads the new binary, then verify the version that serves web requests. After upgrading, check that no php.ini, FPM pool or virtual host still sets session.upload_progress.enabled=1, because an explicit setting overrides the new default.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Apply interim mitigations if you cannot upgrade right away.&lt;/strong&gt; Set session.upload_progress.enabled=0 and limit the untrusted data you store in sessions. Turn off FastCGI connection reuse. On PHP 8.5, set fatal_error_backtraces=0. Fix configuration errors that produce PHP startup warnings, or send PHP errors to syslog instead of a file. Keep PHP-FPM listeners off untrusted networks. These steps reduce exposure; they do not fix the flaws.&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;For a prompt you can give an AI agent to inventory your PHP deployments and check each one against all seven critical CVEs, see the &lt;a href="https://radar.cloudflare.com/zero-wire/php-november-2026-security-release-phpaftershell"&gt;&lt;span style="text-decoration:underline"&gt;phpAfterShell page on Cloudflare Zero Wire&lt;/span&gt;&lt;/a&gt;.&lt;/p&gt;&lt;h2&gt;Update every PHP runtime now&lt;/h2&gt;&lt;p&gt;phpAfterShell turns an interrupted file write in PHP&amp;#x27;s default session handler into a path to code execution, and it arrived in the same release as six other critical flaws. With technical details now public, we expect exploit attempts to follow. Cloudflare WAF blocks known phpAfterShell attack patterns for every customer, including the Free plan, and paid plans have new rules for the PHP-FPM and SOAP flaws. The fix is still to upgrade PHP and restart the services that use it.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>cloudflare-blog</ore:sourceId>
      <ore:sourceName>Cloudflare Blog</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://blog.cloudflare.com/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://blog.cloudflare.com/rss/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://blog.cloudflare.com/phpaftershell-waf-protection/</ore:originalUrl>
      <ore:upstreamId>01M7X76K1JK00SF9K4YN83WANQ</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:f44c2783ea3faff857b42efccd6c4552</id>
    <title>Amazon Transcribe announces a synchronous transcription API</title>
    <updated>2026-11-20T20:00:00Z</updated>
    <published>2026-11-20T20:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/amazon-transcribe-sync-api/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;Amazon Transcribe now offers a synchronous transcription API, &lt;b&gt;&lt;i&gt;TranscribeAudio&lt;/i&gt;&lt;/b&gt;. Send a complete audio file in a single request and get the full transcript back in the same response. There is no job to start, no status to poll, no connection to manage.&amp;nbsp;The transcripts are as accurate as Amazon Transcribe batch transcription, so you can add fast, accurate speech-to-text to interactive applications such as voice assistants, agent-assist tools and on-demand "transcribe this clip" features.&lt;/p&gt; 
&lt;p&gt;The synchronous API supports the Amazon Transcribe features you already use, including:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;Word-level timestamps and smart formatting for numbers, dates, currency and phone numbers&lt;/li&gt; 
 &lt;li&gt;Automatic language identification&lt;/li&gt; 
 &lt;li&gt;Speaker diarization, and channel identification for up to two channels&lt;/li&gt; 
 &lt;li&gt;Custom vocabulary and vocabulary filtering, which you can provide directly in the request with no setup step&lt;/li&gt; 
 &lt;li&gt;PII redaction&lt;/li&gt; 
&lt;/ul&gt; 
&lt;p&gt;Send audio inline (up to 25 MB) or from Amazon S3 (up to 500 MB), 0.5 seconds to 1 hour long, in WAV, MP3, FLAC, M4A, MP4, Ogg, WebM or AMR format. The transcript comes back in the response, or Transcribe can write it to an S3 location you choose. Pricing is $0.0070 per minute of audio, billed per second, with speaker diarization, language identification, custom vocabulary and channel identification included. Two-channel audio is billed once on file duration. PII redaction is available as an add-on.&lt;/p&gt; 
&lt;p&gt;Supports English, Spanish, French, Italian, German, Japanese, Portuguese, Korean and Chinese (Simplified, Traditional and Hong Kong).&amp;nbsp;Available in US East (N. Virginia, Ohio), US West (Oregon), Canada (Central), Europe (Ireland, London, Frankfurt), Asia Pacific (Mumbai, Singapore, Sydney, Tokyo, Seoul) and South America (São Paulo), with PII redaction available in all stated Regions except South America (São Paulo).&lt;/p&gt; 
&lt;p&gt;To get started, see&amp;nbsp;&lt;a href="https://docs.aws.amazon.com/transcribe/latest/APIReference/API_Operations_Amazon_Transcribe_Service.html" target="_blank" rel="noopener noreferrer"&gt;Amazon Transcribe API Reference&lt;/a&gt; and the &lt;a href="https://aws.amazon.com/transcribe/pricing/"&gt;Amazon Transcribe pricing page&lt;/a&gt;.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/amazon-transcribe-sync-api/</ore:originalUrl>
      <ore:upstreamId>6ff37aa30a29dd2099529ac7c6c41375f6baee8b</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:aea9939d3f8a4c52db77bab204372be9</id>
    <title>Amazon DynamoDB vector search now supports new inline filter operators</title>
    <updated>2026-11-20T20:00:00Z</updated>
    <published>2026-11-20T20:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/dynamodb-vector-filters/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;Amazon DynamoDB vector search inline filters now support range comparisons, value lists, and logical operators in addition to the equality operator, so you can narrow a vector search to exactly the items you want. You can now filter on numeric ranges such as price, rating, or publish date, match an attribute against a list of values, check whether an attribute exists, and combine conditions with OR and NOT.&amp;nbsp;Amazon DynamoDB vector indexes store vector embeddings alongside your operational data, and the SearchVectors API returns the items whose embeddings are most similar to your query vector.&lt;/p&gt; 
&lt;p&gt;The search condition expression in a SearchVectors request now accepts the comparison operators &amp;lt;, &amp;lt;=, &amp;gt;, &amp;gt;=, and BETWEEN on Number attributes, the IN operator, the attribute_exists and attribute_not_exists functions, and the logical operators AND, OR, and NOT. DynamoDB applies the filter during the search, so every result it returns matches. For example, a retail application can return the products most similar to a shopper's query within a price range and a set of brands, and a retrieval-augmented generation application can limit results to selected document categories published after a given date.&lt;/p&gt; 
&lt;p&gt;The new operators are available in all AWS Regions where DynamoDB vector search is available.&lt;/p&gt; 
&lt;p&gt;To learn more, see &lt;a href="https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/VectorSearchFilterReference.html" target="_blank"&gt;vector search&lt;/a&gt; in the Amazon DynamoDB Developer Guide, or visit the &lt;a href="https://aws.amazon.com/dynamodb/" target="_blank"&gt;Amazon DynamoDB&lt;/a&gt; page.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/dynamodb-vector-filters/</ore:originalUrl>
      <ore:upstreamId>f890aab8066b55b22b87b5745573585aca70265d</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:d37211dbf60827d818c1ba058131b520</id>
    <title>Amazon CloudWatch Observability EKS add-on now supports telemetry filtering</title>
    <updated>2026-11-20T19:52:00Z</updated>
    <published>2026-11-20T19:52:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/cloudwatch-eks-otel-addon-filtering/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;Today, Amazon CloudWatch announces telemetry filtering for the CloudWatch Observability EKS add-on, so you can stop paying to ingest telemetry you don't use.&lt;/p&gt; 
&lt;p&gt;You can now set cluster-wide include and exclude lists for namespaces, metric names, and pod and node labels. Exclude the non-production namespaces you don't monitor, drop high-cardinality metrics by name, and keep only the labels you group by rather than every label on every resource. Because ingestion is billed per GB, collecting less lowers what you pay, and you can adjust filters with a single add-on configuration update as your clusters change.&lt;/p&gt; 
&lt;p&gt;Telemetry filtering is available in version 8.0.0 and later of the EKS add-on and Helm chart, in all AWS Regions where CloudWatch supports OpenTelemetry metrics. Telemetry sent through the add-on is charged at the Amazon EKS OpenTelemetry ingestion rate of $0.08 per GB. For details, see Amazon CloudWatch &lt;a title="CloudWatch EKS pricing" href="https://aws.amazon.com/cloudwatch/pricing/"&gt;insights pricing&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;To get started, see Amazon CloudWatch Observability EKS add-on in the &lt;a title="CloudWatch EKS OTel Container Insights" href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/container-insights-eks-otel.html"&gt;Amazon CloudWatch User Guide&lt;/a&gt;.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/cloudwatch-eks-otel-addon-filtering/</ore:originalUrl>
      <ore:upstreamId>4ef0a2563f316986a96d6b1482b11cbcfffead48</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hacker-news:466ab6f0b2b1b77cf01e868f5137a1dd</id>
    <title>Winedroid – run Android apps without Android (WASM demo)</title>
    <updated>2026-11-20T19:30:16Z</updated>
    <published>2026-11-20T19:30:16Z</published>
    <link rel="alternate" href="https://winedroid.soham.sh/demo/" />
    <link rel="via" href="https://news.ycombinator.com/rss" />
    <category scheme="urn:ore-news:sources" term="hacker-news" label="Hacker News" />
    <author>
      <name>Hacker News</name>
    </author>
    <source>
      <id>urn:ore-news:source:hacker-news</id>
      <title>Hacker News</title>
      <link rel="alternate" href="https://news.ycombinator.com/" />
      <link rel="via" href="https://news.ycombinator.com/rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hacker-news</ore:sourceId>
      <ore:sourceName>Hacker News</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://news.ycombinator.com/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://news.ycombinator.com/rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://winedroid.soham.sh/demo/</ore:originalUrl>
      <ore:upstreamId>https://winedroid.soham.sh/demo/</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:d4fbbde37117467b4ff1a677a5efbaff</id>
    <title>Amazon SageMaker JumpStart now offers a model leaderboard to compare models on quality, speed, and cost</title>
    <updated>2026-11-20T19:27:00Z</updated>
    <published>2026-11-20T19:27:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/1/sagemaker-jumpstart-model-leaderboard/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;Amazon SageMaker JumpStart now offers a model leaderboard in Amazon SageMaker Studio. You can use it to compare foundation models side by side on throughput, latency, and cost, and then deploy or customize the model that fits your workload.&lt;/p&gt; 
&lt;p&gt;Comparing models has usually meant reading model cards one at a time and relying on benchmark scores that different sources published under different conditions. The JumpStart leaderboard puts consistent measurements in one view. AWS evaluates every model on three reasoning benchmarks, BIG-Bench Hard, GPQA Diamond, and MMLU-Pro, using the same evaluation setup for each model. AWS also measures time to first token, throughput, and instance cost on SageMaker for each JumpStart deployment configuration. You can use all of the filters already available for JumpStart models, such as model provider, license, and input and output modality, to narrow the list. You can also choose a use case profile and an optimization goal (balanced, cost, latency, or throughput) to see the metrics for the configuration you plan to deploy. At launch, the leaderboard covers more than 70 LLMs from providers including Meta, Google, Qwen, IBM, and Arcee.&lt;/p&gt; 
&lt;p&gt;The JumpStart model leaderboard is available at no additional charge in all AWS commercial Regions where Amazon SageMaker Studio is available. To get started, &lt;a href="https://console.aws.amazon.com/sagemaker/home#/launch?source=jumpstart&amp;amp;page=jumpstart"&gt;open SageMaker JumpStart&lt;/a&gt; in SageMaker Studio and choose the Leaderboard view. To learn more, see &lt;a href="https://docs.aws.amazon.com/sagemaker/latest/dg/jumpstart-foundation-models-leaderboard-benchmarks.html"&gt;JumpStart leaderboard methodology&lt;/a&gt; and read the &lt;a href="https://aws.amazon.com/blogs/machine-learning/introducing-the-amazon-sagemaker-jumpstart-model-leaderboard/"&gt;launch blog post&lt;/a&gt;.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/1/sagemaker-jumpstart-model-leaderboard/</ore:originalUrl>
      <ore:upstreamId>9726e8c0deb6ac49490db469347a3bdd3dbb9d86</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hatena-bookmark-technology:af34422a21f0e4c104fb164df089c9a4</id>
    <title>[アップデート] AWS STS の GetScopedCredentials で権限と有効期間を絞った認証情報を作ってみた | DevelopersIO</title>
    <updated>2026-11-20T19:26:02Z</updated>
    <published>2026-11-20T19:26:02Z</published>
    <link rel="alternate" href="https://dev.classmethod.jp/articles/aws-sts-get-scoped-credentials/" />
    <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    <category scheme="urn:ore-news:sources" term="hatena-bookmark-technology" label="Hatena Bookmark Technology" />
    <author>
      <name>Hatena Bookmark Technology</name>
    </author>
    <source>
      <id>urn:ore-news:source:hatena-bookmark-technology</id>
      <title>Hatena Bookmark Technology</title>
      <link rel="alternate" href="https://b.hatena.ne.jp/hotentry/it" />
      <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hatena-bookmark-technology</ore:sourceId>
      <ore:sourceName>Hatena Bookmark Technology</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://b.hatena.ne.jp/hotentry/it</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://b.hatena.ne.jp/hotentry/it.rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://dev.classmethod.jp/articles/aws-sts-get-scoped-credentials/</ore:originalUrl>
      <ore:upstreamId>https://dev.classmethod.jp/articles/aws-sts-get-scoped-credentials/</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hatena-bookmark-technology:d9893aee3f572611aa51c3522853a46c</id>
    <title>Ruby の脆弱性 CVE-2026-132825(Ruby2Shell)についてまとめてみた - piyolog</title>
    <updated>2026-11-20T19:18:28Z</updated>
    <published>2026-11-20T19:18:28Z</published>
    <link rel="alternate" href="https://piyolog.hatenadiary.jp/entry/2026/11/20/224814" />
    <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    <category scheme="urn:ore-news:sources" term="hatena-bookmark-technology" label="Hatena Bookmark Technology" />
    <author>
      <name>Hatena Bookmark Technology</name>
    </author>
    <source>
      <id>urn:ore-news:source:hatena-bookmark-technology</id>
      <title>Hatena Bookmark Technology</title>
      <link rel="alternate" href="https://b.hatena.ne.jp/hotentry/it" />
      <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hatena-bookmark-technology</ore:sourceId>
      <ore:sourceName>Hatena Bookmark Technology</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://b.hatena.ne.jp/hotentry/it</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://b.hatena.ne.jp/hotentry/it.rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://piyolog.hatenadiary.jp/entry/2026/11/20/224814</ore:originalUrl>
      <ore:upstreamId>https://piyolog.hatenadiary.jp/entry/2026/11/20/224814</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:02efbb36e55421ced4183c0309e3dcd3</id>
    <title>AWS Partner Central Agents now help partners create and manage Partner Central and Marketplace support cases</title>
    <updated>2026-11-20T19:07:00Z</updated>
    <published>2026-11-20T19:07:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/partner-central-agents-support/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;AWS Partner Central Agents now help AWS Partners create and manage AWS Partner Central and AWS Marketplace support cases in one place. The agents are available 24/7 and draw on Partner Central account details and authoritative, partner-specific knowledge from AWS to resolve most inquiries instantly. If a inquiry needs a support engineer, the agents will gather details and create a case. This reduces the time partners spend looking for help, and gives support teams the context they need to resolve cases faster.&lt;/p&gt; 
&lt;p&gt;Partners can handle a case from start to finish in one chat, with the full record in AWS Support Center. To create a case, partners can start describing their issue to AWS Partner Central Agents or use the prompt "get support." The agents gather additional details necessary to resolve the case, set the category, and draft the description. Partners review and submit the case, and the agents route the case to the right support team. In the same chat, partners can view case communications, track progress, post replies, and add attachments. With this launch, Partner Central and AWS Marketplace cases also move to AWS Support Center. There, partners can view the full case history and translate support correspondence into Chinese, French, German, Japanese, Korean, Portuguese, and Spanish.&lt;/p&gt; 
&lt;p&gt;The new support experience is available today to all AWS Partners and AWS Marketplace sellers in the &lt;a href="https://us-east-1.console.aws.amazon.com/partnercentral/support?region=us-east-1"&gt;AWS Partner Central console&lt;/a&gt; and through the AWS Partner Central Agents MCP server. With the MCP server, partners can bring the support experience into tools such as Kiro, AWS Quick, CRM systems, and other AI clients. To learn more, see &lt;a href="https://docs.aws.amazon.com/partner-central/latest/getting-started/getting-support.html"&gt;Getting support in AWS Partner Central&lt;/a&gt;, &lt;a href="https://docs.aws.amazon.com/marketplace/latest/userguide/getting-support.html"&gt;Getting support for AWS Marketplace&lt;/a&gt;, and &lt;a href="https://docs.aws.amazon.com/partner-central/latest/developer-guide/mcp-getting-started.html"&gt;Getting started with the Partner Central Agents MCP server&lt;/a&gt;.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/partner-central-agents-support/</ore:originalUrl>
      <ore:upstreamId>609b10847d86c65781c1c54d20c4bc92f80e87a8</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hatena-bookmark-technology:4bf944f0a450ea0ced0421b270080d94</id>
    <title>Unforced Euler singularity, unforced Navier-Stokes singularity, and the Generalized Riemann Hypothesis</title>
    <updated>2026-11-20T19:03:01Z</updated>
    <published>2026-11-20T19:03:01Z</published>
    <link rel="alternate" href="https://terrytao.wordpress.com/2026/11/20/unforced-euler-singularity-unforced-navier-stokes-singularity-and-the-generalized-riemann-hypothesis/" />
    <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    <category scheme="urn:ore-news:sources" term="hatena-bookmark-technology" label="Hatena Bookmark Technology" />
    <author>
      <name>Hatena Bookmark Technology</name>
    </author>
    <source>
      <id>urn:ore-news:source:hatena-bookmark-technology</id>
      <title>Hatena Bookmark Technology</title>
      <link rel="alternate" href="https://b.hatena.ne.jp/hotentry/it" />
      <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hatena-bookmark-technology</ore:sourceId>
      <ore:sourceName>Hatena Bookmark Technology</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://b.hatena.ne.jp/hotentry/it</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://b.hatena.ne.jp/hotentry/it.rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://terrytao.wordpress.com/2026/11/20/unforced-euler-singularity-unforced-navier-stokes-singularity-and-the-generalized-riemann-hypothesis/</ore:originalUrl>
      <ore:upstreamId>https://terrytao.wordpress.com/2026/11/20/unforced-euler-singularity-unforced-navier-stokes-singularity-and-the-generalized-riemann-hypothesis/</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:767ae53b51f2c81a5d10db27a35a6301</id>
    <title>Spend limits in the new AWS experience now support SMS alerts</title>
    <updated>2026-11-20T19:03:00Z</updated>
    <published>2026-11-20T19:03:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/sms/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;Builders using the new AWS experience on the Paid plan can now receive spend limit alerts by text message (SMS), alongside existing email notifications. A spend limit sets the maximum monthly cost for a project. Notifications are sent as a project approaches its limit, and when a project reaches its limit, AWS automatically pauses it. SMS gives builders a second way to stay informed about their project costs.&lt;/p&gt; 
&lt;p&gt;Email alerts can go unnoticed when builders are away from their inbox, leaving little time to respond before a project is paused. SMS alerts close this gap with a text message when a project's actual costs reach 90% of its spend limit, so builders have time to act, such as raising the limit or stopping resources they don't need.&lt;/p&gt; 
&lt;p&gt;To turn on SMS alerts, verify your mobile phone number in AWS Settings and turn on text alerts for spend limits. Text alerts are only sent to verified numbers, and you can opt out at any time. SMS alerts for spend limits are available at no additional charge for US phone numbers, including Puerto Rico, Guam, the US Virgin Islands, and American Samoa.&lt;/p&gt; 
&lt;p&gt;To learn more, see &lt;a href="https://docs.aws.amazon.com/accounts/latest/reference/create-spend-limit.html"&gt;Create a spend limit in AWS Settings&lt;/a&gt;, the &lt;a href="https://docs.aws.amazon.com/accounts/latest/reference/sign-in-new.html"&gt;AWS Account Management Reference Guide&lt;/a&gt;, or &lt;a href="https://aws.amazon.com/start-here/"&gt;Get started with AWS&lt;/a&gt;.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/sms/</ore:originalUrl>
      <ore:upstreamId>04af247eb3bca136b92ef248b9b31e838b7ae15e</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:f1549d3244e3a4117e06a416a3ad8623</id>
    <title>Amazon S3 Vectors raises the filterable metadata limit to 40 KB per vector</title>
    <updated>2026-11-20T19:00:00Z</updated>
    <published>2026-11-20T19:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/amazon-s3-vectors-raises-filterable-metadata-40kb-per-vector/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;Amazon S3 Vectors now supports up to 40 KB of filterable metadata per vector, up from 2 KB. You can attach and filter on more attributes per vector, such as category, permissions, timestamps, and descriptive tags, so your retrieval-augmented generation (RAG), agentic, and semantic-search applications can narrow results by more of the fields that matter to them.&lt;/p&gt; 
&lt;p&gt;S3 Vectors provides native support to store and query vectors in Amazon S3, delivering purpose-built, cost-optimized vector storage and query at billion-vector scale. With this launch, indexes in new vector buckets support the higher limit by default, with no change to how you write vectors with PutVectors or run filtered queries with QueryVectors. To use the higher limit on an existing index, update it in place to enhanced index mode with the UpdateIndexMode API.&lt;/p&gt; 
&lt;p&gt;The higher filterable metadata limit is available at no additional cost in all AWS Regions where Amazon S3 Vectors is available. To get started, use the AWS CLI, AWS SDKs, or the Amazon S3 console. To learn more, visit the Amazon S3 Vectors &lt;a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-vectors-metadata-filtering.html" target="_blank" rel="noopener noreferrer"&gt;documentation&lt;/a&gt;.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/amazon-s3-vectors-raises-filterable-metadata-40kb-per-vector/</ore:originalUrl>
      <ore:upstreamId>1d988d2199dd73845fd88dbea0f3a4940d1a2766</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:accb7991183b949eaa65bfb67d2e373c</id>
    <title>AWS Glue Data Catalog introduces data quality monitoring for catalogs and databases</title>
    <updated>2026-11-20T19:00:00Z</updated>
    <published>2026-11-20T19:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/glue-catalog-data-quality-monitoring/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;AWS Glue Data Catalog introduces data quality monitoring for catalogs and databases, powered by AWS Glue Data Quality, which profiles and evaluates your tables at catalog scale from a single configuration. You define data quality checks once for a catalog, a database, or a single table, and AWS Glue Data Quality evaluates every table in scope, including tables added later, on the cadence you choose. Quality issues surface as data changes, without per-table setup or manual runs, which helps keep bad data from reaching downstream consumers.&lt;/p&gt; 
&lt;p&gt;You can use built-in profiling options that AWS Glue provides for common baseline statistics or provide your own Data Quality Definition Language (DQDL) ruleset with analyzers, rules, or both to hold every table in a database to the same quality standards. You have the flexibility to run evaluations once when you create the configuration or set up triggers, so evaluations run on a schedule or whenever table metadata changes, including every Apache Iceberg commit. After three runs on a table, AWS Glue Data Quality flags anomalous statistics that drift outside expected bounds, surfacing changes that no rule covers. Results are accessible through the existing AWS Glue Data Quality APIs, or you can opt-in to write them to Apache Iceberg tables in the AWS Glue Data Catalog or to Amazon S3.&lt;/p&gt; 
&lt;p&gt;Data quality monitoring for catalogs and databases in AWS Glue Data Catalog is available in all AWS Commercial, AWS GovCloud (US), and AWS China regions.&lt;/p&gt; 
&lt;p&gt;To get started, create a data quality configuration by using the AWS CLI, API, or SDKs, which support built-in profiling and custom DQDL rulesets at the catalog, database, or table level. In Amazon SageMaker Unified Studio, you can turn on profiling for a catalog or database from the catalog page. To learn more, visit the &lt;a href="https://docs.aws.amazon.com/glue/latest/dg/data-quality-catalog-monitoring.html" target="_blank" rel="noopener noreferrer"&gt;AWS Glue Data Quality documentation&lt;/a&gt; and the &lt;a href="https://docs.aws.amazon.com/sagemaker-unified-studio/latest/userguide/dq-profile-catalogs-databases.html"&gt;Amazon SageMaker Unified Studio documentation&lt;/a&gt;.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/glue-catalog-data-quality-monitoring/</ore:originalUrl>
      <ore:upstreamId>c311750b5abf42ae38337e2a8e418a0372e79fe4</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:16e27bfff35ea1ad9fc6c9a78a23c804</id>
    <title>AWS Lambda now supports a batch size of up to 10,000 messages for Amazon SQS FIFO queues</title>
    <updated>2026-11-20T19:00:00Z</updated>
    <published>2026-11-20T19:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/aws-lambda-10K-batch-size-SQSFIFO/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;AWS Lambda now supports a batch size of up to 10,000 messages for &lt;a href="https://aws.amazon.com/sqs/"&gt;Amazon Simple Queue Service&lt;/a&gt; (Amazon SQS) FIFO queue event source mappings (ESMs) in &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/with-sqs.html#sqs-provisioned-mode"&gt;provisioned mode&lt;/a&gt;, up from 10 messages previously. With larger batches, you can process high-volume, ordered workloads such as financial transactions, order processing, and inventory updates with fewer invocations and higher throughput. Lambda continues to preserve message ordering within each message group.&lt;/p&gt; 
&lt;p&gt;Customers use SQS FIFO queues with Lambda to build event-driven applications that need strict message ordering and deduplication. With provisioned mode for SQS ESMs, you can use throughput controls to set a minimum and maximum number of event pollers to&amp;nbsp;meet strict performance requirements. Previously, provisioned mode customers who needed higher throughput for SQS FIFO queues were limited by the maximum batch size of 10 messages. This required them to scale out invocations or add custom buffering logic, which added operational overhead and cost. With this launch, you can set a batch size of up to 10,000 messages and a batching window of up to 300 seconds for FIFO queues, so you can process large volumes of ordered messages in fewer invocations without re-architecting your applications.&lt;/p&gt; 
&lt;p&gt;This feature is available for SQS FIFO ESMs in provisioned mode in all &lt;a href="https://builder.aws.com/build/capabilities"&gt;AWS commercial Regions.&lt;/a&gt; You can configure the batch size and the batching window when you create new ESMs or update existing ESMs by using the Lambda console, AWS CLI, AWS SDKs, AWS CloudFormation, AWS CDK, or AWS SAM. You can also use coding assistants such as Kiro, Claude Code, or Codex with the Agent Toolkit for AWS. To learn more, visit the &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/with-sqs.html"&gt;AWS Lambda Developer Guide&lt;/a&gt; and the &lt;a href="https://aws.amazon.com/lambda/pricing/"&gt;AWS Lambda pricing&lt;/a&gt;.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/aws-lambda-10K-batch-size-SQSFIFO/</ore:originalUrl>
      <ore:upstreamId>ba91fbdb4176dfd00bb2222542142c427f225b22</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:1230665ff5c2df1d86ac05be5e295c6c</id>
    <title>AWS Lambda now provides cost optimization recommendations for Event Functions</title>
    <updated>2026-11-20T19:00:00Z</updated>
    <published>2026-11-20T19:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/aws-lambda-cost-optimization-recommendations/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;AWS Lambda now provides cost optimization recommendations for &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/lambda-functions-chapter.html"&gt;Event Functions&lt;/a&gt; in &lt;a href="https://aws.amazon.com/premiumsupport/technology/trusted-advisor/"&gt;AWS Trusted Advisor&lt;/a&gt;.&amp;nbsp;These recommendations identify on-demand functions&amp;nbsp;where moving to &lt;a href="https://aws.amazon.com/lambda/lambda-managed-instances/"&gt;Lambda Managed Instances&lt;/a&gt; (LMI) is estimated to reduce costs, and provide configuration guidance for running on LMI. With&amp;nbsp;these recommendations, you can lower your Lambda costs by focusing your efforts on the functions with the greatest estimated savings.&lt;/p&gt; 
&lt;p&gt;LMI&amp;nbsp;lets you run Lambda functions on Amazon EC2 instances while maintaining the operational simplicity of Lambda. With LMI, you can access specialized compute configurations and drive cost efficiency through EC2 pricing options such as Savings Plans and Reserved Instances, without managing infrastructure. Previously, to determine whether a function was a good fit for LMI, you had to analyze its invocation patterns, estimate LMI costs, and select the right instance type and memory-to-vCPU ratio yourself. This manual process added overhead and delayed savings. With this launch, Lambda automatically analyzes the invocation patterns, duration, and resource utilization of your high-volume Event Functions and recommends those where LMI is estimated to reduce costs. Estimates are based on a simulation of each function's invocation patterns, using public&amp;nbsp;Lambda pricing and Amazon EC2 On-Demand pricing.&amp;nbsp;Each recommendation includes the function ARN,&amp;nbsp;the recommended EC2 instance type and memory-to-vCPU ratio, the estimated current&amp;nbsp;cost, the estimated LMI cost, and the estimated savings. You can use the recommended configuration to run a function on LMI without sizing it yourself and realize cost savings sooner.&lt;/p&gt; 
&lt;p&gt;These recommendations are available in the following AWS Regions: US East (N. Virginia), US West (Oregon), Europe (Ireland), and Europe (Milan). Customers with eligible AWS Support plans&amp;nbsp;can access them in the Trusted Advisor console alongside other cost optimization checks. To learn more, visit the &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/lambda-managed-instances.html"&gt;AWS Lambda Developer Guide,&lt;/a&gt;&amp;nbsp;the AWS Trusted Advisor &lt;a href="https://docs.aws.amazon.com/awssupport/latest/user/trusted-advisor.html"&gt;User Guide,&lt;/a&gt; and the &lt;a href="https://aws.amazon.com/lambda/pricing/"&gt;AWS Lambda pricing.&lt;/a&gt;&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/aws-lambda-cost-optimization-recommendations/</ore:originalUrl>
      <ore:upstreamId>68db578853b3f91eb21ed3531f94095a5427a1df</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:7873877d48edf35c7889ceb972f83fdf</id>
    <title>AWS Pricing Calculator now estimates workload costs through a new API</title>
    <updated>2026-11-20T18:35:00Z</updated>
    <published>2026-11-20T18:35:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/aws-pricing-calculator-api/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;AWS Pricing Calculator now offers GetUsageLinesEstimatedCost, a new API that returns the estimated cost of a planned workload in a single API call. You send up to 500 usage lines in one request and get the cost back right away, without saving an estimate to your account. While workload estimates let you create and save an estimate in Pricing Calculator, GetUsageLinesEstimatedCost returns a cost on demand, directly in your own tools and workflows.&lt;/p&gt; 
&lt;p&gt;You can choose from three rate types: public On-Demand rates, your rates after discounts, or your rates after discounts plus Savings Plans and Reserved Instances. The API returns the cost of each line and the total. For example, you can check what a design will cost before you deploy it, or let an AI coding agent call the API to price a workload while it helps you design it.&lt;/p&gt; 
&lt;p&gt;GetUsageLinesEstimatedCost is generally available at no additional charge in all AWS Regions, except the AWS GovCloud (US) Regions and the China Regions.&lt;/p&gt; 
&lt;p&gt;To learn more, see&amp;nbsp;&lt;a href="https://docs.aws.amazon.com/cli/latest/reference/bcm-pricing-calculator/get-usage-lines-estimated-cost.html"&gt;GetUsageLinesEstimatedCost&lt;/a&gt; in the AWS Billing and Cost Management API Reference, or&amp;nbsp;visit the AWS Pricing Calculator &lt;a href="https://calculator.aws/#/"&gt;product page&lt;/a&gt;.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/aws-pricing-calculator-api/</ore:originalUrl>
      <ore:upstreamId>06ed2b32cda75ecb478eff821410ea508ff9c5e5</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hacker-news:a17eab08b602965f525778159e34c68b</id>
    <title>Hurried Announcement: Alessandro Masullo GRH</title>
    <updated>2026-11-20T18:33:14Z</updated>
    <published>2026-11-20T18:33:14Z</published>
    <link rel="alternate" href="https://math216.wordpress.com/2026/11/20/hurried-announcement-alessandro-masullo-grh/" />
    <link rel="via" href="https://news.ycombinator.com/rss" />
    <category scheme="urn:ore-news:sources" term="hacker-news" label="Hacker News" />
    <author>
      <name>Hacker News</name>
    </author>
    <source>
      <id>urn:ore-news:source:hacker-news</id>
      <title>Hacker News</title>
      <link rel="alternate" href="https://news.ycombinator.com/" />
      <link rel="via" href="https://news.ycombinator.com/rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hacker-news</ore:sourceId>
      <ore:sourceName>Hacker News</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://news.ycombinator.com/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://news.ycombinator.com/rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://math216.wordpress.com/2026/11/20/hurried-announcement-alessandro-masullo-grh/</ore:originalUrl>
      <ore:upstreamId>https://math216.wordpress.com/2026/11/20/hurried-announcement-alessandro-masullo-grh/</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:787efb8bf9cb8d1cfc5aea02a62410f5</id>
    <title>AWS Billing and Cost Management now offers APIs to track payment status</title>
    <updated>2026-11-20T18:30:00Z</updated>
    <published>2026-11-20T18:30:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/aws-billing-cost-management-apis-payment-status/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;Today, AWS Billing and Cost Management announces new APIs that let you view your AWS payment information through the AWS SDKs and the AWS CLI. With these APIs, you can check your account balance, find invoices that are due or past due, see which payments and credit memos were applied to each invoice, and confirm that the payment methods on your account are active. You can call the APIs from your own tools or through an AI agent.&lt;/p&gt; 
&lt;p&gt;Previously, finance teams had to sign in to the console to find past-due invoices, match payments to invoices, or check whether a payment method was still active. Now you can automate these checks with APIs such as GetFinancialRecord,&amp;nbsp;BatchGetFinancialRecord,&amp;nbsp;ListFinancialRecords,&amp;nbsp;GetAccountBalance,&amp;nbsp;GetPaymentInstrument and ListPaymentInstruments. You can integrate the APIs with your accounts payable systems to monitor past-due balances and reconcile AWS invoices on your own schedule.&lt;/p&gt; 
&lt;p&gt;The APIs are available in the US East (N. Virginia) Region, and available to customers in all commercial AWS Regions.&lt;/p&gt; 
&lt;p&gt;To learn more, visit the &lt;a href="https://docs.aws.amazon.com/aws-cost-management/latest/APIReference/API_Operations_AWS_Payments.html"&gt;AWS Payments API Reference&lt;/a&gt;.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/aws-billing-cost-management-apis-payment-status/</ore:originalUrl>
      <ore:upstreamId>b6e31d09e73b9bbd6214600cea0453a3686347b0</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hacker-news:2cfbb3754bbd924ab5d0ab38f6f9f489</id>
    <title>We promoted developers into architects without informing them</title>
    <updated>2026-11-20T18:17:51Z</updated>
    <published>2026-11-20T18:17:51Z</published>
    <link rel="alternate" href="https://manidoraisamy.com/developer-to-architect.html" />
    <link rel="via" href="https://news.ycombinator.com/rss" />
    <category scheme="urn:ore-news:sources" term="hacker-news" label="Hacker News" />
    <author>
      <name>Hacker News</name>
    </author>
    <source>
      <id>urn:ore-news:source:hacker-news</id>
      <title>Hacker News</title>
      <link rel="alternate" href="https://news.ycombinator.com/" />
      <link rel="via" href="https://news.ycombinator.com/rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hacker-news</ore:sourceId>
      <ore:sourceName>Hacker News</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://news.ycombinator.com/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://news.ycombinator.com/rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://manidoraisamy.com/developer-to-architect.html</ore:originalUrl>
      <ore:upstreamId>https://manidoraisamy.com/developer-to-architect.html</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hacker-news:df74b3a4e7d2d1718036ffd121a4b7e8</id>
    <title>Vibecoding an inference chip</title>
    <updated>2026-11-20T18:15:16Z</updated>
    <published>2026-11-20T18:15:16Z</published>
    <link rel="alternate" href="https://ankitg.me/blog/vibecoding-inference-chip/" />
    <link rel="via" href="https://news.ycombinator.com/rss" />
    <category scheme="urn:ore-news:sources" term="hacker-news" label="Hacker News" />
    <author>
      <name>Hacker News</name>
    </author>
    <source>
      <id>urn:ore-news:source:hacker-news</id>
      <title>Hacker News</title>
      <link rel="alternate" href="https://news.ycombinator.com/" />
      <link rel="via" href="https://news.ycombinator.com/rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hacker-news</ore:sourceId>
      <ore:sourceName>Hacker News</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://news.ycombinator.com/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://news.ycombinator.com/rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://ankitg.me/blog/vibecoding-inference-chip/</ore:originalUrl>
      <ore:upstreamId>https://ankitg.me/blog/vibecoding-inference-chip/</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:63bc641be0230741aaeb755e0ebc7ba0</id>
    <title>Amazon EventBridge Scheduler adds 589 new API actions and event bus targets</title>
    <updated>2026-11-20T18:00:00Z</updated>
    <published>2026-11-20T18:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/eventbridge-scheduler-new-api-actions/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;Amazon EventBridge Scheduler expands its AWS SDK integrations with 589 new API actions across 81 AWS services, and adds templated targets for the enhanced EventBridge Custom event bus. You can now schedule direct invocations of a broader set of AWS services without writing custom integration code.&lt;/p&gt; 
&lt;p&gt;EventBridge Scheduler is a serverless scheduler that allows you to create, run, and manage billions of scheduled events and tasks across more than 270 AWS services, without provisioning or managing the underlying infrastructure. With a new templated target, you can schedule event delivery directly to the Custom event bus using its PutEvents or PutRawEvents API. The templated target also makes it easier to add metadata fields to each event. For example, you can send an event to your bus every night at midnight to start a reconciliation workflow, with no function in between to call the API.&lt;/p&gt; 
&lt;p&gt;The new API actions are available in all commercial AWS Regions where Amazon EventBridge Scheduler is available, subject to the availability of each target service in the Region. The templated targets for the Custom event bus are available in all AWS Regions where the enhanced Custom event bus is available. To learn more, see &lt;a href="https://docs.aws.amazon.com/scheduler/latest/UserGuide/managing-targets-templated.html"&gt;Using templated targets in EventBridge Scheduler&lt;/a&gt; and &lt;a href="https://docs.aws.amazon.com/scheduler/latest/UserGuide/managing-targets-universal.html"&gt;Using universal targets in EventBridge Scheduler&lt;/a&gt; in the Amazon EventBridge Scheduler User Guide. Install the &lt;a href="https://github.com/aws/agent-toolkit-for-aws"&gt;Agent Toolkit for AWS&lt;/a&gt; to start building with your AI coding agent.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/eventbridge-scheduler-new-api-actions/</ore:originalUrl>
      <ore:upstreamId>75045e061356e99011e8afd0ccf81b32474ed4c3</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:4525829087f90925abc5e97af6ff34ba</id>
    <title>AWS CloudFormation Service-Managed StackSets adds custom execution roles with nested stacks support</title>
    <updated>2026-11-20T17:45:00Z</updated>
    <published>2026-11-20T17:45:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/stacksets-custom-execution-roles/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;&lt;a href="https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-concepts.html" target="_blank" rel="noopener noreferrer"&gt;AWS CloudFormation StackSets&lt;/a&gt; now supports custom execution roles for service-managed stack sets, which enables you to scope the permissions StackSets uses in each target AWS account. StackSets deploys the same infrastructure, such as networking and security settings, across thousands of accounts and Regions in one operation. With a custom execution role, you can also use nested stacks, macros, and transforms in service-managed stack sets, which allows you to deploy the reusable templates you use for individual stacks across your organization.&lt;/p&gt; 
&lt;p&gt;With a custom execution role, you define what StackSets can do in each account. By default, service-managed stack sets use a role in each account that can provision any resource in a template without additional setup, and that default remains available. Now, you can provide a template that defines an IAM role, called the execution role, and StackSets creates it in each account before deploying. For example, a stack set that creates Amazon S3 buckets can use an execution role limited to CloudFormation and Amazon S3 permissions. When you update the execution role template, StackSets updates the role in every account it deployed to.&lt;/p&gt; 
&lt;p&gt;To get started, choose Set execution role when you create a stack set in the CloudFormation console, or use the AWS CLI or AWS SDKs. To learn more, visit the &lt;a href="https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-custom-execution-role.html" target="_blank" rel="noopener noreferrer"&gt;documentation&lt;/a&gt; and the &lt;a href="https://aws.amazon.com/blogs/devops/announcing-custom-execution-roles-for-aws-cloudformation-stacksets/" target="_blank" rel="noopener noreferrer"&gt;AWS DevOps Blog&lt;/a&gt;. This feature is available at no additional charge in all commercial AWS Regions, the AWS GovCloud (US) Regions, and the China Regions. Refer to the &lt;a href="https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/"&gt;AWS Region table&lt;/a&gt; for details.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/stacksets-custom-execution-roles/</ore:originalUrl>
      <ore:upstreamId>344b860c79e8a39f46097c85c6a5967bc51e583e</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hatena-bookmark-technology:b733f511a8c7bddb734b874015e04360</id>
    <title>New Relicのアラート対応をClaude Codeで自動修正するワークフローを作った話</title>
    <updated>2026-11-20T17:42:07Z</updated>
    <published>2026-11-20T17:42:07Z</published>
    <link rel="alternate" href="https://speakerdeck.com/manabuseki/new-relic-no-taiou-o-claude-code-de-jidou-shuusei-suru-waku-furo-o-tsukuta-hanashi" />
    <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    <category scheme="urn:ore-news:sources" term="hatena-bookmark-technology" label="Hatena Bookmark Technology" />
    <author>
      <name>Hatena Bookmark Technology</name>
    </author>
    <source>
      <id>urn:ore-news:source:hatena-bookmark-technology</id>
      <title>Hatena Bookmark Technology</title>
      <link rel="alternate" href="https://b.hatena.ne.jp/hotentry/it" />
      <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hatena-bookmark-technology</ore:sourceId>
      <ore:sourceName>Hatena Bookmark Technology</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://b.hatena.ne.jp/hotentry/it</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://b.hatena.ne.jp/hotentry/it.rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://speakerdeck.com/manabuseki/new-relic-no-taiou-o-claude-code-de-jidou-shuusei-suru-waku-furo-o-tsukuta-hanashi</ore:originalUrl>
      <ore:upstreamId>https://speakerdeck.com/manabuseki/new-relic-no-taiou-o-claude-code-de-jidou-shuusei-suru-waku-furo-o-tsukuta-hanashi</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:c3a9b3b5c6e25028d8dbd2671bce3988</id>
    <title>Amazon EventBridge Custom event bus now supports Webhook Events</title>
    <updated>2026-11-20T17:30:00Z</updated>
    <published>2026-11-20T17:30:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/amazon-eventbridge-webhook-events" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;Amazon EventBridge now supports Webhook Events for the enhanced Custom event bus, so SaaS applications, AI agents, and custom integrations can send events to a bus over HTTPS. You no longer need to deploy and operate your own API endpoint and compute to receive webhooks and publish them to your bus.&lt;/p&gt; 
&lt;p&gt;The EventBridge Custom event bus is a serverless event broker that enables you to create scalable event-driven applications by routing events between your applications, SaaS integrations, and AWS services. When you create a webhook event source on your bus, EventBridge provides a managed HTTPS URL and verifies each request using an HMAC signature, a static token, or basic authentication. EventBridge then publishes accepted events to the bus, where Subscribers filter and deliver them like any other event. For example, shipment status updates from a logistics partner can reach your order tracking and customer notification Subscribers as soon as the partner sends them.&lt;/p&gt; 
&lt;p&gt;Webhook Events are available in all AWS Regions where the enhanced Custom event bus is available. Events received through a webhook are billed as standard Custom event bus ingress, with no additional charge for the webhook.&lt;/p&gt; 
&lt;p&gt;To learn more, see &lt;a href="https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-custom-bus-webhook-sources.html"&gt;Webhook Events&lt;/a&gt; in the Amazon EventBridge User Guide and the &lt;a href="https://aws.amazon.com/eventbridge/"&gt;Amazon EventBridge product page&lt;/a&gt;. Install the &lt;a href="https://github.com/aws/agent-toolkit-for-aws"&gt;Agent Toolkit for AWS&lt;/a&gt; to start building with your AI coding agent.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/amazon-eventbridge-webhook-events</ore:originalUrl>
      <ore:upstreamId>4e474f508c81639f25d5c98ad9d64086a61b2aa3</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:a56e6f5cc43144cc7e6947d7a85714bc</id>
    <title>Amazon EventBridge Custom event bus now supports Amazon MSK as a target</title>
    <updated>2026-11-20T17:30:00Z</updated>
    <published>2026-11-20T17:30:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/amazon-eventbridge-msk-target/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;Amazon EventBridge now supports Amazon Managed Streaming for Apache Kafka (Amazon MSK) as a target for the enhanced Custom event bus, so you can deliver events to Kafka topics without running your own producer.&lt;/p&gt; 
&lt;p&gt;The EventBridge Custom event bus is a serverless event broker that enables you to create scalable event-driven applications by routing events between your applications, SaaS integrations, and AWS services. To deliver events to MSK, you create a Subscriber that specifies the cluster ARN and topic. You can also configure Kafka producer settings such as partition key, acknowledgment level, and record headers. EventBridge supports both public and private, serverless and provisioned clusters. When you create a Subscriber for a private cluster, EventBridge automatically sets up a private connection to the cluster. For example, teams that publish to a shared Custom event bus can now deliver purchase-order events to the MSK topics their payments team already consumes from.&lt;/p&gt; 
&lt;p&gt;Amazon MSK targets are available in all AWS Regions where the enhanced Custom event bus is available. Delivery to MSK is billed as standard Custom event bus egress. EventBridge also supports compression before delivery, which is billed as an Event Evaluation.&lt;/p&gt; 
&lt;p&gt;To learn more, see &lt;a href="https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-custom-bus-target-msk.html"&gt;Amazon MSK cluster target&lt;/a&gt; in the Amazon EventBridge User Guide and the &lt;a href="https://aws.amazon.com/eventbridge/"&gt;Amazon EventBridge product page&lt;/a&gt;. Install the &lt;a href="https://github.com/aws/agent-toolkit-for-aws"&gt;Agent Toolkit for AWS&lt;/a&gt; to start building with your AI coding agent.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/amazon-eventbridge-msk-target/</ore:originalUrl>
      <ore:upstreamId>a8cb47452baf351f32e36fa5079b71d8d2eccd4f</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hacker-news:58bcaa17fbdfd5b473dcf09a0bfc0ad3</id>
    <title>Unforced Navier-Stokes Singularity and the Generalized Riemann Hypothesis</title>
    <updated>2026-11-20T17:21:36Z</updated>
    <published>2026-11-20T17:21:36Z</published>
    <link rel="alternate" href="https://terrytao.wordpress.com/2026/11/20/unforced-euler-singularity-unforced-navier-stokes-singularity-and-the-generalized-riemann-hypothesis/" />
    <link rel="via" href="https://news.ycombinator.com/rss" />
    <category scheme="urn:ore-news:sources" term="hacker-news" label="Hacker News" />
    <author>
      <name>Hacker News</name>
    </author>
    <source>
      <id>urn:ore-news:source:hacker-news</id>
      <title>Hacker News</title>
      <link rel="alternate" href="https://news.ycombinator.com/" />
      <link rel="via" href="https://news.ycombinator.com/rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hacker-news</ore:sourceId>
      <ore:sourceName>Hacker News</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://news.ycombinator.com/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://news.ycombinator.com/rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://terrytao.wordpress.com/2026/11/20/unforced-euler-singularity-unforced-navier-stokes-singularity-and-the-generalized-riemann-hypothesis/</ore:originalUrl>
      <ore:upstreamId>https://terrytao.wordpress.com/2026/11/20/unforced-euler-singularity-unforced-navier-stokes-singularity-and-the-generalized-riemann-hypothesis/</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:9c34052218702c7814cdd7bc31b64af7</id>
    <title>Amazon Aurora MySQL 8.4.12 is now generally available</title>
    <updated>2026-11-20T17:00:00Z</updated>
    <published>2026-11-20T17:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/amazon-aurora-mysql-8412-available/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;Starting today, &lt;a href="https://aws.amazon.com/rds/aurora/" target="_blank"&gt;Amazon Aurora MySQL-Compatible Edition&lt;/a&gt; 8.4 supports MySQL 8.4.12. This release includes several security enhancements and bug fixes. We recommend upgrading to the newer minor versions to accept fixes for Common Vulnerabilities and Exposures (CVEs) in prior versions of MySQL and to benefit from bug fixes, performance improvements, and new functionality added by community MySQL. For more details, refer to the &lt;a href="https://docs.aws.amazon.com/AmazonRDS/latest/AuroraMySQLReleaseNotes/AuroraMySQL.Updates.84Updates.html" target="_blank"&gt;Aurora MySQL 8.4&lt;/a&gt; and &lt;a href="https://dev.mysql.com/doc/relnotes/mysql/8.4/en/news-8-4-12.html" target="_blank"&gt;MySQL 8.4.12&lt;/a&gt; release notes.&lt;/p&gt; 
&lt;p&gt;You can upgrade your databases during scheduled maintenance windows using automatic minor version upgrades. To simplify operations at scale, enable &lt;a href="https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.AMVU.html" target="_blank"&gt;automatic minor version upgrades&lt;/a&gt; and use the AWS Organizations &lt;a href="https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.Maintenance.AMVU.UpgradeRollout.html" target="_blank"&gt;Upgrade Rollout Policy&lt;/a&gt; to orchestrate upgrades across your clusters in phases, validating on lower-priority environments before upgrading your most critical ones. You can perform minor version upgrades in-place or via snapshot restore. Learn more about performing version upgrades in the &lt;a href="https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Upgrading.html" target="_blank"&gt;Amazon Aurora User Guide&lt;/a&gt;. This release is supported in all &lt;a href="https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Concepts.RegionsAndAvailabilityZones.html#Aurora.Overview.Availability.MySQL" target="_blank"&gt;AWS Regions&lt;/a&gt; where Aurora MySQL is available.&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://aws.amazon.com/rds/aurora/" target="_blank"&gt;Amazon Aurora&lt;/a&gt; is designed for high performance and availability at global scale with full MySQL compatibility. It provides scale-to-zero serverless compute, Aurora Global Database for multi-Region resilience, Aurora I/O-Optimized for improved price performance on I/O-intensive workloads, and built-in security and continuous backups. To get started, take a look at Aurora's &lt;a href="https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/CHAP_AuroraOverview.html" target="_blank"&gt;getting started page&lt;/a&gt;.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/amazon-aurora-mysql-8412-available/</ore:originalUrl>
      <ore:upstreamId>2ce88365065aaaf445be25c90cc4bb1d623a6f51</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:18c81e4ab23d9891fb29c1361bd36504</id>
    <title>Amazon MSK Standard Brokers adds support for Apache Kafka version 4.2</title>
    <updated>2026-11-20T17:00:00Z</updated>
    <published>2026-11-20T17:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/aws-msk-standard-version-42/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;Amazon Managed Streaming for Apache Kafka (Amazon MSK) now supports Apache Kafka version 4.2 on Standard brokers. A key highlight of this release is Queues for Kafka, which is now production ready. With Queues, multiple consumers can process messages from the same topic partitions, which improves parallelism and throughput for workloads that need point-to-point message delivery. This release also includes Eligible Leader Replicas (ELR) enhancements that improve leader election correctness and strengthen availability. The new consumer rebalance protocol makes consumer group rebalances smoother and faster. The new Streams Rebalance Protocol extends broker-side coordination to Kafka Streams applications so tasks get assigned more efficiently. For the full list of improvements and bug fixes, see the &lt;a href="https://archive.apache.org/dist/kafka/4.2.0/RELEASE_NOTES.html" target="_blank"&gt;Apache Kafka 4.2 release notes&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;To start using Apache Kafka 4.2 on Amazon MSK, select version 4.2.x when creating a new cluster with the AWS Management Console, AWS CLI, or AWS SDKs. You can also upgrade existing MSK provisioned clusters with an in-place rolling update. Amazon MSK orchestrates broker restarts to maintain availability and protect your data during the upgrade. Kafka version 4.2 support is available today in all &lt;a href="https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/" target="_blank"&gt;&lt;u&gt;AWS regions&lt;/u&gt;&lt;/a&gt; where Amazon MSK Standard brokers is offered. To learn how to get started, see the &lt;a href="https://docs.aws.amazon.com/msk/latest/developerguide/getting-started.html" target="_blank"&gt;&lt;u&gt;Amazon MSK Developer Guide&lt;/u&gt;&lt;/a&gt;.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/aws-msk-standard-version-42/</ore:originalUrl>
      <ore:upstreamId>b9393d1fa084429da1cef133ad7efac98087be12</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:13839df62eddc270c01fcd7176a2c977</id>
    <title>Amazon Connect Customer expands how teams track and act on service level agreements for cases</title>
    <updated>2026-11-20T17:00:00Z</updated>
    <published>2026-11-20T17:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/amazon-connect-cases-sla-enhancements/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;Amazon Connect Customer enhances service level agreements (SLAs) for cases, so teams can set service goals for more of their work and respond faster when a case falls behind. Admins can set SLAs on case fields beyond status, such as requiring a case’s severity to drop from high to medium within 24 hours. Admins can add an email action to SLA breach rules, so the assigned agent learns right away when a case misses its SLA. Developers can use APIs to adjust a case’s SLA deadline when the team is waiting on information from an outside party, such as a partner.&lt;/p&gt; 
&lt;p&gt;Cases is available in the following AWS Regions: US East (N. Virginia), US West (Oregon), Canada (Central), Europe (Frankfurt), Europe (London), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), and Africa (Cape Town). To learn more and get started, visit the Cases &lt;a href="https://aws.amazon.com/products/connect/customer/cases/" target="_blank"&gt;webpage&lt;/a&gt; and &lt;a href="https://docs.aws.amazon.com/connect/latest/adminguide/cases-sla.html" target="_blank"&gt;documentation&lt;/a&gt;.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/amazon-connect-cases-sla-enhancements/</ore:originalUrl>
      <ore:upstreamId>e36431c1eb2c41d0e27d67f47dfe60126538a8c1</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:168d689ff2e4860abb0e1f9bbf400793</id>
    <title>Amazon ECS Action Logs now cover tasks, container instances, and capacity providers</title>
    <updated>2026-11-20T16:50:00Z</updated>
    <published>2026-11-20T16:50:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/amazon-ecs-action-logs-expanded-troubleshooting" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;&lt;a href="https://aws.amazon.com/ecs/"&gt;Amazon Elastic Container Service&lt;/a&gt; (Amazon ECS) now extends Action Logs to include tasks, container instances, clusters, and capacity providers, so you can see why your tasks failed or why your clusters didn't scale as desired. Action Logs provide detailed, timestamped records of the actions Amazon ECS performs on your behalf, and until now covered service deployments and managed daemon updates. With the expanded coverage, you can diagnose task failures and scaling issues yourself, and resolve them faster than before, without contacting AWS support. If you use Action Logs already, you receive the new events automatically with no configuration changes.&lt;/p&gt; 
&lt;p&gt;When a task fails to start, Action Logs show the reason. Examples include image pull failures, missing permissions for Amazon EBS volumes, or lack of available IP addresses in the subnet. When a running task stops, you can see the container exit code and the health check that triggered the stop. For cluster infrastructure, Action Logs record container instance registration and draining, Amazon EC2 instances that fail to register with a cluster, capacity provider changes, and managed scaling actions, including when an Amazon EC2 Auto Scaling group reaches its maximum size. Each log entry includes the event name, log level (INFO, WARN, or ERROR), relevant resource ARNs, and a status reason.&lt;/p&gt; 
&lt;p&gt;Action Logs is available in AWS Regions, including the AWS GovCloud (US) &lt;a href="https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/"&gt;Regions&lt;/a&gt;.&amp;nbsp;You can opt in at the cluster level through the Amazon ECS console or the Amazon CloudWatch vended logs APIs, and deliver logs to Amazon CloudWatch Logs, Amazon S3, or Amazon Data Firehose. Standard pricing for each destination applies. To learn more, see &lt;a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/action-logs.html"&gt;Monitor Amazon ECS operations with Action Logs&lt;/a&gt; in the Amazon ECS Developer Guide.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/amazon-ecs-action-logs-expanded-troubleshooting</ore:originalUrl>
      <ore:upstreamId>2e17a38f6c4f750a99d3577faf4859c71c590ca8</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:2be05b9214827589f9abea0c4350f0e0</id>
    <title>AWS Transform announces UI component modernization for Windows web applications</title>
    <updated>2026-11-20T16:30:00Z</updated>
    <published>2026-11-20T16:30:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/aws-transform-ui-windows/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;Today, AWS announced the general availability of third-party UI component porting for ASP.NET web site modernization in AWS Transform. When AWS Transform modernizes a legacy ASP.NET web site, it now detects dependencies on popular third-party UI component libraries. You can replace them with license-free Microsoft-native and open-source components, or you can keep using vendor UI libraries.&lt;/p&gt; 
&lt;p&gt;AWS Transform rewrites legacy ASP.NET web sites for ASP.NET Core UI frameworks. When the AWS Transform for .NET modernization agent finds a dependency on a popular third-party UI library, it offers two options. The first option is for customers who require open-source software only. The agent replaces each proprietary control with a Microsoft-native or open-source control on the target UI framework and removes the original dependency. The second option is for customers who want to keep using vendor libraries. The agent adds code comments and next-step instructions for moving to an equivalent vendor library on the target UI framework. You then arrange licensing with the vendor and finish the port using an AI coding companion.&lt;/p&gt; 
&lt;p&gt;This capability is available at no additional cost in all eight AWS Regions where AWS Transform is offered: US East (N. Virginia), Canada (Central), Asia Pacific (Mumbai), Asia Pacific (Seoul), Asia Pacific (Sydney), Asia Pacific (Tokyo), Europe (Frankfurt), and Europe (London).&lt;/p&gt; 
&lt;p&gt;To learn more, see &lt;a href="https://docs.aws.amazon.com/transform/latest/userguide/dotnet-porting-ui.html"&gt;Porting UI layer code&lt;/a&gt; in the AWS Transform User Guide.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/aws-transform-ui-windows/</ore:originalUrl>
      <ore:upstreamId>59cf4a0ed2c5345ce798832bd2b218b890b10e8c</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hacker-news:7236047bfd3b338b8fe182177502a950</id>
    <title>Language Models Can Rewrite Their Own Weights</title>
    <updated>2026-11-20T16:29:06Z</updated>
    <published>2026-11-20T16:29:06Z</published>
    <link rel="alternate" href="https://arxiv.org/abs/2611.21885" />
    <link rel="via" href="https://news.ycombinator.com/rss" />
    <category scheme="urn:ore-news:sources" term="hacker-news" label="Hacker News" />
    <author>
      <name>Hacker News</name>
    </author>
    <source>
      <id>urn:ore-news:source:hacker-news</id>
      <title>Hacker News</title>
      <link rel="alternate" href="https://news.ycombinator.com/" />
      <link rel="via" href="https://news.ycombinator.com/rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hacker-news</ore:sourceId>
      <ore:sourceName>Hacker News</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://news.ycombinator.com/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://news.ycombinator.com/rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://arxiv.org/abs/2611.21885</ore:originalUrl>
      <ore:upstreamId>https://arxiv.org/abs/2611.21885</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:ba0572b2b1c39f73509b0485ae714b9f</id>
    <title>AWS Transform announces support for .NET 11 and expanded project types</title>
    <updated>2026-11-20T16:00:00Z</updated>
    <published>2026-11-20T16:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/aws-transform-windows-dotnet-11/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;Today, AWS announced the general availability of .NET 11 support in AWS Transform for .NET. Support for VB.NET, desktop projects, and mobile projects, previously in preview, is also now generally available. You can modernize a broad range of Windows .NET workloads to the latest version of .NET and lower costs by running them on Linux. Modernized workloads gain the performance improvements, new C# language features, and improved diagnostics in .NET 11.&lt;/p&gt; 
&lt;p&gt;AWS Transform modernizes both legacy .NET Framework applications (version 3.5 and later) and modern .NET applications (versions 5 through 10) to .NET 11. It transforms code written in C# and VB.NET. Supported project types include class libraries, console applications, ASP.NET web projects (MVC, Web API, and Web Forms), web services (ASMX and WCF), desktop applications (WinForms and WPF), mobile applications (Xamarin), unit test projects (MSTest, NUnit, and xUnit), and Windows services. You can run all transformed applications except desktop and mobile projects on Linux, which can reduce operating costs by up to 40%.&lt;/p&gt; 
&lt;p&gt;This capability is available at no additional cost in all eight AWS Regions where AWS Transform is offered: US East (N. Virginia), Canada (Central), Asia Pacific (Mumbai), Asia Pacific (Seoul), Asia Pacific (Sydney), Asia Pacific (Tokyo), Europe (Frankfurt), and Europe (London).&lt;/p&gt; 
&lt;p&gt;To learn more, see &lt;a href="https://docs.aws.amazon.com/transform/latest/userguide/dotnet.html"&gt;Modernizing .NET with AWS Transform &lt;/a&gt;in the AWS Transform User Guide.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/aws-transform-windows-dotnet-11/</ore:originalUrl>
      <ore:upstreamId>0c0d23bfb753d7cdfc4120dd32a078b0c4945cc3</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:920162edf755d5d0902b8a035f377265</id>
    <title>Amazon Managed Service for Prometheus supports 2B active metrics and 300K rules per workspace</title>
    <updated>2026-11-20T16:00:00Z</updated>
    <published>2026-11-20T16:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/amp-supports-2b-metrics-300k-rules/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;Amazon Managed Service for Prometheus now supports up to 2 billion active metric time series and up to 300,000 total recording and alerting rules per workspace. Customers can also create multiple workspaces per account. This lets them store and analyze billions of Prometheus metrics across their organization.&lt;/p&gt; 
&lt;p&gt;Amazon Managed Service for Prometheus is a fully managed, Prometheus-compatible monitoring service. It helps you monitor and alert on operational metrics at scale. It scales ingestion and storage automatically for high-cardinality workloads across containerized, serverless and hybrid environments. &lt;/p&gt; 
&lt;p&gt;To get started, create an Amazon Managed Service for Prometheus workspace. To raise your active series or rules limits, file a service limit increase request in AWS Support Center or AWS Service Quotas. To learn more, see the &lt;a href="https://docs.aws.amazon.com/prometheus/latest/userguide/AMP_quotas.html"&gt;Amazon Managed Service for Prometheus user guide&lt;/a&gt; and the &lt;a href="https://aws.amazon.com/prometheus/"&gt;product page.&lt;/a&gt;&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/amp-supports-2b-metrics-300k-rules/</ore:originalUrl>
      <ore:upstreamId>70799b8c9c3a5498dca09a0ed78053d146e7b894</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:6ad7f786911dbceda79b6a3fce23d4ba</id>
    <title>Introducing Amazon EC2 T9g instances based on Graviton5</title>
    <updated>2026-11-20T16:00:00Z</updated>
    <published>2026-11-20T16:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/ec2-t9g-instances-ga/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;AWS is announcing the general availability of new low-cost burstable Amazon EC2 T9g instances, which offer the best price performance among general-purpose&amp;nbsp;EC2 instances. These instances are powered by AWS Graviton5 processors and built on the latest sixth generation AWS Nitro cards. T9g instances deliver up to 45% better price performance compared to previous generation T4g instances, and offer four sizes: nano, micro, small, and medium. These instances are designed for workloads requiring low to moderate CPU utilization, including data processing, login gateways, small databases, microservices, low-traffic websites, freemium services, staging and development, and short-duration compute tasks such as batch processing, event-driven functions, and CI/CD pipelines.&lt;/p&gt; 
&lt;p&gt;T9g instances deliver up to 2.3x the compute performance, 1.5x higher network bandwidth, and 2.8x higher EBS bandwidth compared to T4g instances. They are built on the sixth-generation &lt;a href="https://aws.amazon.com/ec2/nitro/" target="_blank" rel="noopener noreferrer"&gt;AWS Nitro System&lt;/a&gt; and feature the Nitro Isolation Engine, harnessing formal verification to provide mathematical assurance that customer workloads are isolated from each other and AWS operators, pioneering a new standard for mathematically proven cloud security.&amp;nbsp;&lt;/p&gt; 
&lt;p&gt;T9g instances use the same CPU credit system as T4g with Standard and Unlimited modes, so existing T customers can upgrade to T9g and immediately benefit from better price performance, enabling them to lower their TCO. For customers new to AWS or migrating from on-premises, T9g instances provide one of the most cost-effective entry points to run a variety of lightweight workloads.&lt;/p&gt; 
&lt;p&gt;T9g.micro and T9g.small are available under the &lt;a href="https://aws.amazon.com/free/" target="_blank" rel="noopener noreferrer"&gt;AWS Free Tier&lt;/a&gt;.&amp;nbsp;T9g instances are available in US East (N. Virginia, Ohio), US West (N. California, Oregon), Canada (Central), South America (São Paulo), Europe (Frankfurt, Spain), and Asia Pacific (Malaysia, Singapore, Sydney, Tokyo) regions. T9g instances are available to purchase via Savings Plans, On-Demand instances, and Spot instances. To learn more, visit the &lt;a href="https://aws.amazon.com/ec2/instance-types/t9g/" target="_blank" rel="noopener noreferrer"&gt;Amazon EC2 T9g instances page&lt;/a&gt;.&amp;nbsp;&amp;nbsp;&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/ec2-t9g-instances-ga/</ore:originalUrl>
      <ore:upstreamId>b879d6e5bde55774fc455d4fa328fff88b2c9300</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:698415822851754c2dfdcd272d1babd3</id>
    <title>Amazon MSK now supports in-place upgrade from Standard brokers to Express brokers</title>
    <updated>2026-11-20T16:00:00Z</updated>
    <published>2026-11-20T16:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/amazon-msk-standard-brokers-to-express-brokers-in-place-upgrade" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;You can now upgrade existing &lt;a href="https://aws.amazon.com/msk/"&gt;Amazon MSK&lt;/a&gt; Provisioned clusters from Standard brokers to Express brokers in place, with fully managed data migration and no application changes. Express brokers are designed to deliver up to 3x more throughput per broker, scale up to 20x faster, and recover up to 90% faster compared to Standard brokers. With in-place upgrade, you can get the performance and operational benefits of Express brokers in hours, without needing to create a new cluster or having to migrate your data and applications to it. The upgrade keeps cluster endpoints unchanged, eliminating application cutovers, and preserves consumer offsets, so stateful applications such as Apache Flink and Kafka Streams continue without reprocessing or duplicates.&lt;/p&gt; 
&lt;p&gt;Express brokers make Apache Kafka simpler to manage and more cost-effective to run at scale, with pay-as-you-go storage that scales automatically and built-in best practice defaults for higher resilience. Previously, upgrading to Express brokers meant creating a new cluster and migrating workloads to it, which required careful planning and cross-team coordination. With this launch, you can upgrade your existing Standard brokers to Express brokers in-place, without interrupting your applications, while maintaining complete control over the upgrade process. The upgrade adds Express brokers to your cluster and moves your topics to them, either automatically or in batches you control. Your Standard brokers stay in the cluster until you choose to decommission them to complete the upgrade, so you can validate your applications and roll back if needed.&lt;/p&gt; 
&lt;p&gt;In-place upgrade is available for MSK Provisioned clusters running Standard brokers on Apache Kafka version 3.9 with KRaft, in all AWS Regions where Express brokers are available. You can upgrade to Express brokers on M7g or M8g instances. Express brokers on M8g deliver up to 30% cost savings compared to Express brokers on M7g. There's no additional charge for the upgrade itself. You pay for both Standard and Express brokers while the upgrade is in progress. To get started, visit the &lt;a href="https://docs.aws.amazon.com/msk/latest/developerguide/what-is-msk.html"&gt;Amazon MSK Developer Guide&lt;/a&gt; and the &lt;a href="https://aws.amazon.com/msk/features/express-brokers-for-amazon-msk/"&gt;Migration to Express brokers&lt;/a&gt; product page.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/amazon-msk-standard-brokers-to-express-brokers-in-place-upgrade</ore:originalUrl>
      <ore:upstreamId>8af7ea171a4eb38b77843d75b5c9241c69b6e9e2</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:676cf10b77a8e67d711b90fd3d3a86f6</id>
    <title>AWS Lambda MicroVMs is now available in 7 additional AWS regions</title>
    <updated>2026-11-20T16:00:00Z</updated>
    <published>2026-11-20T16:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/aws-lambda-microvms-7-regions" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;AWS Lambda MicroVMs is now available in 7 additional AWS Regions: Asia Pacific (Osaka), Asia Pacific (Seoul), Canada (Central), Europe (London), Europe (Paris), South America (São Paulo), and US West (N. California). With this launch, you can use Lambda MicroVMs in a total of 21 AWS Regions.&lt;/p&gt; 
&lt;p&gt;Lambda MicroVMs is a serverless compute primitive that provides VM-level isolation, near-instant launch and resume speeds, and state preservation for executing user or AI generated code.&amp;nbsp; The service enables secure, stateful, and responsive code execution for applications including AI coding assistants, interactive development environments, and vulnerability scanners.&lt;/p&gt; 
&lt;p&gt;With today's launch, developers can run Lambda MicroVMs closer to their end-users in 7 additional Regions, helping meet latency and data residency requirements. To get started, create a MicroVM image from your Dockerfile, then launch MicroVMs from that image. Give each user or job their own MicroVM with a dedicated HTTPS URL that supports popular connectivity protocols such as HTTP/2, gRPC, and WebSockets. You can use MicroVMs through the AWS Lambda console, AWS CloudFormation, AWS Cloud Development Kit, or with your preferred Agentic development tools using the &lt;a href="https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/specialized-skills/serverless-skills/aws-lambda-microvms"&gt;Agent Toolkit for AWS&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;To learn more, visit the &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/lambda-microvms-guide.html"&gt;AWS Lambda MicroVMs developer guide&lt;/a&gt;. For information on pricing, see &lt;a href="https://aws.amazon.com/lambda/pricing/"&gt;Lambda MicroVMs pricing&lt;/a&gt;. Visit the &lt;a href="https://builder.aws.com/build/capabilities"&gt;AWS Capabilities by Region page&lt;/a&gt; for the latest region availability.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/aws-lambda-microvms-7-regions</ore:originalUrl>
      <ore:upstreamId>8cc964bd2d5ffb95c0a2e75463daf9009b5c3079</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:479c3a2841dcc4bdc9cc5aa32ec86b5e</id>
    <title>Amazon Managed Service for Prometheus now available in the AWS European Sovereign Cloud (Germany) region</title>
    <updated>2026-11-20T16:00:00Z</updated>
    <published>2026-11-20T16:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/amp-aws-european-sovereign-cloud/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;Amazon Managed Service for Prometheus is now available in the AWS European Sovereign Cloud (Germany) region, along with Amazon Managed Service for Prometheus collector.&amp;nbsp;Amazon Managed Service for Prometheus is a fully managed, Prometheus-compatible monitoring service, that&amp;nbsp;helps you monitor and alert on operational metrics at scale. Customers in the AWS European Sovereign Cloud can now run Prometheus-compatible monitoring workloads in-region, which lowers latency for local workloads and keeps metric data within the region.&lt;/p&gt; 
&lt;p&gt;Amazon Managed Service for Prometheus collector is a fully managed, agentless collector. It discovers and collects Prometheus metrics from your container workloads, so you do not need to run collection agents yourself. The collector sends metrics to an Amazon Managed Service for Prometheus workspace, where you query and analyze them. A workspace is a logical space for storing and querying Prometheus metrics.&amp;nbsp;&lt;/p&gt; 
&lt;p&gt;For the full list of regions where Amazon Managed Service for Prometheus is available, see the &lt;a href="https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/"&gt;AWS Regional Services List&lt;/a&gt;. For pricing, see the &lt;a href="https://www.aws.eu/prometheus/pricing/"&gt;Amazon Managed Service for Prometheus pricing page&lt;/a&gt;. To learn more, see the &lt;a href="https://docs.aws.amazon.com/prometheus/latest/userguide/what-is-Amazon-Managed-Service-Prometheus.html"&gt;Amazon Managed Service for Prometheus user guide&lt;/a&gt; and the &lt;a href="https://aws.amazon.com/prometheus/"&gt;product page.&lt;/a&gt;&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/amp-aws-european-sovereign-cloud/</ore:originalUrl>
      <ore:upstreamId>ef96f608fd55ed5203c288210765e4467ce767d1</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hatena-bookmark-technology:d10783c21d7fc2edb6e1fad37a83e8fd</id>
    <title>ZOZOTOWNの退会者含む1,518万人分の情報が漏えい　WEAR by ZOZOでも1,393万人分に（ビジネス＋IT） - Yahoo!ニュース</title>
    <updated>2026-11-20T15:59:06Z</updated>
    <published>2026-11-20T15:59:06Z</published>
    <link rel="alternate" href="https://news.yahoo.co.jp/articles/1739163b2e1fd496107c05cb8b455d37d52be5d9" />
    <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    <category scheme="urn:ore-news:sources" term="hatena-bookmark-technology" label="Hatena Bookmark Technology" />
    <author>
      <name>Hatena Bookmark Technology</name>
    </author>
    <source>
      <id>urn:ore-news:source:hatena-bookmark-technology</id>
      <title>Hatena Bookmark Technology</title>
      <link rel="alternate" href="https://b.hatena.ne.jp/hotentry/it" />
      <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hatena-bookmark-technology</ore:sourceId>
      <ore:sourceName>Hatena Bookmark Technology</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://b.hatena.ne.jp/hotentry/it</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://b.hatena.ne.jp/hotentry/it.rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://news.yahoo.co.jp/articles/1739163b2e1fd496107c05cb8b455d37d52be5d9</ore:originalUrl>
      <ore:upstreamId>https://news.yahoo.co.jp/articles/1739163b2e1fd496107c05cb8b455d37d52be5d9</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hacker-news:18143b3c8739dc468656ca482146785b</id>
    <title>Finite-time blow-up for the Navier–Stokes equations</title>
    <updated>2026-11-20T15:34:31Z</updated>
    <published>2026-11-20T15:34:31Z</published>
    <link rel="alternate" href="https://github.com/tristanbuckmaster/navier-stokes/" />
    <link rel="via" href="https://news.ycombinator.com/rss" />
    <category scheme="urn:ore-news:sources" term="hacker-news" label="Hacker News" />
    <author>
      <name>Hacker News</name>
    </author>
    <source>
      <id>urn:ore-news:source:hacker-news</id>
      <title>Hacker News</title>
      <link rel="alternate" href="https://news.ycombinator.com/" />
      <link rel="via" href="https://news.ycombinator.com/rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hacker-news</ore:sourceId>
      <ore:sourceName>Hacker News</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://news.ycombinator.com/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://news.ycombinator.com/rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://github.com/tristanbuckmaster/navier-stokes/</ore:originalUrl>
      <ore:upstreamId>https://github.com/tristanbuckmaster/navier-stokes/</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hatena-bookmark-technology:1e59b067315da8e22153024e45c246c5</id>
    <title>モダンな情シスは、AIエージェントを育て、任せ、圧倒的な生産性を生む｜kajinari | モダンな情シス</title>
    <updated>2026-11-20T15:27:05Z</updated>
    <published>2026-11-20T15:27:05Z</published>
    <link rel="alternate" href="https://note.com/kajinari/n/n19c73d819b14" />
    <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    <category scheme="urn:ore-news:sources" term="hatena-bookmark-technology" label="Hatena Bookmark Technology" />
    <author>
      <name>Hatena Bookmark Technology</name>
    </author>
    <source>
      <id>urn:ore-news:source:hatena-bookmark-technology</id>
      <title>Hatena Bookmark Technology</title>
      <link rel="alternate" href="https://b.hatena.ne.jp/hotentry/it" />
      <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hatena-bookmark-technology</ore:sourceId>
      <ore:sourceName>Hatena Bookmark Technology</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://b.hatena.ne.jp/hotentry/it</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://b.hatena.ne.jp/hotentry/it.rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://note.com/kajinari/n/n19c73d819b14</ore:originalUrl>
      <ore:upstreamId>https://note.com/kajinari/n/n19c73d819b14</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hacker-news:7290991f7a3bb2d40872e5981134dc98</id>
    <title>Slopstrap – Make your site look hastily vibecoded</title>
    <updated>2026-11-20T15:24:11Z</updated>
    <published>2026-11-20T15:24:11Z</published>
    <link rel="alternate" href="https://slopstrap.mikelacher.com/" />
    <link rel="via" href="https://news.ycombinator.com/rss" />
    <category scheme="urn:ore-news:sources" term="hacker-news" label="Hacker News" />
    <author>
      <name>Hacker News</name>
    </author>
    <source>
      <id>urn:ore-news:source:hacker-news</id>
      <title>Hacker News</title>
      <link rel="alternate" href="https://news.ycombinator.com/" />
      <link rel="via" href="https://news.ycombinator.com/rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hacker-news</ore:sourceId>
      <ore:sourceName>Hacker News</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://news.ycombinator.com/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://news.ycombinator.com/rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://slopstrap.mikelacher.com/</ore:originalUrl>
      <ore:upstreamId>https://slopstrap.mikelacher.com/</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hatena-bookmark-technology:03aaab6ced6f20d9dfb996a8aa66ed2e</id>
    <title>https://alpo.ge/remark.pdf</title>
    <updated>2026-11-20T15:14:55Z</updated>
    <published>2026-11-20T15:14:55Z</published>
    <link rel="alternate" href="https://alpo.ge/remark.pdf" />
    <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    <category scheme="urn:ore-news:sources" term="hatena-bookmark-technology" label="Hatena Bookmark Technology" />
    <author>
      <name>Hatena Bookmark Technology</name>
    </author>
    <source>
      <id>urn:ore-news:source:hatena-bookmark-technology</id>
      <title>Hatena Bookmark Technology</title>
      <link rel="alternate" href="https://b.hatena.ne.jp/hotentry/it" />
      <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hatena-bookmark-technology</ore:sourceId>
      <ore:sourceName>Hatena Bookmark Technology</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://b.hatena.ne.jp/hotentry/it</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://b.hatena.ne.jp/hotentry/it.rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://alpo.ge/remark.pdf</ore:originalUrl>
      <ore:upstreamId>https://alpo.ge/remark.pdf</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:8f554e3b04b7468ca5373662a47622a2</id>
    <title>AWS Lambda adds support for Node.js 26</title>
    <updated>2026-11-20T15:00:00Z</updated>
    <published>2026-11-20T15:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/aws-lambda-nodejs-26/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;AWS Lambda now supports creating serverless applications using Node.js 26, for both Lambda Web Functions and Lambda Event Functions. Developers can use Node.js 26 as both a managed runtime and a base container image (Event Functions only). AWS will automatically apply updates to the managed runtime and base image as they become available.&lt;br&gt; &lt;br&gt; Node.js 26 is the latest long-term support release of Node.js and is expected to be supported for security and bug fixes until April 2029. With this release, you can use the latest Node.js 26 features in Lambda, such as the Temporal API for easier date, time, and time zone handling, and enhancements to the Fetch API. You can use Node.js 26 with &lt;a href="https://docs.powertools.aws.dev/lambda/typescript/latest/" target="_blank" rel="noopener noreferrer"&gt;Powertools for AWS Lambda (TypeScript)&lt;/a&gt;, a developer toolkit to implement serverless best practices and increase developer velocity. You can also use the full range of AWS deployment tools, including the Lambda console, AWS CLI, AWS Serverless Application Model (AWS SAM), AWS CDK, and AWS CloudFormation to deploy and manage serverless applications written in Node.js 26.&lt;br&gt; &lt;br&gt; The Node.js 26 runtime is available in all Regions where Web Functions and Event Functions are available.&lt;br&gt; &lt;br&gt; For more information about Node.js 26 in Lambda, refer to the &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/web-functions-nodejs.html" target="_blank" rel="noopener noreferrer"&gt;Web Function&lt;/a&gt; and &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/lambda-nodejs.html" target="_blank" rel="noopener noreferrer"&gt;Event Function&lt;/a&gt; documentation. For more information about AWS Lambda, visit our &lt;a href="https://aws.amazon.com/lambda/" target="_blank" rel="noopener noreferrer"&gt;product page&lt;/a&gt;.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/aws-lambda-nodejs-26/</ore:originalUrl>
      <ore:upstreamId>868b1482ea911460dde8fce321f42fbefbe6ee81</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:28e1f8de88bce379c63ddf442ce9a3a7</id>
    <title>Amazon S3 increases the read request rate for general purpose buckets by up to 2x</title>
    <updated>2026-11-20T15:00:00Z</updated>
    <published>2026-11-20T15:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/amazon-s3-increases-read-request-rate/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;Amazon S3 now supports at least 11,000 GET/HEAD requests per second, up from 5,500, for general purpose buckets.&lt;/p&gt; 
&lt;p&gt;With this higher request rate, you can retrieve data faster for read-intensive workloads such as machine learning training, data analytics, and data transfers. To maximize throughput, distribute your requests across multiple prefixes so that S3 can scale each one independently.&lt;/p&gt; 
&lt;p&gt;This increase applies automatically to your existing read requests in all AWS Regions, with no changes required to your applications and at no additional charge beyond standard S3 request pricing. To learn more, visit the &lt;a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/optimizing-performance.html" target="_blank"&gt;&lt;u&gt;Amazon S3 user guide&lt;/u&gt;&lt;/a&gt; and the &lt;a href="https://aws.amazon.com/s3/" target="_blank"&gt;&lt;u&gt;S3 product page&lt;/u&gt;&lt;/a&gt;.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/amazon-s3-increases-read-request-rate/</ore:originalUrl>
      <ore:upstreamId>0790daaa1090f191712c317bf63e4c639cc71bd7</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:6befb164f6ef50d0907e00883974a386</id>
    <title>AWS Lambda adds support for Python 3.15</title>
    <updated>2026-11-20T14:59:00Z</updated>
    <published>2026-11-20T14:59:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/aws-lambda-python-315/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;AWS Lambda now supports creating serverless applications using Python 3.15. Python 3.15 is generally available for Lambda Event Functions and is available in public preview for Lambda Web Functions. This is the first Python runtime for Web Functions, which until now only supported Node.js. With this launch, developers can also build web applications and APIs on Web Functions in Python. Developers can use Python 3.15 as both a managed runtime and a base container image (Event Functions only), and AWS will automatically apply updates to the managed runtime and base image as they become available.&lt;br&gt; &lt;br&gt; Python 3.15 is the latest release of Python. With this release, you can use the latest Python 3.15 features in Lambda, such as explicit lazy imports that can reduce function startup time, the new frozendict and sentinel built-in types, and an improved JIT compiler. You can use Python 3.15 with &lt;a href="https://docs.aws.amazon.com/powertools/python/latest/" target="_blank" rel="noopener noreferrer"&gt;Powertools for AWS Lambda (Python)&lt;/a&gt;, a developer toolkit to implement serverless best practices and increase developer velocity. You can also use the full range of AWS deployment tools, including the Lambda console, AWS CLI, AWS Serverless Application Model (AWS SAM), AWS CDK, and AWS CloudFormation to deploy and manage serverless applications written in Python 3.15.&lt;br&gt; &lt;br&gt; The Python 3.15 runtime is available in all Regions where Event Functions and Web Functions are available.&lt;br&gt; &lt;br&gt; For more information about Python 3.15 in Lambda, refer to the &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/lambda-python.html" target="_blank" rel="noopener noreferrer"&gt;Event Function&lt;/a&gt; and &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/web-functions-python.html" target="_blank" rel="noopener noreferrer"&gt;Web Function&lt;/a&gt; documentation. For more information about AWS Lambda, visit our &lt;a href="https://aws.amazon.com/lambda/" target="_blank" rel="noopener noreferrer"&gt;product page&lt;/a&gt;.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/aws-lambda-python-315/</ore:originalUrl>
      <ore:upstreamId>6295dee371511cb476d8efc418adcff2690071a1</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hatena-bookmark-technology:fd45176593de8b11dbc4a7dfc7f86841</id>
    <title>どれだけGeminiが賢くなってもAIオタクが避ける理由。ついに解消の可能性 - すまほん!!</title>
    <updated>2026-11-20T14:35:51Z</updated>
    <published>2026-11-20T14:35:51Z</published>
    <link rel="alternate" href="https://smhn.info/202611-gemini-subscription-third-party-harness-december-2" />
    <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    <category scheme="urn:ore-news:sources" term="hatena-bookmark-technology" label="Hatena Bookmark Technology" />
    <author>
      <name>Hatena Bookmark Technology</name>
    </author>
    <source>
      <id>urn:ore-news:source:hatena-bookmark-technology</id>
      <title>Hatena Bookmark Technology</title>
      <link rel="alternate" href="https://b.hatena.ne.jp/hotentry/it" />
      <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hatena-bookmark-technology</ore:sourceId>
      <ore:sourceName>Hatena Bookmark Technology</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://b.hatena.ne.jp/hotentry/it</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://b.hatena.ne.jp/hotentry/it.rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://smhn.info/202611-gemini-subscription-third-party-harness-december-2</ore:originalUrl>
      <ore:upstreamId>https://smhn.info/202611-gemini-subscription-third-party-harness-december-2</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hatena-bookmark-technology:8dfe5f826b26c1bdbda001dbf1848c1c</id>
    <title>1万円のシンセをAIで魔改造。電子楽器のファームウェア開放が始まった | ギズモード・ジャパン</title>
    <updated>2026-11-20T14:31:09Z</updated>
    <published>2026-11-20T14:31:09Z</published>
    <link rel="alternate" href="https://www.gizmodo.jp/article/0b0516f2-94f8-442e-bdae-2987f090be13/" />
    <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    <category scheme="urn:ore-news:sources" term="hatena-bookmark-technology" label="Hatena Bookmark Technology" />
    <author>
      <name>Hatena Bookmark Technology</name>
    </author>
    <source>
      <id>urn:ore-news:source:hatena-bookmark-technology</id>
      <title>Hatena Bookmark Technology</title>
      <link rel="alternate" href="https://b.hatena.ne.jp/hotentry/it" />
      <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hatena-bookmark-technology</ore:sourceId>
      <ore:sourceName>Hatena Bookmark Technology</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://b.hatena.ne.jp/hotentry/it</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://b.hatena.ne.jp/hotentry/it.rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://www.gizmodo.jp/article/0b0516f2-94f8-442e-bdae-2987f090be13/</ore:originalUrl>
      <ore:upstreamId>https://www.gizmodo.jp/article/0b0516f2-94f8-442e-bdae-2987f090be13/</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hacker-news:f59b0c40112a24333faf610cae9a3427</id>
    <title>Levent Alpöge claims proof of the Generalized Riemann Hypothesis [pdf]</title>
    <updated>2026-11-20T14:16:21Z</updated>
    <published>2026-11-20T14:16:21Z</published>
    <link rel="alternate" href="https://alpo.ge/remark.pdf" />
    <link rel="via" href="https://news.ycombinator.com/rss" />
    <category scheme="urn:ore-news:sources" term="hacker-news" label="Hacker News" />
    <author>
      <name>Hacker News</name>
    </author>
    <source>
      <id>urn:ore-news:source:hacker-news</id>
      <title>Hacker News</title>
      <link rel="alternate" href="https://news.ycombinator.com/" />
      <link rel="via" href="https://news.ycombinator.com/rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hacker-news</ore:sourceId>
      <ore:sourceName>Hacker News</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://news.ycombinator.com/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://news.ycombinator.com/rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://alpo.ge/remark.pdf</ore:originalUrl>
      <ore:upstreamId>https://alpo.ge/remark.pdf</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:eafa2e10f0716905c6bdf7fa5ddd58d8</id>
    <title>AWS launches standardized cost and rate columns in CUR 2.0 and Cost Explorer</title>
    <updated>2026-11-20T14:00:00Z</updated>
    <published>2026-11-20T14:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/aws-cur-cost-explorer/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;AWS Data Exports for Cost and Usage Report (CUR) 2.0 now includes standardized cost and rate columns that represent cost consistently across AWS purchase options, including On Demand, Savings Plans, Reserved Instances, EC2 Spot, and EC2 Capacity Blocks for ML. These 14 columns are added&amp;nbsp;when you enable Include Standardized cost and rate columns&amp;nbsp;while setting up a new&amp;nbsp;CUR 2.0 export or editing an existing CUR 2.0 and these columns have&amp;nbsp;the prefix cost_analytics_. With these new columns, you can quantify the savings you realize from commitments, discounts, and tiered pricing, and analyze amortized cost the same way for every pricing model with multiple payment options, directly in CUR 2.0.&lt;/p&gt; 
&lt;p&gt;Previously, calculating savings required combining CUR with Savings Plans rates and public price lists, and amortized cost used different columns for each pricing model. Now each line item carries billed, effective, list, contracted, public on-demand cost, the public equivalent of billed and effective cost before discounts, and a rate for each, so you can measure savings and amortized cost without building your own calculations. To add the columns, select Include&amp;nbsp;standardized cost and rate columns&amp;nbsp;when you create or edit a CUR 2.0 export. In Cost Explorer, choose the new cost types under Advanced options to see the same costs.&lt;/p&gt; 
&lt;p&gt;Standardized cost and rate&amp;nbsp;columns are available at no additional charge in all AWS Regions except the AWS GovCloud (US) Regions and the China Regions. To learn more, see the &lt;a href="https://docs.aws.amazon.com/cur/latest/userguide/table-dictionary-cur2.html"&gt;CUR 2.0 data dictionary&lt;/a&gt; and the &lt;a href="https://docs.aws.amazon.com/cost-management/latest/userguide/ce-advanced.html"&gt;user guide for Cost Explorer&lt;/a&gt;.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/aws-cur-cost-explorer/</ore:originalUrl>
      <ore:upstreamId>c49daaabd2b33202fd7d47ade7aca9eff2fdd0f3</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hacker-news:e9860039260381d32c4f58a2423f67fe</id>
    <title>Nasdaq erases all 2026 gains as AI sell-off dampens Anthropic’s second day</title>
    <updated>2026-11-20T13:29:59Z</updated>
    <published>2026-11-20T13:29:59Z</published>
    <link rel="alternate" href="https://www.theguardian.com/business/2026/nov/20/global-stock-markets-slump-anthropic-ipo-ai-sell-off" />
    <link rel="via" href="https://news.ycombinator.com/rss" />
    <category scheme="urn:ore-news:sources" term="hacker-news" label="Hacker News" />
    <author>
      <name>Hacker News</name>
    </author>
    <source>
      <id>urn:ore-news:source:hacker-news</id>
      <title>Hacker News</title>
      <link rel="alternate" href="https://news.ycombinator.com/" />
      <link rel="via" href="https://news.ycombinator.com/rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hacker-news</ore:sourceId>
      <ore:sourceName>Hacker News</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://news.ycombinator.com/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://news.ycombinator.com/rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://www.theguardian.com/business/2026/nov/20/global-stock-markets-slump-anthropic-ipo-ai-sell-off</ore:originalUrl>
      <ore:upstreamId>https://www.theguardian.com/business/2026/nov/20/global-stock-markets-slump-anthropic-ipo-ai-sell-off</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hatena-bookmark-technology:5748fdfe1ed426ae330e6037f42d76c8</id>
    <title>SSDの価格は2027年後半に下落し始める可能性あり</title>
    <updated>2026-11-20T13:06:42Z</updated>
    <published>2026-11-20T13:06:42Z</published>
    <link rel="alternate" href="https://gigazine.net/news/20261120-ssd-prices-outlook/" />
    <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    <category scheme="urn:ore-news:sources" term="hatena-bookmark-technology" label="Hatena Bookmark Technology" />
    <author>
      <name>Hatena Bookmark Technology</name>
    </author>
    <source>
      <id>urn:ore-news:source:hatena-bookmark-technology</id>
      <title>Hatena Bookmark Technology</title>
      <link rel="alternate" href="https://b.hatena.ne.jp/hotentry/it" />
      <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hatena-bookmark-technology</ore:sourceId>
      <ore:sourceName>Hatena Bookmark Technology</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://b.hatena.ne.jp/hotentry/it</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://b.hatena.ne.jp/hotentry/it.rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://gigazine.net/news/20261120-ssd-prices-outlook/</ore:originalUrl>
      <ore:upstreamId>https://gigazine.net/news/20261120-ssd-prices-outlook/</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:3bd6a9099afe50cd2570de35fe89a347</id>
    <title>AWS CloudFormation increases the default stacks per account quota to 300,000</title>
    <updated>2026-11-20T12:35:00Z</updated>
    <published>2026-11-20T12:35:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/cloudformation-stacks-per-account-quota/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;AWS CloudFormation now supports up to 300,000 stacks in each AWS account and Region by default (previously 2,000), which enables you to add stacks as your workloads grow without requesting a quota increase. CloudFormation manages related AWS resources as a stack that you create, update, and delete as one unit. Teams that deploy a separate stack for each customer, environment, or developer can now scale those patterns within a single account.&lt;/p&gt; 
&lt;p&gt;A higher default quota allows you to keep growing workloads in the accounts where they already run. Previously, accounts that needed more than 2,000 stacks in a Region requested a quota increase through Service Quotas. Now, the default quota covers these workloads without a request. For example, a software provider that deploys one stack for each customer can grow from 2,000 to 300,000 customer stacks in one account and Region. Existing stacks work without changes.&lt;/p&gt; 
&lt;p&gt;The higher quota applies to stacks you create in the CloudFormation console or with the AWS CLI, AWS SDKs, AWS CDK, or AWS SAM. To view your stacks per account quota, open the Service Quotas console. For more information, see &lt;a href="https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cloudformation-limits.html" target="_blank" rel="noopener noreferrer"&gt;CloudFormation quotas&lt;/a&gt; in the AWS CloudFormation User Guide. The increased quota is available at no additional charge in all AWS Regions where AWS CloudFormation is supported. For Region availability, see the &lt;a href="https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/"&gt;AWS Region table&lt;/a&gt;.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/cloudformation-stacks-per-account-quota/</ore:originalUrl>
      <ore:upstreamId>36c6387bf5eb3fd6c685662dedce9c6a02d52b79</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hatena-bookmark-technology:1beffbce7a3f708310269f56cf60c87a</id>
    <title>「Windows Server 2028」で「WSUS」や「SMB 1.0」、「VBScript」などが削除へ／「Windows PowerShell 5.1」「WDS」は非推奨に、レガシーBIOSでの起動も不可</title>
    <updated>2026-11-20T11:11:54Z</updated>
    <published>2026-11-20T11:11:54Z</published>
    <link rel="alternate" href="https://forest.watch.impress.co.jp/docs/news/2158261.html" />
    <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    <category scheme="urn:ore-news:sources" term="hatena-bookmark-technology" label="Hatena Bookmark Technology" />
    <author>
      <name>Hatena Bookmark Technology</name>
    </author>
    <source>
      <id>urn:ore-news:source:hatena-bookmark-technology</id>
      <title>Hatena Bookmark Technology</title>
      <link rel="alternate" href="https://b.hatena.ne.jp/hotentry/it" />
      <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hatena-bookmark-technology</ore:sourceId>
      <ore:sourceName>Hatena Bookmark Technology</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://b.hatena.ne.jp/hotentry/it</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://b.hatena.ne.jp/hotentry/it.rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://forest.watch.impress.co.jp/docs/news/2158261.html</ore:originalUrl>
      <ore:upstreamId>https://forest.watch.impress.co.jp/docs/news/2158261.html</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:ca739f2c09d4c31693d52629a3b21f69</id>
    <title>AgentCore runtime instances now support Amazon EC2 G7 instances</title>
    <updated>2026-11-20T10:00:00Z</updated>
    <published>2026-11-20T10:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/agentcore-ec2-g7/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;Amazon Bedrock AgentCore &lt;a href="https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-instances.html"&gt;runtime instances&lt;/a&gt; now support Amazon EC2 G7 instances, powered by NVIDIA RTX PRO 4500 Blackwell Server Edition GPUs. Runtime instances run your agents on Amazon EC2 instances while AgentCore handles provisioning, patching, scaling, and lifecycle management. G7 instances give agents that do 3D rendering or model inference another GPU option, alongside families such as G6e and G7e.&lt;/p&gt; 
&lt;p&gt;To use G7, add G7 instance types, from g7.2xlarge to g7.48xlarge, to the allowed instance types of your capacity provider. AgentCore installs the NVIDIA drivers on the instance, so standard container images run GPU workloads without bundling drivers. For example, an agent can render 3D scenes or run a vision model on its own GPU, in &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/08/aws-bedrock-agentcore-runtime-instances-generally-available/"&gt;sessions of up to 14 days&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;G7 instances on runtime instances are available in select AWS Regions: US East (N. Virginia), US East (Ohio), US West (Oregon), Europe (Frankfurt), Europe (London), Europe (Stockholm), Asia Pacific (Mumbai), and Asia Pacific (Sydney). You are charged for managing the provisioned compute, in addition to your Amazon EC2 costs.&lt;/p&gt; 
&lt;p&gt;To get started, see the following resources:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;a href="https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-instances-how-it-works.html#runtime-instances-gpu"&gt;Use GPU instance types&lt;/a&gt; in the Amazon Bedrock AgentCore Developer Guide&lt;/li&gt; 
 &lt;li&gt;&lt;a href="https://aws.amazon.com/bedrock/agentcore/pricing/"&gt;AgentCore pricing&lt;/a&gt;&lt;/li&gt; 
&lt;/ul&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/agentcore-ec2-g7/</ore:originalUrl>
      <ore:upstreamId>a687e4c378ce1715ae055850ef22e8bf251679c0</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:9dbc90e01743433d9db028371f79a5ea</id>
    <title>​​​Amazon RDS for Db2 now supports renaming databases​</title>
    <updated>2026-11-20T08:53:00Z</updated>
    <published>2026-11-20T08:53:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/amazon-rds-db2-supports-rename-databases" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;​​Amazon Relational Database Service (Amazon RDS) for Db2 now supports renaming databases in place. You can rename a database on your DB instance by calling the new rdsadmin.rename_database stored procedure. Previously, renaming a database required you to back it up and restore it under a new name. With rename, the database keeps its data in place, so it's faster than backing up and restoring the database.​&lt;/p&gt; 
&lt;p&gt;​​Database rename simplifies workflows such as replacing a database with a restored copy. For example, after you restore a copy of a database from a backup, you can rename the original database, and then give its name to the restored copy, without changing your application connection strings. Database rename runs as a background task that you can monitor with rdsadmin.get_task_status.​&amp;nbsp;&lt;/p&gt; 
&lt;p&gt;​​Database rename is available in all AWS Regions where Amazon RDS for Db2 is offered. To get started, see the &lt;a href="https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/db2-managing-databases.html#db2-renaming-database" target="_blank"&gt;Amazon RDS User Guide&lt;/a&gt;.​​&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/amazon-rds-db2-supports-rename-databases</ore:originalUrl>
      <ore:upstreamId>a05d2de881d535cacc1454a3313655a7727e58b3</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:046bf796658d9e6f42b23d89d816e8b2</id>
    <title>Amazon RDS for Db2 now supports new Canadian time zones</title>
    <updated>2026-11-20T08:49:00Z</updated>
    <published>2026-11-20T08:49:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/amazon-rds-db2-supports-new-canadian-time" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;​​Amazon RDS for Db2 now supports four new time zones, America/Vancouver, America/Edmonton, America/Inuvik, and America/Winnipeg, that reflect the updated local time rules for British Columbia, Alberta, the Northwest Territories, and Manitoba in Canada. As of November 1, 2026, these provinces and territories observe permanent daylight saving time and no longer set their clocks back by an hour.​&lt;/p&gt; 
&lt;p&gt;​Data stored in UTC is unaffected, but values based on the instance's local time, such as CURRENT TIMESTAMP, CURRENT DATE, default timestamp columns, scheduled jobs, and business-day batch logic, can be affected. With these new time zones, you can keep local time values accurate for workloads operating in these regions.&amp;nbsp;&lt;/p&gt; 
&lt;p&gt;​​You can select the new time zones when you create a new RDS for Db2 instance. To change the time zone of an existing instance, contact AWS Support, as modifying the time zone of an existing instance is not supported through the AWS CLI, API, or SDK. If your instances serve workloads in these regions, we recommend reviewing them and updating your time zone configuration to avoid incorrect local times in your applications.​&lt;/p&gt; 
&lt;p&gt;​The new time zones are available in all AWS Regions where Amazon RDS for Db2 is offered. To learn more and see the full list of supported time zones, visit the Amazon RDS for Db2 time zone &lt;a href="https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/db2-time-zone.html" target="_blank"&gt;documentation&lt;/a&gt;.​&amp;nbsp;&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/amazon-rds-db2-supports-new-canadian-time</ore:originalUrl>
      <ore:upstreamId>441ec56587a15f30865bfca9cd4ae816786549ed</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:6c12055d210c3fa1b0411f2d4b751e09</id>
    <title>Amazon RDS for Db2 now supports object-level audit policies</title>
    <updated>2026-11-20T08:34:00Z</updated>
    <published>2026-11-20T08:34:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/amazon-rds-db2-supports-object-level-audit-policies" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;Amazon RDS for Db2 now supports object-level audit policies, giving you fine-grained control over which database objects are audited. You can create custom audit policies and attach them to specific tables, users, groups, roles, and authorities in your RDS for Db2 databases.&lt;/p&gt; 
&lt;p&gt;With object-level audit policies, you can focus on auditing the objects that matter most — for example, a single table that contains sensitive data or a specific user — without generating audit records for your entire database. Object-level audit policies complement the existing database-level audit logging in Amazon RDS for Db2. You can use both at the same time, and they operate independently.&amp;nbsp;&lt;/p&gt; 
&lt;p&gt;Amazon RDS provides stored procedures to create, modify, attach, detach, and drop object-level audit policies. Audit records are uploaded to the same Amazon S3 bucket that you configured for Db2 audit logging.&lt;/p&gt; 
&lt;p&gt;Object-level audit policies for Amazon RDS for Db2 are available in all AWS Regions where Amazon RDS for Db2 is available. To get started see the &lt;a href="https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/db2-object-level-audit.html" target="_blank"&gt;Amazon RDS User Guide.&lt;/a&gt;&amp;nbsp;&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/amazon-rds-db2-supports-object-level-audit-policies</ore:originalUrl>
      <ore:upstreamId>8144e0fc9a2fddd08dd358907062dfa7191f13bf</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:ebc1ff1ea9824608766a1f9489a08387</id>
    <title>Amazon RDS Custom now supports the latest Cumulative Update and GDR updates for Microsoft SQL Server</title>
    <updated>2026-11-20T08:30:00Z</updated>
    <published>2026-11-20T08:30:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/amazon-rds-custom-supports-latest-cumulative-update-gdr-microsoft-sql-server/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;&lt;a href="https://aws.amazon.com/rds/custom/" target="_blank"&gt;Amazon Relational Database Service (Amazon RDS) Custom for SQL Server&lt;/a&gt; now supports the latest Cumulative Updates (CU) and General Distribution Release (GDR) updates for Microsoft SQL Server. This release includes support for SQL Server 2019 CU32 + GDR &lt;a href="https://support.microsoft.com/en-us/servicing/sql/sql-server-2019/cumulative-update/kb5128494-cu32-gdr-october-2026" target="_blank"&gt;KB5128494&lt;/a&gt; (RDS version 15.00.4500.2.v1) and SQL Server 2022 CU27 + GDR &lt;a href="https://support.microsoft.com/en-us/servicing/sql/sql-server-2022/cumulative-update/kb5126934-cu27-gdr-october-2026" target="_blank"&gt;KB5126934&lt;/a&gt; (RDS version 16.00.4305.5.v1). &lt;/p&gt; 
&lt;p&gt;For additional information on the improvements and fixes included in these updates, see Microsoft documentation for KB5128494 and KB5126934. You can upgrade your Amazon RDS Custom for SQL Server instances to apply these recommended updates using Amazon RDS Management Console, or by using the AWS SDK or CLI. To learn more about upgrading your database instances, see &lt;a href="https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/custom-upgrading-sqlserver.html" target="_blank"&gt;Amazon RDS Custom User Guide&lt;/a&gt;.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/amazon-rds-custom-supports-latest-cumulative-update-gdr-microsoft-sql-server/</ore:originalUrl>
      <ore:upstreamId>89ab64b8a98abd06c9bd0bbf854350ff17660ea0</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:a762e807692e51da9bf7150543889c9e</id>
    <title>Amazon Route 53 now supports Availability Zone (AZ) affinity routing</title>
    <updated>2026-11-20T08:21:00Z</updated>
    <published>2026-11-20T08:21:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/route-53-affinity-routing/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;Amazon Route 53 now supports Availability Zone (AZ) affinity routing, which routes DNS queries from your VPCs to resources in the same AZ as the client that sends the query. This helps you keep traffic within the same AZ as the client, reducing latency and improving application performance.&lt;/p&gt; 
&lt;p&gt;Until now, customers who wanted lower latency used other routing policies, such as latency-based or geoproximity routing. With this launch, DNS queries from your clients are answered with resources in the same AZ. This keeps traffic within the AZ and gives your clients faster responses. If there's no record for the client's AZ, Route 53 falls back to a record for a less specific location: the Zone Group, then the AWS Region, and then Global, in the same order.&lt;/p&gt; 
&lt;p&gt;To get started, create AZ-affinity records and choose a location type for each: Availability Zone, Zone Group, Region, or Global. For Availability Zone records, specify the AZ ID, such as use1-az1. You can associate a health check with any AZ-affinity record, whether it's for an AZ, a Zone Group, or a Region. If the endpoint is unhealthy, Route 53 answers with the record for the next location. You can use AZ-affinity routing for records in both public and private hosted zones. The Global record answers queries that don't come from your VPCs, such as queries from the internet. You can create AZ-affinity records with the Route 53 console, API, AWS CLI, AWS SDKs, and AWS CloudFormation.&lt;/p&gt; 
&lt;p&gt;AZ-affinity routing is available in all AWS commercial Regions where Route 53 public and private hosted zones are available. To learn more, see the &lt;a href="https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-policy-azaffinity.html"&gt;AZ-affinity routing&lt;/a&gt; topic in the Route 53 Developer Guide. For pricing, see the &lt;a href="https://aws.amazon.com/route53/pricing/"&gt;Route 53 pricing page&lt;/a&gt;.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/route-53-affinity-routing/</ore:originalUrl>
      <ore:upstreamId>39e7c7710482cd5e4cbfe8b1fd43fc6589cf25ed</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:d951c12adbb4d3e8c49f88e4e0349293</id>
    <title>Amazon VPC IPAM policies now support automated internet firewall and AWS Lambda Web Functions and MicroVMs</title>
    <updated>2026-11-20T08:06:00Z</updated>
    <published>2026-11-20T08:06:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/vpc-ipam-policies-firewall-lambda/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;Amazon Virtual Private Cloud (VPC) IP Address Manager (IPAM) policies now support AWS Network Firewall automated internet firewall and AWS Lambda Web Functions and MicroVMs. You can centrally configure IPAM policies across AWS accounts and AWS Regions to allocate public IPv4 addresses to these resources from specific IPAM pools, such as Bring Your Own IP (BYOIP) addresses or Amazon-provided contiguous IPv4 blocks. This enables a stronger security posture, simplifies network and security operations, and can reduce public IPv4 costs when you use BYOIP.&lt;/p&gt; 
&lt;p&gt;Many customers allowlist the public IPs of their AWS resources in network access control lists (ACLs) and firewalls. Previously, keeping these resources on allowlisted addresses depended on each application team. With this launch, you can define allocation rules for them alongside existing resource types, so security teams can add IP-based filters with confidence that these resources draw addresses from approved ranges. For Lambda Web Functions and MicroVMs, this covers the public IPv4 addresses used for outbound traffic through Lambda Network Connectors. If a pool runs out of addresses, resources fall back to Amazon-provided addresses. You can also share allocated ranges with partners through IPAM integration with AWS prefix lists.&lt;/p&gt; 
&lt;p&gt;The feature is available in all AWS commercial Regions, in both the Free Tier and Advanced Tier of VPC IPAM. To learn more, see the &lt;a href="https://docs.aws.amazon.com/vpc/latest/ipam/define-public-ipv4-allocation-strategy-with-ipam-policies.html"&gt;IPAM policies documentation page&lt;/a&gt; and the &lt;a href="https://docs.aws.amazon.com/vpc/latest/ipam/what-it-is-ipam.html"&gt;IPAM documentation&lt;/a&gt;. For pricing details, see the IPAM tab on the &lt;a href="https://aws.amazon.com/vpc/pricing/"&gt;Amazon VPC Pricing page&lt;/a&gt;&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/vpc-ipam-policies-firewall-lambda/</ore:originalUrl>
      <ore:upstreamId>329aece692ba170b23a976ea72eaa40d12b73ec2</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:f497e31adca2d2c46853040f5e3481da</id>
    <title>Amazon Route 53 now offers Advanced Hosted Zones</title>
    <updated>2026-11-20T08:00:00Z</updated>
    <published>2026-11-20T08:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/route-53-offers-advanced-hosted-zones/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;Amazon Route 53 now offers Advanced Hosted Zones, a new hosted zone tier with additional guardrails, visibility, and resilience features. Advanced Hosted Zones include Change Guardrails that prevent accidental record deletions, record-level Change History, and public DNS fallback in private hosted zones.&lt;/p&gt;
&lt;p&gt;A single mistaken DNS change can take part of your domain offline, such as deleting a record that is still serving traffic or removing a delegation that resolvers are still using. To protect against this, customers build their own validation pipelines, review processes, and audit tooling. With Change Guardrails turned on, Route 53 checks each change before applying it. It blocks deleting a record that is still receiving DNS queries, a record that an alias record in the same hosted zone points to, or a delegation that is still in use. When a guardrail blocks a change, Route 53 rejects the whole request with an error that explains why, and no records change. Guardrails apply to every change, including changes from infrastructure as code tools. Change History gives you a record-level history of changes to your hosted zone, retained for 365 days, so you can see what changed and when.&lt;/p&gt;
&lt;p&gt;To get started, create a new Advanced Hosted Zone or upgrade an existing hosted zone, then turn on the guardrails you want. You can use the Route 53 console, API, AWS CLI, AWS SDKs, or AWS CloudFormation. Advanced Hosted Zones are priced separately from Standard Hosted Zones. For rates, see the &lt;a href="https://aws.amazon.com/route53/pricing/"&gt;Route 53 pricing page&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Advanced Hosted Zones are available in all AWS commercial Regions where Route 53 public and private hosted zones are available. To learn more, see &lt;a href="https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/hosted-zone-tiers.html" target="_blank"&gt;Advanced Hosted Zones&lt;/a&gt; in the Route 53 Developer Guide.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/route-53-offers-advanced-hosted-zones/</ore:originalUrl>
      <ore:upstreamId>9d4c03479481780c274b9f47d18c33227f62102c</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:e0abf039ce5e49fe1272da446e17a079</id>
    <title>Announcing a new skill for AI agents in Amazon Textract Core</title>
    <updated>2026-11-20T08:00:00Z</updated>
    <published>2026-11-20T08:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/amazon-textract-core-skill-ai-agents/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;Amazon Textract Core now lets AI agents extract text, tables, forms, and other data from documents through a skill, with no server to run or infrastructure to deploy. The skill guides an agent to the right Amazon Textract Core API for each document and includes a tested parser that converts the output into reading-order text and structured fields, such as answers to questions, receipt and invoice details, and identity document fields. Previously, teams that connected an agent to Amazon Textract had to build and maintain their own integration.&lt;/p&gt;
&lt;p&gt;You ask in natural language, and the agent returns the answers you need. The skill processes multi-page PDFs and returns every page in reading order. It uses confidence scores to accept high-confidence results and flags the rest, so you can route them to your own review process. For example, you can ask an agent to turn a patient's intake form into structured data and flag unclear fields for staff review.&lt;/p&gt;
&lt;p&gt;The skill is available at no additional charge, and standard &lt;a href="https://aws.amazon.com/textract/pricing/" target="_blank"&gt;Amazon Textract pricing applies&lt;/a&gt;. It is available in all commercial AWS Regions where Amazon Textract is available, including: US East (Ohio), US East (N. Virginia), US West (N. California), US West (Oregon), Asia Pacific (Mumbai), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Canada (Central), Europe (Frankfurt), Europe (Ireland), Europe (London), Europe (Paris), Europe (Spain), and Europe (Zurich). If you use the AWS MCP server with the aws-core plugin, your agent can load the skill automatically. The skill is also published in the AWS Agent Toolkit, so agents including Kiro, Claude Code, and Cursor can use it. To learn more, see the AWS &lt;a href="https://github.com/aws/agent-toolkit-for-aws" target="_blank"&gt;Agent Toolkit on GitHub&lt;/a&gt;.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/amazon-textract-core-skill-ai-agents/</ore:originalUrl>
      <ore:upstreamId>f20db42f0570aec9fea6f0a1e64d4679280d8c5a</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:dcc9868492dadb1657bb9f7b606545dd</id>
    <title>Announcing the general availability of a new AWS Local Zone in Bogotá, Colombia</title>
    <updated>2026-11-20T08:00:00Z</updated>
    <published>2026-11-20T08:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/aws-local-zone-bogota-colombia/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;Today, AWS announces the general availability of a new Local Zone in Bogotá, Colombia, bringing AWS infrastructure closer to end users for applications that require single-digit millisecond latency. You can use the Bogotá Local Zone for workloads such as real-time gaming, live video streaming, medical imaging, and financial transaction processing.&lt;/p&gt; 
&lt;p&gt;AWS Local Zones are infrastructure deployments that place compute, storage, networking, and other select AWS services closer to metropolitan areas, with the same APIs and tools as AWS Regions. You pay only for what you use, with no minimum commitment. Pricing options include On-Demand, Savings Plans, and Spot Instances. AWS Local Zones are available in more than 30 locations worldwide.&lt;/p&gt; 
&lt;p&gt;The AWS Local Zone in Bogotá supports&amp;nbsp;Amazon Elastic Compute Cloud (Amazon EC2) with C7i, M7i, and R7i instances, Amazon S3 with the One Zone-Infrequent Access storage class, Amazon EBS with local snapshots and volume types gp3, gp2, and io1, Amazon Elastic Container Service (Amazon ECS), Amazon Elastic Kubernetes Service (Amazon EKS), Amazon Virtual Private Cloud (Amazon VPC), AWS Direct Connect, and Application Load Balancer. &amp;nbsp;&lt;/p&gt; 
&lt;p&gt;To get started, enable the AWS Local Zone in Bogotá (us-east-1-bog-1a) from the &lt;a href="https://us-east-1.console.aws.amazon.com/ec2globalview/home"&gt;Regions and Zones&lt;/a&gt; tab in the AWS Global View or by using the &lt;a href="https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_ModifyAvailabilityZoneGroup.html?refid=769a1a2b-8c19-4976-9c45-b6b1226c7d20"&gt;ModifyAvailabilityZoneGroup&lt;/a&gt; API. For pricing information, visit the &lt;a href="https://aws.amazon.com/about-aws/global-infrastructure/localzones/pricing/?nc=sn&amp;amp;loc=4"&gt;AWS Local Zones pricing page&lt;/a&gt;.&amp;nbsp;To learn more, visit the &lt;a href="https://aws.amazon.com/about-aws/global-infrastructure/localzones/"&gt;AWS Local Zones overview page&lt;/a&gt;.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/aws-local-zone-bogota-colombia/</ore:originalUrl>
      <ore:upstreamId>08dbc148bb7d0b59e3d0e5c7c9161da74da6c579</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:dba5f5f927d8bcde4431a4aeb0a7bc26</id>
    <title>AWS Secrets Store CSI Driver Provider now supports AssumeRole for cross-account secret access</title>
    <updated>2026-11-20T08:00:00Z</updated>
    <published>2026-11-20T08:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/secrets-store-csi-driver-assumerole/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;The AWS Secrets Store CSI Driver Provider now supports AssumeRole (role-chaining), allowing Kubernetes pods to access secrets and parameters across AWS accounts by assuming an IAM role in the account where the secrets are stored. Previously, customers reading cross-account secrets needed to add a resource policy to each secret and use a customer-managed KMS key, as the AWS managed key (aws/secretsmanager) cannot be used for cross-account access. Now, teams can name a target role in the SecretProviderClass, and the provider assumes that role to fetch the secrets.&lt;/p&gt;
&lt;p&gt;With AssumeRole support, customers managing hundreds of AWS accounts and thousands of services can simplify cross-account secret access. A single trust policy on one target role replaces resource policies on each secret. Secrets encrypted with the AWS managed key (aws/secretsmanager) and SSM parameters become readable across accounts. The target account sees workload-specific session names in CloudTrail events for better attribution. This feature works with both IAM Roles for Service Accounts (IRSA) and EKS Pod Identity on initial mount and rotation, and supports failover regions.&lt;/p&gt;
&lt;p&gt;AssumeRole support is available in all AWS Regions where Amazon EKS and the AWS Secrets Store CSI Driver Provider are available.&lt;/p&gt;
&lt;p&gt;To learn more, see the &lt;a href="https://docs.aws.amazon.com/secretsmanager/latest/userguide/integrating_ascp_assume_role.html" target="_blank"&gt;Assume an IAM role to retrieve secrets with the ASCP&lt;/a&gt; documentation.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/secrets-store-csi-driver-assumerole/</ore:originalUrl>
      <ore:upstreamId>a41425c4d97e2ae440c1734f4711c62db2c8bc7c</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:d6072f9194724baeb55527db57111b0a</id>
    <title>Amazon SageMaker adds new capabilities – improved blueprints and catalog experience, simplified data quality monitoring, and support for DuckDB 2.0 and DuckDB extensions</title>
    <updated>2026-11-20T08:00:00Z</updated>
    <published>2026-11-20T08:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/amazon-sagemaker-adds-new-capabilities/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;&lt;b&gt;Improved blueprints:&lt;/b&gt; Amazon SageMaker Unified Studio now gives project teams more ownership of their data and resources, within governance policies that administrators set centrally. Additional releases include faster notebook queries through DuckDB 2.0 support and data quality monitoring at catalog scale.&lt;/p&gt;
&lt;p&gt;&lt;b&gt;Improved data quality monitoring:&lt;/b&gt; Teams can also profile entire catalogs and databases to keep data statistics current. Project members can get email notifications for all supported notification types, including data quality and data profiling runs.&lt;/p&gt;
&lt;p&gt;&lt;b&gt;Improved catalog experience:&lt;/b&gt; Administrators can now manage metadata forms, business glossaries, and custom asset types in one place, with a consistent experience across all domain types. They can also transfer asset ownership to the project that knows the data best. Members of that project can then curate those assets and approve or reject subscription requests themselves. With resource blueprints, administrators can allow projects to deploy approved resources, such as Amazon EMR Serverless applications. Teams can then provision what they need without waiting for an administrator.&lt;/p&gt;
&lt;p&gt;&lt;b&gt;Support for DuckDB 2.0 and extensions:&lt;/b&gt; SageMaker notebooks now support DuckDB 2.0 and DuckDB extensions. Data engineers, analysts, and data scientists get faster queries over Amazon S3 data, plus access to more file formats, data source connectors, and functions such as excel, geospatial and full-text search.&lt;/p&gt;
&lt;p&gt;These capabilities are available in all &lt;a href="https://docs.aws.amazon.com/sagemaker-unified-studio/latest/adminguide/supported-regions.html" target="_blank"&gt;AWS Regions&lt;/a&gt; where SageMaker Unified Studio is supported. To learn more, visit &lt;a href="https://docs.aws.amazon.com/sagemaker-unified-studio/latest/userguide/catalog-manage.html" target="_blank"&gt;Manage the catalog&lt;/a&gt;, &lt;a href="https://docs.aws.amazon.com/sagemaker-unified-studio/latest/userguide/catalog-iam-based-domains.html" target="_blank"&gt;Working with data and catalog in IAM-based domains&lt;/a&gt;, &lt;a href="https://docs.aws.amazon.com/sagemaker-unified-studio/latest/adminguide/resource-blueprints.html" target="_blank"&gt;Deploy on-demand blueprints&lt;/a&gt;, and &lt;a href="https://docs.aws.amazon.com/sagemaker-unified-studio/latest/userguide/notebooks.html" target="_blank"&gt;Notebooks&lt;/a&gt;.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/amazon-sagemaker-adds-new-capabilities/</ore:originalUrl>
      <ore:upstreamId>255d47ae422bd715c398eecdd5ce7f14c928f510</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:c279f1bdef7ac67e55ef96e727a96cfa</id>
    <title>AWS Agent Registry now offers naming and public discovery capabilities</title>
    <updated>2026-11-20T08:00:00Z</updated>
    <published>2026-11-20T08:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/agent-registry-naming-public-discovery/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;AWS Agent Registry now offers public naming capabilities, making it easy to attach verified domain names to your agents and AI tools. Developers and network admins can perform domain verification checks to prove domain ownership, then associate the verified domain names with their agents to promote them for public visibility beyond their registry and AWS account.&lt;/p&gt;
&lt;p&gt;Previously, developers had to manually configure how agents discover and connect to one another, which added complexity to building multi-agent systems. With this launch, since the public agent records are anchored to a verified domain identity, you can confirm the source of an agent before connecting to it. Once published, agent records are searchable by any AWS-authenticated user using both semantic and lexical search.&lt;/p&gt;
&lt;p&gt;This capability is available at no additional charge at this time in all AWS Regions where AWS Agent Registry is available. To learn more about naming and public discovery, visit the &lt;a href="https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/registry.html" target="_blank"&gt;AWS Agent Registry documentation&lt;/a&gt;.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/agent-registry-naming-public-discovery/</ore:originalUrl>
      <ore:upstreamId>e24002814dd4404b18c234c08f571ab0573ddf0b</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:b7cc508e022d25d6213e84da394984fe</id>
    <title>AWS DevOps Agent reduces investigation latency</title>
    <updated>2026-11-20T08:00:00Z</updated>
    <published>2026-11-20T08:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/devops-agent-reduces-latency/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;When an incident is occurring, mean time to recover needs to be as fast as possible.&lt;/p&gt;
&lt;p&gt;With this launch, incident investigations performed by AWS DevOps Agent complete faster. Investigations now also include a real-time summary that is updated with the current state of an investigation, so initial findings and observations surface quickly, before a final root cause and mitigation plan are created. For customers using AWS DevOps Agent's built in Slack integration, these summaries are also automatically pushed to the relevant Slack channel.&lt;/p&gt;
&lt;p&gt;See all the latest AWS DevOps Agent features on the &lt;a href="https://docs.aws.amazon.com/devopsagent/latest/userguide/whats-new.html" target="_blank"&gt;release history&lt;/a&gt; page. For the list of AWS Regions where AWS DevOps Agent is available, see the &lt;a href="https://docs.aws.amazon.com/devopsagent/latest/userguide/about-aws-devops-agent-supported-regions.html" target="_blank"&gt;supported Regions table&lt;/a&gt;.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/devops-agent-reduces-latency/</ore:originalUrl>
      <ore:upstreamId>029e03bf745c856a8bd7ae3ae9a177382fef2e76</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:b27fec271228527d9e131880b0ecddd7</id>
    <title>Announcing Test Insights for AWS Device Farm</title>
    <updated>2026-11-20T08:00:00Z</updated>
    <published>2026-11-20T08:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/device-farm-test-insights/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;&lt;a href="https://aws.amazon.com/device-farm/"&gt;AWS Device Farm&lt;/a&gt;, a service for testing mobile and web apps, now provides Test Insights for Appium, Espresso, and XCUITest runs across multiple devices. Test Insights helps you and AI agents understand the health of your tests and resolve failures faster by providing a detailed breakdown of your test suite by device and by test.&lt;/p&gt;
&lt;p&gt;With Test Insights, Device Farm's existing APIs now return enhanced test metadata, failure root cause with stack trace, a video for each test, start and stop times, median and average times spent on each device and test, and test counts by result. With this data in one place, your agents spend less time and fewer tokens looking for the root cause of test failures, and the &lt;a href="https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/specialized-skills/web-and-mobile-development/troubleshooting-aws-device-farm-runs" target="_blank"&gt;AWS Device Farm troubleshooting skill&lt;/a&gt; uses it to help diagnose failed runs and suggest fixes. Test Insights is available alongside any default and custom test reports you generate, at no additional cost.&lt;/p&gt;
&lt;p&gt;Test Insights is included in all &lt;a href="https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/"&gt;AWS Regions&lt;/a&gt; where Device Farm is available.&lt;/p&gt;
&lt;p&gt;To get started, see &lt;a href="https://docs.aws.amazon.com/devicefarm/latest/developerguide/reports.html#reports-test-insights" target="_blank"&gt;Test Insights&lt;/a&gt; in the AWS Device Farm Developer Guide.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/device-farm-test-insights/</ore:originalUrl>
      <ore:upstreamId>1f01e3ca232c83fc0c90c86db9e43a7a5344cd4d</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:a8352a3405292f6c091c1a945bfcd460</id>
    <title>Amazon Route 53 private hosted zones now support public DNS fallback</title>
    <updated>2026-11-20T08:00:00Z</updated>
    <published>2026-11-20T08:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/route-53-public-dns-fallback/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;Amazon Route 53 private hosted zones now support public DNS fallback. When a query for a name in your private hosted zone's domain doesn't match a record in the zone, Route 53 returns the answer from public DNS instead of a "name not found" (NXDOMAIN) error. Public DNS fallback is part of the &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/11/route-53-offers-advanced-hosted-zones/"&gt;Advanced Hosted Zones&lt;/a&gt; offering.&lt;/p&gt;
&lt;p&gt;Until now, Route 53 treated an associated private hosted zone as fully authoritative for its domain, so queries for names that weren't in the zone returned NXDOMAIN. To resolve a few names privately, customers also had to copy every other record from their public zone into the private hosted zone and keep the two in sync. With public DNS fallback, you add only the names you need privately, and every other name resolves from your existing public DNS. For example, your private hosted zone for example.com points example.com to a private endpoint, while partner.example.com exists only in public DNS. Before, a lookup for partner.example.com returned NXDOMAIN. Now it resolves from public DNS.&lt;/p&gt;
&lt;p&gt;To get started, create a private Advanced Hosted Zone or upgrade an existing private hosted zone, and then turn on public DNS fallback. You can use the Route 53 console, API, AWS CLI, AWS SDKs, or AWS CloudFormation.&lt;/p&gt;
&lt;p&gt;Public DNS fallback is available in all AWS commercial Regions where Route 53 private hosted zones are available. To learn more, see &lt;a href="https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/hosted-zone-private-public-dns-fallback.html" target="_blank"&gt;Enabling public DNS fallback for a private hosted zone&lt;/a&gt; in the Route 53 Developer Guide and the &lt;a href="https://aws.amazon.com/route53/pricing/"&gt;Route 53 pricing page&lt;/a&gt;.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/route-53-public-dns-fallback/</ore:originalUrl>
      <ore:upstreamId>0116834268e969d8c5c50d4be97996d887f88512</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:8de38b59fd0481ca95e356723f0ba071</id>
    <title>AWS Continuum for Penetration Testing now estimates task hours before you run a test</title>
    <updated>2026-11-20T08:00:00Z</updated>
    <published>2026-11-20T08:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/continuum-pentest-cost-estimates/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;AWS Continuum for Penetration Testing (formerly AWS Security Agent) now lets you estimate task hours before running a penetration test, so developers and security teams can see how many billable task hours a test is likely to need and choose a maximum task-hours limit with confidence. Continuum for Penetration Testing runs on-demand, AI-driven penetration tests against your web applications and APIs. Previously, the only way to know how long a test would take was to run it, making it difficult to plan budgets and set appropriate usage limits.&lt;/p&gt;
&lt;p&gt;With task-hour estimates, you open a penetration test, choose the Pentest cost estimate tab, and request an estimate. AWS Continuum runs a short preliminary analysis of your application's scope. It then draws on expertise from past penetration tests to estimate the task hours needed and shows the task hours that most similar applications finish within, and the higher range a few applications require. Requesting an estimate is free, and the estimate is a guide, not a quote or a limit. Actual task hours can be higher or lower, and only the maximum task-hours limit caps usage.&lt;/p&gt;
&lt;p&gt;Task-hour estimates are available in all AWS Regions where AWS Continuum for Penetration Testing is available.&lt;/p&gt;
&lt;p&gt;To learn more, see the &lt;a href="https://docs.aws.amazon.com/securityagent/latest/userguide/perform-penetration-test.html#task-hour-estimate" target="_blank"&gt;documentation&lt;/a&gt;. To get started, visit the &lt;a href="https://aws.amazon.com/continuum/"&gt;AWS Continuum product page&lt;/a&gt;.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/continuum-pentest-cost-estimates/</ore:originalUrl>
      <ore:upstreamId>70d205dc426570b8676e5efb7a68cdd397f14376</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:89c9e69cdfd60a7ebf7d1cd8ad0d0b4d</id>
    <title>Amazon Transcribe now available in AWS European Sovereign Cloud</title>
    <updated>2026-11-20T08:00:00Z</updated>
    <published>2026-11-20T08:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/amazon-transcribe-germany/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;Amazon Transcribe is now available in the AWS European Sovereign Cloud (Germany) Region. Customers who need to keep data and operations within the EU for regulatory compliance and data sovereignty requirements can now use automatic speech recognition (ASR) in the Region to turn speech into text.&lt;/p&gt; 
&lt;p&gt;Amazon Transcribe offers two ways to transcribe audio in this Region. Batch transcription processes media files stored in Amazon S3, and streaming transcription returns text in real time from live audio over HTTP/2 or WebSocket. Both support custom vocabularies, so you can improve recognition of domain-specific terms such as product names, industry jargon, and proper nouns.&lt;/p&gt; 
&lt;p&gt;To learn more, see &lt;a href="https://docs.aws.eu/transcribe/latest/dg/getting-started.html" target="_blank" rel="noopener noreferrer"&gt;Getting started with Amazon Transcribe&lt;/a&gt;, &lt;a href="https://docs.aws.eu/transcribe/latest/dg/supported-languages.html" target="_blank" rel="noopener noreferrer"&gt;Supported languages and language-specific features&lt;/a&gt;, and &lt;a href="https://www.aws.eu/european-sovereign-cloud/pricing/" target="_blank" rel="noopener noreferrer"&gt;AWS European Sovereign Cloud pricing&lt;/a&gt;.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/amazon-transcribe-germany/</ore:originalUrl>
      <ore:upstreamId>3107339583692a3a4d7f905133e424e8f898a87f</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:8201d29a37f9b233ffcf6f2aaa04f1b0</id>
    <title>AWS Lambda MicroVMs now supports customer managed keys in AWS KMS</title>
    <updated>2026-11-20T08:00:00Z</updated>
    <published>2026-11-20T08:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/lambda-microvms-customer-managed-keys/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;AWS Lambda MicroVMs now supports customer managed keys (CMK) in &lt;a href="https://aws.amazon.com/kms/"&gt;AWS Key Management Service&lt;/a&gt; (KMS) for data encryption at rest. CMK gives you full control over the lifecycle and usage of your KMS keys&lt;a href="https://aws.amazon.com/cloudtrail/"&gt;,&lt;/a&gt; helping meet compliance requirements in regulated industries like financial services and healthcare.&lt;/p&gt; 
&lt;p&gt;Lambda MicroVMs is a serverless compute primitive that provides VM-level isolation, near-instant launch and resume, and state preservation for executing user or AI generated code. Use MicroVMs to build applications like AI coding assistants, interactive development environments, and vulnerability scanners.&lt;/p&gt; 
&lt;p&gt;To get started, create a CMK in AWS KMS and configure its cryptographic properties, metadata, and &lt;a href="https://aws.amazon.com/iam/"&gt;AWS IAM&lt;/a&gt; access permissions.&amp;nbsp;Then, specify this CMK as a parameter when you create a MicroVM image or run a MicroVM. Lambda uses this CMK to encrypt your MicroVM image, MicroVM image environment variables, and the payload passed to the MicroVM run hook.&amp;nbsp; You can use CMK with Lambda MicroVMs&amp;nbsp;through the &lt;a href="https://console.aws.amazon.com/lambda/"&gt;AWS Lambda console&lt;/a&gt;, &lt;a href="https://aws.amazon.com/cloudformation/"&gt;AWS CloudFormation&lt;/a&gt;, &lt;a href="https://aws.amazon.com/cdk/"&gt;AWS Cloud Development Kit&lt;/a&gt;, or with your preferred Agentic development tools using the &lt;a href="https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/specialized-skills/serverless-skills/aws-lambda-microvms"&gt;Agent Toolkit for AWS&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;​​CMK support for MicroVMs is available in the following AWS Regions:&amp;nbsp;Asia Pacific (Hong Kong), Asia Pacific (Malaysia), Asia Pacific (Mumbai), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Thailand), Asia Pacific (Tokyo), Europe (Frankfurt), Europe (Ireland), Europe (Spain), Europe (Stockholm), South America (São Paulo),&amp;nbsp;US East (N. Virginia), US East (Ohio), and US West (Oregon). To learn more about Lambda MicroVMs, visit the &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/lambda-microvms-guide.html"&gt;AWS Lambda MicroVMs developer guide&lt;/a&gt;. For information on pricing for&amp;nbsp;CMK, see &lt;a href="https://aws.amazon.com/kms/pricing/"&gt;AWS KMS pricing&lt;/a&gt;.​&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/lambda-microvms-customer-managed-keys/</ore:originalUrl>
      <ore:upstreamId>ec011ece14c08c6fa72472ffd9e6249012958e69</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:746cc8cefb06cab24a4ca203f454cb7b</id>
    <title>AWS Agent Registry now supports WebBotAuth bot registration</title>
    <updated>2026-11-20T08:00:00Z</updated>
    <published>2026-11-20T08:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/agent-registry-webbotauth-support/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;AWS Agent Registry now supports registering &lt;a href="https://datatracker.ietf.org/wg/webbotauth/about/" target="_blank"&gt;WebBotAuth&lt;/a&gt; (WBA) bots as a new record type, making it easier to verify legitimate bot traffic through a standardized protocol. Previously, organizations lacked a standardized way to distinguish verified bots from malicious traffic. Now, bots can prove domain ownership through WebBotAuth, and you can integrate this verification with &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/11/aws-waf-bot-control-onboarding/" target="_blank"&gt;AWS WAF Bot Control&lt;/a&gt; to write rules that combine verification status and bot identity.&lt;/p&gt;
&lt;p&gt;This new capability gives content providers and application developers fine-grained control over which bots can access your resources. You can enhance security and improve traffic management by distinguishing legitimate bots from malicious actors. For example, you can allow WBA verified search engine crawlers while blocking unverified traffic or create custom access policies based on both bot identity and verification status.&lt;/p&gt;
&lt;p&gt;This feature is available in all AWS Regions where AWS Agent Registry is available. To learn more, visit the &lt;a href="https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/registry.html" target="_blank"&gt;AWS Agent Registry documentation&lt;/a&gt; and the &lt;a href="https://docs.aws.amazon.com/waf/latest/developerguide/waf-bot-control.html" target="_blank"&gt;AWS WAF Bot Control documentation&lt;/a&gt;.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/agent-registry-webbotauth-support/</ore:originalUrl>
      <ore:upstreamId>0c6d5590ed875105cd726b4d073723fb9797b991</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:5ebd49cca2e10bc04f8c510e63ff4aa5</id>
    <title>AWS DevOps Agent adds community and partner tools repository</title>
    <updated>2026-11-20T08:00:00Z</updated>
    <published>2026-11-20T08:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/devops-agent-tools-repository/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;AWS DevOps Agent now gives you ways to share and leverage skills, MCP servers, connectors, and custom agents that enhance the capabilities of your AWS DevOps Agent instances.&lt;/p&gt;
&lt;p&gt;The &lt;a href="https://aws.github.io/tools-for-devops-agent/" target="_blank"&gt;AWS DevOps Agent Tools open source repository&lt;/a&gt; is a centralized, AWS-curated collection of tools that extend AWS DevOps Agent capabilities. Customers can import ready-to-use, quality-controlled tools directly into their DevOps Agent configurations to improve investigation quality and expand operational context. A growing community of AWS DevOps Agent users and partners, and AWS service and support teams, have contributed a growing collection of tools to the community, including several partner-managed connectors that simplify connecting AWS DevOps Agent to third party MCP servers. Partners providing connectors include: Bluebox, Bronto, Celonis, Clickhouse Observability, Coralogix, Cribl, Elastic, Halo, Honeycomb, LaunchDarkly, Neo4j, Sumo Logic, and Wiz.&lt;/p&gt;
&lt;p&gt;To get started, browse the skills and connector catalogs from within your AWS DevOps Agent instance, or add and share your own tools by creating a PR within the AWS DevOps Agent Tools repository.&lt;/p&gt;
&lt;p&gt;See all the latest AWS DevOps Agent features on the &lt;a href="https://docs.aws.amazon.com/devopsagent/latest/userguide/whats-new.html" target="_blank"&gt;release history&lt;/a&gt; page. For the list of AWS Regions where AWS DevOps Agent is available, see the &lt;a href="https://docs.aws.amazon.com/devopsagent/latest/userguide/about-aws-devops-agent-supported-regions.html" target="_blank"&gt;supported Regions table&lt;/a&gt;.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/devops-agent-tools-repository/</ore:originalUrl>
      <ore:upstreamId>dc032020825c153cb3dd6608e3bcc87db2dbcfd8</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:53a22510ee0311989e2d5fe9b276f16b</id>
    <title>AWS DevOps Agent adds new chat capabilities</title>
    <updated>2026-11-20T08:00:00Z</updated>
    <published>2026-11-20T08:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/devops-agent-new-chat-capabilities/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;AWS DevOps Agent now extends its chat capabilities across MCP clients like Kiro and Claude Code, as well as Slack and Microsoft Teams channels. With Model Context Protocol (MCP) support, AWS DevOps Agent can now take directed chat actions including support for GitHub, GitLab, Azure DevOps, ServiceNow, and PagerDuty MCP tools, giving developers and operations teams powerful workflow automation directly from their preferred chat interface.&lt;/p&gt;
&lt;p&gt;This launch also adds auto-creation of per-incident Slack code channels and bi-directional chat within Microsoft Teams. AWS DevOps Agent has access to a compute sandbox that it can use to execute scripts and access the network to work more efficiently, and users can now rename and archive chats across all supported platforms.&lt;/p&gt;
&lt;p&gt;See all the latest AWS DevOps Agent features on the &lt;a href="https://docs.aws.amazon.com/devopsagent/latest/userguide/whats-new.html" target="_blank"&gt;release history&lt;/a&gt; page. For the list of AWS Regions where AWS DevOps Agent is available, see the &lt;a href="https://docs.aws.amazon.com/devopsagent/latest/userguide/about-aws-devops-agent-supported-regions.html" target="_blank"&gt;supported Regions table&lt;/a&gt;.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/devops-agent-new-chat-capabilities/</ore:originalUrl>
      <ore:upstreamId>0e6e37dbe8df1574629dfb5ae9dfa5c2bb3299fd</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:3f988e3eba46727d02c417b7988b903f</id>
    <title>Second-generation AWS Outposts racks now supported in the AWS Asia Pacific (Osaka)</title>
    <updated>2026-11-20T08:00:00Z</updated>
    <published>2026-11-20T08:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/aws-outposts-racks-osaka/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;Second-generation AWS Outposts racks are now supported in the AWS Asia Pacific (Osaka) Region. Outposts racks extend AWS infrastructure, AWS services, APIs, and tools to virtually any on-premises data center or colocation space for a truly consistent hybrid experience.&lt;/p&gt; 
&lt;p&gt;Organizations of every size, from startups to enterprises to public sector agencies, can now order Outposts racks connected to this newly supported Region to optimize for latency and data residency needs. This regional expansion provides additional flexibility in the number of AWS Regions that customers' Outposts can connect to.&lt;/p&gt; 
&lt;p&gt;To learn more about second-generation Outposts racks, read the &lt;a href="https://aws.amazon.com/blogs/aws/announcing-second-generation-aws-outposts-racks-with-breakthrough-performance-and-scalability-on-premises/" target="_blank" rel="noopener noreferrer"&gt;AWS Outposts blog post&lt;/a&gt; and &lt;a href="https://docs.aws.amazon.com/outposts/latest/network-userguide/what-is-outposts.html" target="_blank" rel="noopener noreferrer"&gt;user guide&lt;/a&gt;. For the latest list of countries and territories and the AWS Regions where second-generation Outposts racks are supported, see the &lt;a href="https://aws.amazon.com/outposts/rack/faqs/"&gt;AWS Outposts FAQs page&lt;/a&gt;.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/aws-outposts-racks-osaka/</ore:originalUrl>
      <ore:upstreamId>233e03a45947d6106fd31ef811d8e9247f776d44</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:32d9aaaee7df6c5dd7dcb59eb3a34b21</id>
    <title>Amazon VPC Lattice now supports CloudWatch metrics for VPC resources</title>
    <updated>2026-11-20T08:00:00Z</updated>
    <published>2026-11-20T08:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/vpc-lattice-cloudwatch-metrics/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;Amazon VPC Lattice now publishes Amazon CloudWatch metrics for VPC resources. Resource owners — those who share resources via VPC Lattice — and resource consumers — those who access those shared resources — can now see TCP traffic to resources such as databases, clusters, and on-premises endpoints. Resource owners get metrics for resource gateways and resource configurations. Consumers get metrics for resource endpoints, service network endpoints, and service network VPC associations. Previously, resource access logs were the primary way to see this traffic, but they required additional processing and provided limited real-time visibility. Now you can monitor your layer-4 resources directly in CloudWatch.&lt;/p&gt; 
&lt;p&gt;With these metrics, you can proactively catch connectivity issues and optimize resource capacity. Capacity planning metrics — including bytes processed, new flows, and active flows — let resource owners monitor traffic per resource gateway and per resource configuration to track load on shared resources. Reliability metrics, such as dropped packets, help you detect problems early. Resource gateways also report port allocation errors, which show when a resource gateway needs more IPv4 addresses per network interface. Consumers can monitor traffic per resource endpoint, service network endpoint, or service network VPC association. They can set CloudWatch alarms for when new flows drop to zero or dropped packets increase, catching an unreachable resource before their applications do. Both owners and consumers can break metrics down by Availability Zone to isolate zonal issues or verify connections after configuration changes.&lt;/p&gt; 
&lt;p&gt;CloudWatch metrics for VPC resources are available in all AWS Regions where Amazon VPC Lattice is available. For the list of Regions, see the &lt;a href="https://docs.aws.amazon.com/vpc-lattice/latest/ug/what-is-vpc-lattice.html" target="_blank" rel="noopener noreferrer"&gt;Amazon VPC Lattice FAQs&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;To learn more, see &lt;a href="https://docs.aws.amazon.com/vpc-lattice/latest/ug/monitoring-cloudwatch.html" target="_blank" rel="noopener noreferrer"&gt;CloudWatch metrics for Amazon VPC Lattice&lt;/a&gt; in the Amazon VPC Lattice User Guide, or visit the &lt;a href="https://docs.aws.amazon.com/vpc-lattice/" target="_blank" rel="noopener noreferrer"&gt;Amazon VPC Lattice product page&lt;/a&gt;.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/vpc-lattice-cloudwatch-metrics/</ore:originalUrl>
      <ore:upstreamId>cb034df9a902d85a21e42253d5f1c32b42c217cc</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:1a922f07a50ff8eed0d2b185e809ea34</id>
    <title>Amazon Textract Insights is now generally available</title>
    <updated>2026-11-20T08:00:00Z</updated>
    <published>2026-11-20T08:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/textract-insights-ga/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;Amazon Textract Insights brings document understanding to Amazon Textract. It is a new generative AI feature of Amazon Textract, and is now generally available in the US East (N. Virginia) and US West (Oregon) AWS Regions. Amazon Textract Insights splits, classifies, and extracts structured data from documents in a single asynchronous request. Documents like insurance claims, tax packets, and onboarding packages often arrive as one long scan that holds many documents in no fixed order. Processing them has meant assembling and operating separate steps for text detection, splitting, classification, and extraction. Amazon Textract Insights handles that work in one managed request, with no AI models to train.&lt;/p&gt;
&lt;p&gt;How it works: You define the fields you need in a blueprint, a JSON schema that describes each field in natural language, or you can start from a library of AWS public blueprints for common document types such as W-2s, invoices, and bank statements. Amazon Textract Insights can split each file into separate sub-documents, classify each one by matching it to the best-fitting blueprint, and extract your fields. It returns a confidence score for every value and grounds each one to its location on the page, so you can automate high-confidence results and route the rest to human review. It can also return Markdown, HTML, and plain text for retrieval-augmented generation (RAG) applications, generate document summaries and figure captions, and detect and redact personally identifiable information. Amazon Textract Insights reads documents from and writes results to your own Amazon S3 buckets.&lt;/p&gt;
&lt;p&gt;You can use Amazon Textract Insights through the AWS SDKs and the AWS CLI. To learn more, see the &lt;a href="https://aws.amazon.com/textract/"&gt;Amazon Textract product page&lt;/a&gt; and the Amazon Textract Insights section of the &lt;a href="https://docs.aws.amazon.com/textract/latest/dg/what-is.html" target="_blank"&gt;Amazon Textract Developer Guide&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Regional Availability: US East (N. Virginia), US West (Oregon)&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/textract-insights-ga/</ore:originalUrl>
      <ore:upstreamId>94e47fb4d51042f6366bd6fcdb4981d23fa02d67</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:071f7ee6fc2459c4733b4b9366e6cd26</id>
    <title>AWS Backup now supports incremental backups for Amazon DynamoDB</title>
    <updated>2026-11-20T08:00:00Z</updated>
    <published>2026-11-20T08:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/aws-backup-incremental-backups-dynamodb/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;AWS Backup now supports incremental backups of Amazon DynamoDB tables, enabling you to reduce backup storage while maintaining backup schedules as frequent as one hour.&lt;/p&gt; 
&lt;p&gt;Until now, AWS Backup created a full copy of your DynamoDB tables. With this launch, after an initial full backup, each incremental backup now captures only the data that changed, and AWS Backup takes a new full backup every 15 days. This lets you store less data and back up more often. You can restore from any recovery point in the chain, and you can schedule incremental backups anywhere from hourly to weekly frequencies. You can store incremental backups in both AWS Backup vaults and logically air-gapped vaults. Cross-Region backup copies are also incremental, further increasing your savings.&lt;/p&gt; 
&lt;p&gt;AWS Backup turns on incremental backups automatically for new customers who protect DynamoDB. If you already back up DynamoDB with AWS Backup, you can turn on incremental backups under advanced features in AWS Backup settings, which lets you manage your backup preferences at the account and region level. You can create and manage incremental backups from the AWS Backup console, the AWS CLI, or the API.&lt;/p&gt; 
&lt;p&gt;Incremental backups for DynamoDB are available in all AWS Regions where AWS Backup protects DynamoDB. To learn more, see &lt;a href="https://docs.aws.amazon.com/aws-backup/latest/devguide/working-with-supported-services.html#working-with-ddb" target="_blank" rel="noopener noreferrer"&gt;working with supported services&lt;/a&gt; in the AWS Backup Developer Guide, read the &lt;a href="https://aws.amazon.com/blogs/storage/reduce-amazon-dynamodb-backup-storage-costs-with-incremental-backups-in-aws-backup/" target="_blank" rel="noopener noreferrer"&gt;launch blog&lt;/a&gt;, and visit the &lt;a href="https://aws.amazon.com/backup/" target="_blank" rel="noopener noreferrer"&gt;AWS Backup product page&lt;/a&gt;. To get started, open the AWS Backup console.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/aws-backup-incremental-backups-dynamodb/</ore:originalUrl>
      <ore:upstreamId>948777bb3e6e5d40d12166c8e8211ab2936ed74f</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:github-trending:e475a0249087d58fb536da65b2b58678</id>
    <title>google-labs-code/stitch-skills</title>
    <updated>2026-11-20T07:58:14Z</updated>
    <published>2026-11-20T07:58:14Z</published>
    <link rel="alternate" href="https://github.com/google-labs-code/stitch-skills" />
    <link rel="via" href="https://mshibanami.github.io/GitHubTrendingRSS/daily/all.xml" />
    <category scheme="urn:ore-news:sources" term="github-trending" label="GitHub Trending RSS" />
    <author>
      <name>GitHub Trending RSS</name>
    </author>
    <source>
      <id>urn:ore-news:source:github-trending</id>
      <title>GitHub Trending RSS</title>
      <link rel="alternate" href="https://github.com/mshibanami/GitHubTrendingRSS" />
      <link rel="via" href="https://mshibanami.github.io/GitHubTrendingRSS/daily/all.xml" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>github-trending</ore:sourceId>
      <ore:sourceName>GitHub Trending RSS</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://github.com/mshibanami/GitHubTrendingRSS</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://mshibanami.github.io/GitHubTrendingRSS/daily/all.xml</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://github.com/google-labs-code/stitch-skills</ore:originalUrl>
      <ore:upstreamId>https://github.com/google-labs-code/stitch-skills</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:github-trending:ddf5796941d50ec352daf645ed897a59</id>
    <title>HKUDS/CLI-Anything</title>
    <updated>2026-11-20T07:58:14Z</updated>
    <published>2026-11-20T07:58:14Z</published>
    <link rel="alternate" href="https://github.com/HKUDS/CLI-Anything" />
    <link rel="via" href="https://mshibanami.github.io/GitHubTrendingRSS/daily/all.xml" />
    <category scheme="urn:ore-news:sources" term="github-trending" label="GitHub Trending RSS" />
    <author>
      <name>GitHub Trending RSS</name>
    </author>
    <source>
      <id>urn:ore-news:source:github-trending</id>
      <title>GitHub Trending RSS</title>
      <link rel="alternate" href="https://github.com/mshibanami/GitHubTrendingRSS" />
      <link rel="via" href="https://mshibanami.github.io/GitHubTrendingRSS/daily/all.xml" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>github-trending</ore:sourceId>
      <ore:sourceName>GitHub Trending RSS</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://github.com/mshibanami/GitHubTrendingRSS</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://mshibanami.github.io/GitHubTrendingRSS/daily/all.xml</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://github.com/HKUDS/CLI-Anything</ore:originalUrl>
      <ore:upstreamId>https://github.com/HKUDS/CLI-Anything</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:github-trending:dadcf337b6b1ee75681f4d895f0766c7</id>
    <title>obra/superpowers</title>
    <updated>2026-11-20T07:58:14Z</updated>
    <published>2026-11-20T07:58:14Z</published>
    <link rel="alternate" href="https://github.com/obra/superpowers" />
    <link rel="via" href="https://mshibanami.github.io/GitHubTrendingRSS/daily/all.xml" />
    <category scheme="urn:ore-news:sources" term="github-trending" label="GitHub Trending RSS" />
    <author>
      <name>GitHub Trending RSS</name>
    </author>
    <source>
      <id>urn:ore-news:source:github-trending</id>
      <title>GitHub Trending RSS</title>
      <link rel="alternate" href="https://github.com/mshibanami/GitHubTrendingRSS" />
      <link rel="via" href="https://mshibanami.github.io/GitHubTrendingRSS/daily/all.xml" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>github-trending</ore:sourceId>
      <ore:sourceName>GitHub Trending RSS</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://github.com/mshibanami/GitHubTrendingRSS</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://mshibanami.github.io/GitHubTrendingRSS/daily/all.xml</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://github.com/obra/superpowers</ore:originalUrl>
      <ore:upstreamId>https://github.com/obra/superpowers</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:github-trending:cd5e6df7a2166f30933f9b840ab4c537</id>
    <title>cathrynlavery/diagram-design</title>
    <updated>2026-11-20T07:58:14Z</updated>
    <published>2026-11-20T07:58:14Z</published>
    <link rel="alternate" href="https://github.com/cathrynlavery/diagram-design" />
    <link rel="via" href="https://mshibanami.github.io/GitHubTrendingRSS/daily/all.xml" />
    <category scheme="urn:ore-news:sources" term="github-trending" label="GitHub Trending RSS" />
    <author>
      <name>GitHub Trending RSS</name>
    </author>
    <source>
      <id>urn:ore-news:source:github-trending</id>
      <title>GitHub Trending RSS</title>
      <link rel="alternate" href="https://github.com/mshibanami/GitHubTrendingRSS" />
      <link rel="via" href="https://mshibanami.github.io/GitHubTrendingRSS/daily/all.xml" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>github-trending</ore:sourceId>
      <ore:sourceName>GitHub Trending RSS</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://github.com/mshibanami/GitHubTrendingRSS</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://mshibanami.github.io/GitHubTrendingRSS/daily/all.xml</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://github.com/cathrynlavery/diagram-design</ore:originalUrl>
      <ore:upstreamId>https://github.com/cathrynlavery/diagram-design</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:github-trending:ae548868a8e13fba964c7d792bc9ea44</id>
    <title>elementalsouls/Claude-BugHunter</title>
    <updated>2026-11-20T07:58:14Z</updated>
    <published>2026-11-20T07:58:14Z</published>
    <link rel="alternate" href="https://github.com/elementalsouls/Claude-BugHunter" />
    <link rel="via" href="https://mshibanami.github.io/GitHubTrendingRSS/daily/all.xml" />
    <category scheme="urn:ore-news:sources" term="github-trending" label="GitHub Trending RSS" />
    <author>
      <name>GitHub Trending RSS</name>
    </author>
    <source>
      <id>urn:ore-news:source:github-trending</id>
      <title>GitHub Trending RSS</title>
      <link rel="alternate" href="https://github.com/mshibanami/GitHubTrendingRSS" />
      <link rel="via" href="https://mshibanami.github.io/GitHubTrendingRSS/daily/all.xml" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>github-trending</ore:sourceId>
      <ore:sourceName>GitHub Trending RSS</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://github.com/mshibanami/GitHubTrendingRSS</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://mshibanami.github.io/GitHubTrendingRSS/daily/all.xml</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://github.com/elementalsouls/Claude-BugHunter</ore:originalUrl>
      <ore:upstreamId>https://github.com/elementalsouls/Claude-BugHunter</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:github-trending:a8a9f00ba850dd931c676d9d73481791</id>
    <title>Tracer-Cloud/opensre</title>
    <updated>2026-11-20T07:58:14Z</updated>
    <published>2026-11-20T07:58:14Z</published>
    <link rel="alternate" href="https://github.com/Tracer-Cloud/opensre" />
    <link rel="via" href="https://mshibanami.github.io/GitHubTrendingRSS/daily/all.xml" />
    <category scheme="urn:ore-news:sources" term="github-trending" label="GitHub Trending RSS" />
    <author>
      <name>GitHub Trending RSS</name>
    </author>
    <source>
      <id>urn:ore-news:source:github-trending</id>
      <title>GitHub Trending RSS</title>
      <link rel="alternate" href="https://github.com/mshibanami/GitHubTrendingRSS" />
      <link rel="via" href="https://mshibanami.github.io/GitHubTrendingRSS/daily/all.xml" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>github-trending</ore:sourceId>
      <ore:sourceName>GitHub Trending RSS</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://github.com/mshibanami/GitHubTrendingRSS</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://mshibanami.github.io/GitHubTrendingRSS/daily/all.xml</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://github.com/Tracer-Cloud/opensre</ore:originalUrl>
      <ore:upstreamId>https://github.com/Tracer-Cloud/opensre</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:github-trending:9e81054088fe4ccdf678deb4ae9de11a</id>
    <title>openvinotoolkit/openvino</title>
    <updated>2026-11-20T07:58:14Z</updated>
    <published>2026-11-20T07:58:14Z</published>
    <link rel="alternate" href="https://github.com/openvinotoolkit/openvino" />
    <link rel="via" href="https://mshibanami.github.io/GitHubTrendingRSS/daily/all.xml" />
    <category scheme="urn:ore-news:sources" term="github-trending" label="GitHub Trending RSS" />
    <author>
      <name>GitHub Trending RSS</name>
    </author>
    <source>
      <id>urn:ore-news:source:github-trending</id>
      <title>GitHub Trending RSS</title>
      <link rel="alternate" href="https://github.com/mshibanami/GitHubTrendingRSS" />
      <link rel="via" href="https://mshibanami.github.io/GitHubTrendingRSS/daily/all.xml" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>github-trending</ore:sourceId>
      <ore:sourceName>GitHub Trending RSS</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://github.com/mshibanami/GitHubTrendingRSS</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://mshibanami.github.io/GitHubTrendingRSS/daily/all.xml</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://github.com/openvinotoolkit/openvino</ore:originalUrl>
      <ore:upstreamId>https://github.com/openvinotoolkit/openvino</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:github-trending:85515d3b15cdf22c0ae8ad71fb2383bd</id>
    <title>zhouxiaoka/autoclip</title>
    <updated>2026-11-20T07:58:14Z</updated>
    <published>2026-11-20T07:58:14Z</published>
    <link rel="alternate" href="https://github.com/zhouxiaoka/autoclip" />
    <link rel="via" href="https://mshibanami.github.io/GitHubTrendingRSS/daily/all.xml" />
    <category scheme="urn:ore-news:sources" term="github-trending" label="GitHub Trending RSS" />
    <author>
      <name>GitHub Trending RSS</name>
    </author>
    <source>
      <id>urn:ore-news:source:github-trending</id>
      <title>GitHub Trending RSS</title>
      <link rel="alternate" href="https://github.com/mshibanami/GitHubTrendingRSS" />
      <link rel="via" href="https://mshibanami.github.io/GitHubTrendingRSS/daily/all.xml" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>github-trending</ore:sourceId>
      <ore:sourceName>GitHub Trending RSS</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://github.com/mshibanami/GitHubTrendingRSS</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://mshibanami.github.io/GitHubTrendingRSS/daily/all.xml</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://github.com/zhouxiaoka/autoclip</ore:originalUrl>
      <ore:upstreamId>https://github.com/zhouxiaoka/autoclip</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:github-trending:7b80a4702e8e60e36cf3b6db1034c5b8</id>
    <title>XiaoYouChR/Ghost-Downloader-3</title>
    <updated>2026-11-20T07:58:14Z</updated>
    <published>2026-11-20T07:58:14Z</published>
    <link rel="alternate" href="https://github.com/XiaoYouChR/Ghost-Downloader-3" />
    <link rel="via" href="https://mshibanami.github.io/GitHubTrendingRSS/daily/all.xml" />
    <category scheme="urn:ore-news:sources" term="github-trending" label="GitHub Trending RSS" />
    <author>
      <name>GitHub Trending RSS</name>
    </author>
    <source>
      <id>urn:ore-news:source:github-trending</id>
      <title>GitHub Trending RSS</title>
      <link rel="alternate" href="https://github.com/mshibanami/GitHubTrendingRSS" />
      <link rel="via" href="https://mshibanami.github.io/GitHubTrendingRSS/daily/all.xml" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>github-trending</ore:sourceId>
      <ore:sourceName>GitHub Trending RSS</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://github.com/mshibanami/GitHubTrendingRSS</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://mshibanami.github.io/GitHubTrendingRSS/daily/all.xml</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://github.com/XiaoYouChR/Ghost-Downloader-3</ore:originalUrl>
      <ore:upstreamId>https://github.com/XiaoYouChR/Ghost-Downloader-3</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:github-trending:6cd7a655e08af3dd03268f9a46b73836</id>
    <title>mvanhorn/last30days-skill</title>
    <updated>2026-11-20T07:58:14Z</updated>
    <published>2026-11-20T07:58:14Z</published>
    <link rel="alternate" href="https://github.com/mvanhorn/last30days-skill" />
    <link rel="via" href="https://mshibanami.github.io/GitHubTrendingRSS/daily/all.xml" />
    <category scheme="urn:ore-news:sources" term="github-trending" label="GitHub Trending RSS" />
    <author>
      <name>GitHub Trending RSS</name>
    </author>
    <source>
      <id>urn:ore-news:source:github-trending</id>
      <title>GitHub Trending RSS</title>
      <link rel="alternate" href="https://github.com/mshibanami/GitHubTrendingRSS" />
      <link rel="via" href="https://mshibanami.github.io/GitHubTrendingRSS/daily/all.xml" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>github-trending</ore:sourceId>
      <ore:sourceName>GitHub Trending RSS</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://github.com/mshibanami/GitHubTrendingRSS</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://mshibanami.github.io/GitHubTrendingRSS/daily/all.xml</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://github.com/mvanhorn/last30days-skill</ore:originalUrl>
      <ore:upstreamId>https://github.com/mvanhorn/last30days-skill</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:github-trending:6194213fd4087c8026a15936f1318e31</id>
    <title>toeverything/AFFiNE</title>
    <updated>2026-11-20T07:58:14Z</updated>
    <published>2026-11-20T07:58:14Z</published>
    <link rel="alternate" href="https://github.com/toeverything/AFFiNE" />
    <link rel="via" href="https://mshibanami.github.io/GitHubTrendingRSS/daily/all.xml" />
    <category scheme="urn:ore-news:sources" term="github-trending" label="GitHub Trending RSS" />
    <author>
      <name>GitHub Trending RSS</name>
    </author>
    <source>
      <id>urn:ore-news:source:github-trending</id>
      <title>GitHub Trending RSS</title>
      <link rel="alternate" href="https://github.com/mshibanami/GitHubTrendingRSS" />
      <link rel="via" href="https://mshibanami.github.io/GitHubTrendingRSS/daily/all.xml" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>github-trending</ore:sourceId>
      <ore:sourceName>GitHub Trending RSS</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://github.com/mshibanami/GitHubTrendingRSS</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://mshibanami.github.io/GitHubTrendingRSS/daily/all.xml</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://github.com/toeverything/AFFiNE</ore:originalUrl>
      <ore:upstreamId>https://github.com/toeverything/AFFiNE</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:github-trending:60bd560301f77661728f12151111c82e</id>
    <title>mjmirza/app-store-compliance</title>
    <updated>2026-11-20T07:58:14Z</updated>
    <published>2026-11-20T07:58:14Z</published>
    <link rel="alternate" href="https://github.com/mjmirza/app-store-compliance" />
    <link rel="via" href="https://mshibanami.github.io/GitHubTrendingRSS/daily/all.xml" />
    <category scheme="urn:ore-news:sources" term="github-trending" label="GitHub Trending RSS" />
    <author>
      <name>GitHub Trending RSS</name>
    </author>
    <source>
      <id>urn:ore-news:source:github-trending</id>
      <title>GitHub Trending RSS</title>
      <link rel="alternate" href="https://github.com/mshibanami/GitHubTrendingRSS" />
      <link rel="via" href="https://mshibanami.github.io/GitHubTrendingRSS/daily/all.xml" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>github-trending</ore:sourceId>
      <ore:sourceName>GitHub Trending RSS</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://github.com/mshibanami/GitHubTrendingRSS</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://mshibanami.github.io/GitHubTrendingRSS/daily/all.xml</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://github.com/mjmirza/app-store-compliance</ore:originalUrl>
      <ore:upstreamId>https://github.com/mjmirza/app-store-compliance</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:github-trending:5d31f8addd9dac6cb0b8996d5d90ff0e</id>
    <title>cursor/plugins</title>
    <updated>2026-11-20T07:58:14Z</updated>
    <published>2026-11-20T07:58:14Z</published>
    <link rel="alternate" href="https://github.com/cursor/plugins" />
    <link rel="via" href="https://mshibanami.github.io/GitHubTrendingRSS/daily/all.xml" />
    <category scheme="urn:ore-news:sources" term="github-trending" label="GitHub Trending RSS" />
    <author>
      <name>GitHub Trending RSS</name>
    </author>
    <source>
      <id>urn:ore-news:source:github-trending</id>
      <title>GitHub Trending RSS</title>
      <link rel="alternate" href="https://github.com/mshibanami/GitHubTrendingRSS" />
      <link rel="via" href="https://mshibanami.github.io/GitHubTrendingRSS/daily/all.xml" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>github-trending</ore:sourceId>
      <ore:sourceName>GitHub Trending RSS</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://github.com/mshibanami/GitHubTrendingRSS</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://mshibanami.github.io/GitHubTrendingRSS/daily/all.xml</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://github.com/cursor/plugins</ore:originalUrl>
      <ore:upstreamId>https://github.com/cursor/plugins</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:github-trending:3b6a0c5e229585a26bc16c3b4739351b</id>
    <title>firecrawl/firecrawl</title>
    <updated>2026-11-20T07:58:14Z</updated>
    <published>2026-11-20T07:58:14Z</published>
    <link rel="alternate" href="https://github.com/firecrawl/firecrawl" />
    <link rel="via" href="https://mshibanami.github.io/GitHubTrendingRSS/daily/all.xml" />
    <category scheme="urn:ore-news:sources" term="github-trending" label="GitHub Trending RSS" />
    <author>
      <name>GitHub Trending RSS</name>
    </author>
    <source>
      <id>urn:ore-news:source:github-trending</id>
      <title>GitHub Trending RSS</title>
      <link rel="alternate" href="https://github.com/mshibanami/GitHubTrendingRSS" />
      <link rel="via" href="https://mshibanami.github.io/GitHubTrendingRSS/daily/all.xml" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>github-trending</ore:sourceId>
      <ore:sourceName>GitHub Trending RSS</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://github.com/mshibanami/GitHubTrendingRSS</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://mshibanami.github.io/GitHubTrendingRSS/daily/all.xml</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://github.com/firecrawl/firecrawl</ore:originalUrl>
      <ore:upstreamId>https://github.com/firecrawl/firecrawl</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:github-trending:3b54ffa88af3b713a97eaeb234f3ebdd</id>
    <title>nginx/nginx</title>
    <updated>2026-11-20T07:58:14Z</updated>
    <published>2026-11-20T07:58:14Z</published>
    <link rel="alternate" href="https://github.com/nginx/nginx" />
    <link rel="via" href="https://mshibanami.github.io/GitHubTrendingRSS/daily/all.xml" />
    <category scheme="urn:ore-news:sources" term="github-trending" label="GitHub Trending RSS" />
    <author>
      <name>GitHub Trending RSS</name>
    </author>
    <source>
      <id>urn:ore-news:source:github-trending</id>
      <title>GitHub Trending RSS</title>
      <link rel="alternate" href="https://github.com/mshibanami/GitHubTrendingRSS" />
      <link rel="via" href="https://mshibanami.github.io/GitHubTrendingRSS/daily/all.xml" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>github-trending</ore:sourceId>
      <ore:sourceName>GitHub Trending RSS</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://github.com/mshibanami/GitHubTrendingRSS</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://mshibanami.github.io/GitHubTrendingRSS/daily/all.xml</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://github.com/nginx/nginx</ore:originalUrl>
      <ore:upstreamId>https://github.com/nginx/nginx</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:github-trending:2b6b445bfbfc87bc8a895dbc7844caa1</id>
    <title>jingyaogong/minimind</title>
    <updated>2026-11-20T07:58:14Z</updated>
    <published>2026-11-20T07:58:14Z</published>
    <link rel="alternate" href="https://github.com/jingyaogong/minimind" />
    <link rel="via" href="https://mshibanami.github.io/GitHubTrendingRSS/daily/all.xml" />
    <category scheme="urn:ore-news:sources" term="github-trending" label="GitHub Trending RSS" />
    <author>
      <name>GitHub Trending RSS</name>
    </author>
    <source>
      <id>urn:ore-news:source:github-trending</id>
      <title>GitHub Trending RSS</title>
      <link rel="alternate" href="https://github.com/mshibanami/GitHubTrendingRSS" />
      <link rel="via" href="https://mshibanami.github.io/GitHubTrendingRSS/daily/all.xml" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>github-trending</ore:sourceId>
      <ore:sourceName>GitHub Trending RSS</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://github.com/mshibanami/GitHubTrendingRSS</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://mshibanami.github.io/GitHubTrendingRSS/daily/all.xml</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://github.com/jingyaogong/minimind</ore:originalUrl>
      <ore:upstreamId>https://github.com/jingyaogong/minimind</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hermes-agent-releases:332d2f61aadedb12423b0549d02e25ec</id>
    <title>Hermes Agent canary v0.23.3+canary.20261120T064609Z</title>
    <updated>2026-11-20T07:49:17Z</updated>
    <published>2026-11-20T07:49:17Z</published>
    <link rel="alternate" href="https://github.com/NousResearch/hermes-agent/releases/tag/v0.23.3%2Bcanary.20261120T064609Z" />
    <link rel="via" href="https://api.github.com/repos/NousResearch/hermes-agent/releases" />
    <category scheme="urn:ore-news:sources" term="hermes-agent-releases" label="Hermes Agent GitHub Releases" />
    <author>
      <name>Hermes Agent GitHub Releases</name>
    </author>
    <source>
      <id>urn:ore-news:source:hermes-agent-releases</id>
      <title>Hermes Agent GitHub Releases</title>
      <link rel="alternate" href="https://github.com/NousResearch/hermes-agent/releases" />
      <link rel="via" href="https://api.github.com/repos/NousResearch/hermes-agent/releases" />
    </source>
    <content type="text"># Hermes Agent v0.23.3+canary.20261120T064609Z (v0.23.3+canary.20261120T064609Z)

**Release Date:** November 20, 2026

&lt;!-- HERMES_BUILDS_TABLE --&gt;
## Downloads

### Hermes Desktop

| OS | Architecture | Download |
|---|---|---|
| macOS | Apple Silicon (M-series) | [DMG](https://hermes-assets.nousresearch.com/releases/tag/v0.23.3%2Bcanary.20261120T064609Z/HermesBundled-0.23.3%2Bcanary.20261120T064609Z-mac-arm64.dmg) |
| Windows | x86 (64-bit) | [MSIX](https://hermes-assets.nousresearch.com/releases/tag/v0.23.3%2Bcanary.20261120T064609Z/HermesBundled-0.23.3%2Bcanary.20261120T064609Z-win-x64.msix) |
| Windows | ARM (arm64 / aarch64) | [MSIX](https://hermes-assets.nousresearch.com/releases/tag/v0.23.3%2Bcanary.20261120T064609Z/HermesBundled-0.23.3%2Bcanary.20261120T064609Z-win-arm64.msix) |

### Native install/chat smoke

Download availability is independent of smoke status. Each result covers all native legs in that format group. Linux AppImages and unsigned Store envelopes are not install-smoked. No-upload dry tags have no download handoff and are not smoke-qualified.

| Packages | Smoke status |
|---|---|
| macOS DMG + ZIP (arm64) | Passed |
| Windows MSIX (arm64) | Passed |
| Windows MSIX (x64) | Passed |
&lt;!-- /HERMES_BUILDS_TABLE --&gt;

## ✨ Features

- Plugin-catalog): add memrack (memory rack provider) - v0.11.1 ([`94688a1e`](https://github.com/NousResearch/hermes-agent/commit/94688a1e775dbaacedeed875783d055e8c849620)) — @Kesuek
- Plugin-catalog): add swarm-studio plugin ([`c66486b2`](https://github.com/NousResearch/hermes-agent/commit/c66486b2d3c45857f7b65c6a5b279934ec1cf72d)) — @Pukujan
- Catalog): add deapi ([`61271811`](https://github.com/NousResearch/hermes-agent/commit/612718111dbfaa414337026d5a6f888f8163a99b)) — @dawidope
- OneHaus to the plugin catalog ([`a8603f0c`](https://github.com/NousResearch/hermes-agent/commit/a8603f0c3b3cc7438da582280c1544467ddd0ca8)) — @Im5tu
- Plugin-catalog: add hermes-lectern 0.5.0 ([`b6dc9576`](https://github.com/NousResearch/hermes-agent/commit/b6dc95767199a1cbb46a27ad4defa60123359e75)) — @Fiction000
- Plugin-catalog): add composer-predictions desktop plugin ([`62d8501b`](https://github.com/NousResearch/hermes-agent/commit/62d8501b95a1535cd825984210a082440a678aef)) — @xuhuawork
- Plugin-catalog): add hermes-atlas-evolution plugin ([`0f1f0c67`](https://github.com/NousResearch/hermes-agent/commit/0f1f0c6759c6316509a581e24f53208c0921be20)) — @sesantanajr
- Catalog: add hermes-officecraft ([`bb205c1f`](https://github.com/NousResearch/hermes-agent/commit/bb205c1f1b0bc23818289de349b9b3eaa18f0381)) — @KosmGit
- Plugin-catalog): add hermes-program-status ([`45b7feb5`](https://github.com/NousResearch/hermes-agent/commit/45b7feb5f91578b43da6f72a483263a2180ed006)) — @sicruse
- Hermes Personal Task Manager 1.0.0 to plugin catalog ([`f3f5f676`](https://github.com/NousResearch/hermes-agent/commit/f3f5f676f2e822f1de3eab4a41a244905490094d)) — @RudiFreeman
- Plugin-catalog): add labelqueue plugin ([`5c255555`](https://github.com/NousResearch/hermes-agent/commit/5c255555b7d42b9b0b4fd006b736fa0cef1bc711)) — @AbigailDavised
- Plugin-catalog): add blindboxshop plugin ([`e2874c9e`](https://github.com/NousResearch/hermes-agent/commit/e2874c9eb8ac6d5e218e6a8b6e5bb0f308331e72)) — @AbigailDavised
- Catalog): add optiq-cloud-provider ([`7f224710`](https://github.com/NousResearch/hermes-agent/commit/7f224710261589663bf17a1e12518e54e2ea9da2)) — @optiq-bot
- Plugin-catalog: add merageo (meraGEO AI Visibility) ([`c0dd733d`](https://github.com/NousResearch/hermes-agent/commit/c0dd733d38287b3a14bfba3943b413252ba23872)) — @Sandeep85Das
- Plugin-catalog: add twitchboard ([`013fb28b`](https://github.com/NousResearch/hermes-agent/commit/013fb28bf739d33f40c435d334a3559950e457a7)) — @hlplanet
- Plugin-catalog): update whiteboard to 0.1.10 ([`9687ea50`](https://github.com/NousResearch/hermes-agent/commit/9687ea505e3edbaec764d5f40caa07e502778efc)) — @Adolanium
- Plugin-catalog): kanzo-board 0.1.2 (re-pin to ec708e8) ([`9732f084`](https://github.com/NousResearch/hermes-agent/commit/9732f08470e378c421658d709947ff5888e4472b)) — @0sahil
- Plugin-catalog): add kanzo-board plugin ([`7eb86e49`](https://github.com/NousResearch/hermes-agent/commit/7eb86e494ecb3ef1b8aea35f2d7db017320f02d8)) — @0sahil
- Plugin-catalog): add cobrain (shared Markdown memory, remote MCP) ([`f0e1c529`](https://github.com/NousResearch/hermes-agent/commit/f0e1c529078b4c179b91e08ef6b6343a0f436213)) — @alessandromoretti90
- Plugin-catalog entry for web-forage ([`ae2fc3df`](https://github.com/NousResearch/hermes-agent/commit/ae2fc3dfbbcd860067b326ae3e7c25e717a056f5)) — @aldemaroc
- Catalog: add iacg-desk + iacg-board (IaC Genius CE) ([`32410ab4`](https://github.com/NousResearch/hermes-agent/commit/32410ab4fbbaed6270b60e5af030bb9c555a82f9)) — @RajaRenga
- Plugin-catalog): rename flowcanvas to arachne-flow and pin 1.1.0 (b15bd0f4) ([`77458ec9`](https://github.com/NousResearch/hermes-agent/commit/77458ec9416367b7f776fc4bc35786f3686ab0fc)) — @EmotionalThrifty
- Plugin-catalog): add promptli-comms plugin ([`6ca80e15`](https://github.com/NousResearch/hermes-agent/commit/6ca80e1536202e2c64421d01659f89eebbeec7e0)) — @promptli-dev
- Catalog): add Gnani Prisma STT and Timbre TTS ([`fb69c331`](https://github.com/NousResearch/hermes-agent/commit/fb69c33197c1a4b0187e057b5cbfa07020934416)) — @ANAMASGARD
- Plugin-catalog: add cover banner image for global-business-culture ([`b6d8d734`](https://github.com/NousResearch/hermes-agent/commit/b6d8d734cf8c01f1bff5de1a17e60f7bcd0eb477)) — @pswong661-eng
- Plugin-catalog): update worktable plugin to 0.1.6 ([`8e7bc622`](https://github.com/NousResearch/hermes-agent/commit/8e7bc62266b35420e92034f4df8829111e0f66db)) — @obkaro
- Catalog: add Context Tracker ([`6748b53a`](https://github.com/NousResearch/hermes-agent/commit/6748b53a05c0c796470f0bdbb3c5596c1f0a55e6)) — @mu1ze
- Plugin-catalog): herm-t3s 0.1.2 ([`98837af3`](https://github.com/NousResearch/hermes-agent/commit/98837af3c68edc321a798ac22b7310e041f82e00)) — @seanflynnfilm
- Plugin-catalog): herm-t3s 0.1.1 (snooze hides) ([`80936550`](https://github.com/NousResearch/hermes-agent/commit/80936550aa2f4246dbd2b6a20f4e3c1e214d724d)) — @seanflynnfilm
- Plugin-catalog): add herm-t3s ([`1fd59c91`](https://github.com/NousResearch/hermes-agent/commit/1fd59c91f45cbb13b4488d9cb28dd1c070315cfb)) — @seanflynnfilm
- Plugin-catalog: add ctxprune ([`9ee8b6cd`](https://github.com/NousResearch/hermes-agent/commit/9ee8b6cdb6fb5908d0fc5374a4f09a296a7e51ab)) — @riceharvest
- Plugin-catalog): add eksis ([`6ce0bec5`](https://github.com/NousResearch/hermes-agent/commit/6ce0bec50c4d06aac34786309572771a90385e5d)) — @yusupsupriyadi
- Catalog): update OpenMail to 0.3.0 with inbox drafts ([`d0ee9276`](https://github.com/NousResearch/hermes-agent/commit/d0ee9276a1ded9c944e19d9ce05284e50c68f336)) — @KOnaitis
- Plugin-catalog): add doubleword-provider ([`bdee8dac`](https://github.com/NousResearch/hermes-agent/commit/bdee8dacde46463ad9328c170d3d3a4cab04472e)) — @jaedmunt
- Plugin-catalog): add Novada MCP ([`95ac0767`](https://github.com/NousResearch/hermes-agent/commit/95ac07670a2034bcacf975fe23bee376374e6f40)) — @Novada-proxy
- Plugin-catalog): add spanish-top-tech-companies plugin ([`5bc7d893`](https://github.com/NousResearch/hermes-agent/commit/5bc7d893cc07df17f714883a04c673c0f180e279)) — @pugarte7
- Hermes-pushover-deliverables ([`67b8c60f`](https://github.com/NousResearch/hermes-agent/commit/67b8c60ffe37f2949ba170412a750fc2d2b754f6)) — @Jessy-Boo
- Plugin-catalog): add meeting-ai ([`11550f28`](https://github.com/NousResearch/hermes-agent/commit/11550f285c24d13021b954e7c2ef15fa4cc146c7)) — @meeting-ai
- Plugin-catalog): add meeting-ai ([`af4bbaff`](https://github.com/NousResearch/hermes-agent/commit/af4bbaff115f9b4a14d2c42d1eebc3e482c6bd89)) — @meeting-ai
- Catalog: add geo-analyzer-mcp entry ([`622dc4ab`](https://github.com/NousResearch/hermes-agent/commit/622dc4abaf8ae44c81f30b6f8d97e0bddee464f2)) — @clance1
- Plugin-catalog: add meragpt (meraGPT Decider) ([`cf8b3b08`](https://github.com/NousResearch/hermes-agent/commit/cf8b3b08b48758782162d811f8479dd46aa27fac)) — @Sandeep85Das
- Plugin-catalog): add mahjonghandbook plugin ([`9bee9adc`](https://github.com/NousResearch/hermes-agent/commit/9bee9adc6e23767cfeb967c94a912e99e477a212)) — @AbigailDavised
- Plugin-catalog): pin layersift to 953903d ([`03598d76`](https://github.com/NousResearch/hermes-agent/commit/03598d76abaaf19e5129b14aec44b1a66d57b8f9)) — @rodricksz4h5
- Plugin-catalog): add layersift ([`4f64be68`](https://github.com/NousResearch/hermes-agent/commit/4f64be6801bd4e2cf6f0682837c038aff2eb27bd)) — @rodricksz4h5
- Plugin-catalog): update hermes-voice-lab to 0.5.0 ([`1ce21740`](https://github.com/NousResearch/hermes-agent/commit/1ce21740f7795db95e54ae2ed7524dfe6ce77f3a)) — @Adolanium
- Plugin-catalog): update hermes-osint-map to 0.5.0 ([`d0daf535`](https://github.com/NousResearch/hermes-agent/commit/d0daf535f4eb98544ceaeb8345636cf4307ad697)) — @Adolanium
- Catalog): add kosa8 Cloud terminal backend ([`c552ac5d`](https://github.com/NousResearch/hermes-agent/commit/c552ac5d17ae45db03125dec497010c0d8853876)) — @drvt69talati
- Plugin-catalog): update sheets to 0.1.10 ([`9219fc34`](https://github.com/NousResearch/hermes-agent/commit/9219fc344ad3ca5229bf4d63bedc7f6f92b8bc8a)) — @Adolanium
- Plugin-catalog): add testerswap plugin ([`c30a706f`](https://github.com/NousResearch/hermes-agent/commit/c30a706fe2500519e834f25270c38c7a3853381b)) — @sohhamm
- Plugin-catalog): bump Planeja+ to 1.0.9 ([`d64fb9b5`](https://github.com/NousResearch/hermes-agent/commit/d64fb9b56ad8cdbf2da7649b8049f0162aff70e0)) — @hendrykcosta75
- Treg-jobs to the plugin catalog ([`93728bd0`](https://github.com/NousResearch/hermes-agent/commit/93728bd01767e8d3a58b75026fa614cd7e058d5a)) — @YAN-XBT
- Plugin-catalog): pin each::labs to 0.4.3 ([`72d92ff3`](https://github.com/NousResearch/hermes-agent/commit/72d92ff303aa21eb05a75e2a693c54da50a3abbd)) — @tiptophelmet
- Plugin-catalog): add each::labs ([`8a5fc9d9`](https://github.com/NousResearch/hermes-agent/commit/8a5fc9d9cd257d99b3965b4a8357b82143fc7b57)) — @tiptophelmet
- Tradersagent-plugin to the catalog ([`e28df7f3`](https://github.com/NousResearch/hermes-agent/commit/e28df7f387437a11a966073feae4e879a92bede3)) — @godzillacode0000
- Catalog: add omp (oh-my-pi terminal backend) ([`272731da`](https://github.com/NousResearch/hermes-agent/commit/272731da4adffc26fb2a75a1c89c3785a6afd4a8)) — @Thaeland
- While.sh: new description (your colleagues, a client with a link and a password, or everyone) ([`0ed9c42e`](https://github.com/NousResearch/hermes-agent/commit/0ed9c42e456e19c440781afbe509c55462fc6dda)) — @while-sh
- Plugin-catalog: add while (while.sh) ([`8e991c7d`](https://github.com/NousResearch/hermes-agent/commit/8e991c7d09f17ab9cc12c3e2c0cce6f5eeb6079d)) — @while-sh
- Plugin-catalog: add while (while.sh) ([`d75c9555`](https://github.com/NousResearch/hermes-agent/commit/d75c9555ee66656316d6bc73aae50dff398c4fe7)) — @while-sh
- Plugin-catalog): add aether plugin ([`800d5c1d`](https://github.com/NousResearch/hermes-agent/commit/800d5c1d94b87fac7d80d4b79910bae64f067993)) — @abundantbeing
- Plugin-catalog): add sol-pi (SoL-Pi ObservationPack + Action Fusion) ([`5c5847d8`](https://github.com/NousResearch/hermes-agent/commit/5c5847d82dbd5b33420054aed29f7bc12a4a8d51)) — @kvnloo
- Catalog: add hermes-pilot (community) ([`1713c7ac`](https://github.com/NousResearch/hermes-agent/commit/1713c7ac78d89cb46884409d8669328f99e8fd85)) — @hajimemanila
- Plugins): add Threadpacket to the catalog ([`ecbc3550`](https://github.com/NousResearch/hermes-agent/commit/ecbc3550ad582aef449742fb3a7714b3210f6c61)) — @evgolsh
- Catalog: add perf-lab 0.1.0 (community) ([`c1aca151`](https://github.com/NousResearch/hermes-agent/commit/c1aca151fa4c8e0ccebecb186e64d7fbccb112d4)) — @Murali-lns
- Plugin-catalog): bump reminders-kanban to 0.1.0-beta.3 ([`ce75e370`](https://github.com/NousResearch/hermes-agent/commit/ce75e3703983e93d94b67e6d75c6c14757ed2546)) — @nicolasdmolina
- Plugin-catalog: add ficelle ([`19005fc3`](https://github.com/NousResearch/hermes-agent/commit/19005fc3453d5a6560ea09498e9de7afadadb2b8)) — @TheBlueHouse75
- Catalog): re-pin phoenix v0.3.1 to HEAD commit 3bc3509 ([`20b65ad0`](https://github.com/NousResearch/hermes-agent/commit/20b65ad0f3ba2423b05106b768460553f46e3ffa)) — @Ratz00007
- Catalog): update phoenix to v0.3.1 (fc43551) ([`23ec2f66`](https://github.com/NousResearch/hermes-agent/commit/23ec2f669ffb7193727c1b1426773e9eb1c914b9)) — @Ratz00007
- Plugin-catalog): update phoenix to v2.0.0 (Flight Recorder &amp; 10k Crash Proof) ([`7e52e3f0`](https://github.com/NousResearch/hermes-agent/commit/7e52e3f005e848d2373bca3bf1530252ab9cede6)) — @Ratz00007
- Catalog: add hermes-make-it-smart ([`1b837865`](https://github.com/NousResearch/hermes-agent/commit/1b8378651538c111cb1c68cf91f0e5ffd064e48d)) — @tesla963
- Catalog: add focus ([`164d0fb1`](https://github.com/NousResearch/hermes-agent/commit/164d0fb133fc5ba1f77c9838b9e3a2665f23abdd)) — @Jemadiar1
- Catalog: add preflight (dry-run gate with approval) ([`5d5276ab`](https://github.com/NousResearch/hermes-agent/commit/5d5276ab35025141df72fd4ff1c644cc35381046)) — @soyluisarca
- Catalog harness2: pin 51acf02, add promote stage ([`b2869e09`](https://github.com/NousResearch/hermes-agent/commit/b2869e090344cea79d7ea085d211bc7b08d080ec)) — @shrinedogg
- Plugin-catalog: add harness2 (Harness^2 self-improvement loop) ([`2890fcc8`](https://github.com/NousResearch/hermes-agent/commit/2890fcc859f2b66abc492a6d6dd7aa6ff2c5e910)) — @shrinedogg
- Models): list GPT-6.2 Astra and Sol (+ Pro) for OpenRouter and Nous Portal ([`4c680fcb`](https://github.com/NousResearch/hermes-agent/commit/4c680fcb2f263d4a87246f513b4f4bf7be10c483))

## 🔧 Improvements

- Plugin-catalog: update hermes-kame-provider to 1.9.0.3 ([`45b65769`](https://github.com/NousResearch/hermes-agent/commit/45b657698cf0ff7950f360b47bad99c74d153776)) — @Kame696
- Plugin-catalog: update hermes-kame-api-rotation to 1.9.0.3 ([`a1f06c28`](https://github.com/NousResearch/hermes-agent/commit/a1f06c28c09df8bb1ee1feb66803895a686a03e3)) — @Kame696
- OpenMail catalog pin to 0.3.2 for attachment IDs ([`5261df67`](https://github.com/NousResearch/hermes-agent/commit/5261df67a3989d68fb44dbecfeb9a2a383f3d54f)) — @KOnaitis
- OpenMail catalog pin to 0.3.1 with draft editing and deletion ([`b94ef42a`](https://github.com/NousResearch/hermes-agent/commit/b94ef42a89936806de8ce7f9e2c06c5ea57a64c3)) — @KOnaitis
- Plugins: update Subnano to 0.3.67 ([`3333c02b`](https://github.com/NousResearch/hermes-agent/commit/3333c02b851f883661dd45b726e466862e1009b1)) — @madsb
- Plugins: update inline to 1.2.2 for responsive agent settings ([`7cef6742`](https://github.com/NousResearch/hermes-agent/commit/7cef674205fa5356b0613075cc4d8e407c263900)) — @morajabi
- Catalog: update hermes-dreaming to 3.8.12 ([`3622da1a`](https://github.com/NousResearch/hermes-agent/commit/3622da1a47bd07e5a48bbf6e28a343dcb32d7ff7)) — @itpartypattaya
- Catalog: update hermes-dreaming to 3.8.11 ([`4dab616c`](https://github.com/NousResearch/hermes-agent/commit/4dab616cfb484d1faf7abb3a725f89fe645e075c)) — @itpartypattaya
- Catalog: update hermes-dreaming to 3.8.10 ([`2f096156`](https://github.com/NousResearch/hermes-agent/commit/2f096156b6b3627dc6d8af55a467822bea3cdff0)) — @itpartypattaya
- Catalog: update hermes-dreaming to 3.8.9 ([`92404d8b`](https://github.com/NousResearch/hermes-agent/commit/92404d8b851efd4eb577329ac586729929a14669)) — @itpartypattaya
- Catalog: update hermes-dreaming to 3.8.8 ([`bf513af8`](https://github.com/NousResearch/hermes-agent/commit/bf513af82bb66b52554c44f0a02266759d490c1d)) — @itpartypattaya
- Catalog: update hermes-guests to 0.1.1 ([`0de3bb0c`](https://github.com/NousResearch/hermes-agent/commit/0de3bb0c2e2243e87d7d9cb5009d53429f5c0b32)) — @d8joseph
- Game Lab localization skills to 0.4.1 ([`96e8eebd`](https://github.com/NousResearch/hermes-agent/commit/96e8eebda6227e860932afbc3c6c66d8ad456d59)) — @flabanabba8
- Pandora.yaml with new version and SHA ([`7e5a7ecc`](https://github.com/NousResearch/hermes-agent/commit/7e5a7ecca9a33af0234ce78191b096f092d6560b)) — @36North
- Version and SHA in hermes-pilot.yaml ([`b09edd33`](https://github.com/NousResearch/hermes-agent/commit/b09edd3395155bc60ebc38db928ec0dcbd3aa255)) — @hajimemanila
- Catalog: update hermes-make-it-smart pin to f06d4ec (v0.32.0 docs HEAD) ([`08de0fd1`](https://github.com/NousResearch/hermes-agent/commit/08de0fd1705f9235240efe64a46b46c546b10146)) — @tesla963
- Feishu): card authz as a cards/ package imported package-relative ([`797be253`](https://github.com/NousResearch/hermes-agent/commit/797be253e1c6722144f269350b715cbf243e2c9a)) — @c2h5oh
- Codex): move developer-prompt wire helpers to codex_responses_adapter ([`2f36063c`](https://github.com/NousResearch/hermes-agent/commit/2f36063cb0e3d53fa200d517bc95983732d5f0df)) — @BearHuddleston
- Discord): move slash-command registry diff into adapter_command_sync ([`c1a3cb0e`](https://github.com/NousResearch/hermes-agent/commit/c1a3cb0e836c5de081ca06448863098f1308329d)) — @kshitijk4poor

## 🐛 Bug Fixes

- Web): preserve profile/state on /learn handoff, cancel on startup paste, and split chat learn tests ([`32dbc1dc`](https://github.com/NousResearch/hermes-agent/commit/32dbc1dcda2255fd35969ec99cfc0170988c3eca)) — @unsupportedpastels
- Web): pass /learn skill handoff via router state and normalize terminal sequences ([`3c59a0f7`](https://github.com/NousResearch/hermes-agent/commit/3c59a0f7c3e831a5a44f69a98fd4e07ef56398c8)) — @unsupportedpastels
- Modal): build a routed profile's client inside the startup deadline ([`58914bf9`](https://github.com/NousResearch/hermes-agent/commit/58914bf9277ea0999b1989775f6b80b407224f1e)) — @kshitijk4poor
- Vault): remove inspection stamps on every exit of the operation that made them ([`9ee2507d`](https://github.com/NousResearch/hermes-agent/commit/9ee2507d992ecc115bb1963ffb75cd0622767105)) — @c2h5oh
- Vault): recheck the pinned channel right before each trusted insert ([`0b6a1170`](https://github.com/NousResearch/hermes-agent/commit/0b6a1170a496efdcd283530ee3b6a8de395b4f7c)) — @c2h5oh
- Vault): refuse a CDP operation whose origin check read no session ([`81874f25`](https://github.com/NousResearch/hermes-agent/commit/81874f25c8d00daa23a76f3f4b806c4bc3a4455b)) — @c2h5oh
- Vault): keep the page-backend fill path off the CDP supervisor ([`19caf311`](https://github.com/NousResearch/hermes-agent/commit/19caf311497a8794c5a8d7f4847f3784bfe1b647)) — @Likivik
- Auth): judge each Nous token by its own arrival time ([`7c7daa25`](https://github.com/NousResearch/hermes-agent/commit/7c7daa25c66262d504e3c2b29ade0ed5928b056e))
- Mcp): a re-login wakes an OAuth-parked server even after a failed revival ([`cbcf56e5`](https://github.com/NousResearch/hermes-agent/commit/cbcf56e5eceb61791d1f6c707ddba42afafaec47))
- Catalog): pin Pushary 1.0.5, which finds its history helper without PATH ([`6c1e7534`](https://github.com/NousResearch/hermes-agent/commit/6c1e7534ead036c471da854d8c1b168564c927c8)) — @aadilghani1
- Catalog): pin pushary 1.0.4 ([`84b92623`](https://github.com/NousResearch/hermes-agent/commit/84b926232fb13a39b92d9b274c673e2c9b3d2567)) — @aadilghani1
- Catalog): show the Pushary quickstart at the 1.0.3 pin ([`b815b483`](https://github.com/NousResearch/hermes-agent/commit/b815b4834ab1614d69b171bd20f37854d3ea5e18)) — @aadilghani1
- Profiles): keep the elevated-Windows ACL repair at the home-directory boundary ([`2b300bea`](https://github.com/NousResearch/hermes-agent/commit/2b300bea92c9d1caed775b01c2f88e30cbde21c8)) — @kshitijk4poor
- Plugin-catalog: re-pin agora to v2.0.14 (fix #12: worker provisioning never created a profile) ([#12](https://github.com/NousResearch/hermes-agent/pull/12)) — @yzy806806
- Catalog): update Hermes Attention to v1.5.2 ([`6e3e55b5`](https://github.com/NousResearch/hermes-agent/commit/6e3e55b59517442286f16fae5e5ae9a6b33fba08)) — @xraysight
- Plugin-catalog): bump pixel-hq to 1.4.0 (1145fa7) — several hosts, read-only ([`3fe8fdd4`](https://github.com/NousResearch/hermes-agent/commit/3fe8fdd43422710ce5b55fa80525cb793099e911)) — @W4-NERF
- Plugin-catalog): update hermes-gensyn-delphi to 8c49f39 ([`f068c77e`](https://github.com/NousResearch/hermes-agent/commit/f068c77e64909de862d93fa69353327d9c367ebb)) — @TakeshiTGAL
- Catalog): update hermes-resetwatch to 0.2.30 ([`cb32d19e`](https://github.com/NousResearch/hermes-agent/commit/cb32d19e95595ebe073924ba5025600ef3297ed5)) — @Adolanium
- Plugin-catalog): update terraform-drift to 11506e5 ([`a9dfc27a`](https://github.com/NousResearch/hermes-agent/commit/a9dfc27a8c6cbd858dff96b2f4e35b56aa95c251)) — @TakeshiTGAL
- Plugin-catalog): re-pin aether to 71129b3 (readable pointer reaction menu) ([`d7ef30b3`](https://github.com/NousResearch/hermes-agent/commit/d7ef30b3ee00d3a0e0f3349438548f7a69dc8b0d)) — @abundantbeing
- Plugin-catalog): re-pin aether to 5067a7a (manifests read with hermes_yaml) ([`c2b0dee0`](https://github.com/NousResearch/hermes-agent/commit/c2b0dee0a163ef25c520a0003b5431224a7e72f5)) — @abundantbeing
- Plugin-catalog): pin reminders-kanban security fixes ([`09eebd18`](https://github.com/NousResearch/hermes-agent/commit/09eebd1873e9fa173dad0ecc0463ca28392831e7)) — @nicolasdmolina
- Catalog): repin reviewed Hermes Unlimited host-gating and feedback isolation ([`2701160b`](https://github.com/NousResearch/hermes-agent/commit/2701160b0e293d389bf03b5924eea4ef0a486646)) — @nsolland
- Feishu): import the card mixins package-relative so a reload reaches cards/ ([`e97efa9c`](https://github.com/NousResearch/hermes-agent/commit/e97efa9c350f1b5a47b8825696af5a7fad6f8778)) — @c2h5oh
- Aux): price a wrapper client's token source keyless ([`ce7cbae3`](https://github.com/NousResearch/hermes-agent/commit/ce7cbae33595e312caa44b32fe2e2a0e11eeddb7)) — @c2h5oh
- Aux): price an aux call with the credential that served it ([`1a310620`](https://github.com/NousResearch/hermes-agent/commit/1a310620c32dda31076e37af2a1c419df1c4780c)) — @c2h5oh
- Models): probe the pool row the strategy would select ([`53af6902`](https://github.com/NousResearch/hermes-agent/commit/53af6902a24ab08c4e678ad50777037849b8bb7e)) — @c2h5oh
- Catalog): drop the duplicated disclosure paragraph in hermes-watchdog ([`77178cf3`](https://github.com/NousResearch/hermes-agent/commit/77178cf306db9d55c175c7fc72e4fd5475472778)) — @33hodl
- Desktop): fall back when idle callbacks are unavailable ([`a1ee88d7`](https://github.com/NousResearch/hermes-agent/commit/a1ee88d79486af3b899b921096363b684b4aa16a)) — @demianad
- Ci): provision Rust for the Linux wheel cache identity ([`c249aca1`](https://github.com/NousResearch/hermes-agent/commit/c249aca1a7015e69f5a32eed8b7aac8e8f18495f)) — @BearHuddleston
- Bundles): account for packed relative relocations in the glibc floor ([`cdca5cca`](https://github.com/NousResearch/hermes-agent/commit/cdca5cca574b10bb39498d01397da6f1e1d965af)) — @BearHuddleston
- Ci): install the X11 headers for the Linux HUD helper ([`bb0da98d`](https://github.com/NousResearch/hermes-agent/commit/bb0da98d96528dd457b9fe601de9feb0e615d918)) — @BearHuddleston
- Release): keep queued Linux builds off the canary publication path ([`0d3a0e8b`](https://github.com/NousResearch/hermes-agent/commit/0d3a0e8b84a16896fafbb24d1a40c3a243b37ca7)) — @BearHuddleston
- Codex): preserve developer system prompt across request_overrides.input ([`d885e6d4`](https://github.com/NousResearch/hermes-agent/commit/d885e6d4bd8595164676647d58a71c9fdc686d62)) — @BearHuddleston
- Codex): send GPT-6.2+ system prompt as leading developer input item ([`a41b998c`](https://github.com/NousResearch/hermes-agent/commit/a41b998c3104f0bce80f3e4fe9b4921d3180f8d5)) — @BearHuddleston
- Discord): preserve scope drift recreation ([`4504606a`](https://github.com/NousResearch/hermes-agent/commit/4504606a397385f90978e0fd8882163728a4f837)) — @andyylin
- Discord guild slash command visibility ([`dc1b4a99`](https://github.com/NousResearch/hermes-agent/commit/dc1b4a990282f1a69766e798947bc6ee98317315)) — @andyylin
- Discord): diff slash commands against the raw registry #104399 ([#104399](https://github.com/NousResearch/hermes-agent/pull/104399)) — @yashiels

## 📚 Documentation

- Mcp): describe the parked self-probe backoff; park logs name it ([`f613e90f`](https://github.com/NousResearch/hermes-agent/commit/f613e90fc67f457da1392ca80843900a094b2dce))
- Plugin-catalog): say what Meeting.ai Coins are ([`815e2369`](https://github.com/NousResearch/hermes-agent/commit/815e23696c1f07823a30c03b12c32a99899839c6)) — @meeting-ai
- Plugin-catalog): describe what Meeting.ai and Hermes each do ([`0712f92e`](https://github.com/NousResearch/hermes-agent/commit/0712f92e02beabc380a2623e1f4e517adad1ed73)) — @meeting-ai
- Plugin-catalog): restore the meeting-ai disclosure ([`bfc4947f`](https://github.com/NousResearch/hermes-agent/commit/bfc4947fd7d2fdc5bd03633adf3231e216a36bc5)) — @meeting-ai
- Plugin-catalog): rewrite the meeting-ai description ([`5992a4ab`](https://github.com/NousResearch/hermes-agent/commit/5992a4abb08c21a9fc4e94c452f1dd575d715d7f)) — @meeting-ai
- Catalog): align disclosures with validated host-only source ([`587a876a`](https://github.com/NousResearch/hermes-agent/commit/587a876abc6f17bb627d2fa40a969477d339b284)) — @nsolland
- Catalog): pin model-leaderboard to 1.6.2 (context price tiers) ([`0182f419`](https://github.com/NousResearch/hermes-agent/commit/0182f419e2d6426b0d74b3a4bd2947f0c252a85e)) — @blavenie
- Plugin-catalog): clarify StalkChain alert delivery ([`7ee3ceab`](https://github.com/NousResearch/hermes-agent/commit/7ee3ceabe0d6a37e508b4795bbafbb388e294455)) — @antoinersx
- Providers): say the snapshot directory reserves its sweep names ([`502009cc`](https://github.com/NousResearch/hermes-agent/commit/502009cc3fe7be2d7bb9a42c1670c14ac0ad9e7b)) — @kshitijk4poor

## 🧪 Tests

- Vault): answer the read-back in the Bitwarden unlock-then-fill test ([`8b2d16ba`](https://github.com/NousResearch/hermes-agent/commit/8b2d16baf982e36760345f34d1c15aa2ea37ab2b)) — @c2h5oh
- Ssl): prove the exported SSL_CERT_FILE bundle over a real handshake on every OS lane ([`f47f6e03`](https://github.com/NousResearch/hermes-agent/commit/f47f6e03d22ede4c812b037fa63a2030e4dc7a10)) — @emozilla
- Bundles): use a portable filename for the ELF byte-order fixtures ([`07e99b4a`](https://github.com/NousResearch/hermes-agent/commit/07e99b4a5e28afb2ef8994bf236bcb539ef9257f)) — @BearHuddleston

## 🏗️ Infrastructure

- Ci): run Linux install/update E2E jobs on Blacksmith ([`fb0be5b0`](https://github.com/NousResearch/hermes-agent/commit/fb0be5b0f920e9e056f5f104cb797a6a4c3a951e)) — @BearHuddleston
- Drop duplicate contributor mapping (main already maps kesuek@users.noreply.github.com) ([`2ea04bd2`](https://github.com/NousResearch/hermes-agent/commit/2ea04bd23e4afdcdb6f881442e0a7b47cfc23d9b))
- Catalog): review disclosure for memrack ([`7fa67891`](https://github.com/NousResearch/hermes-agent/commit/7fa67891c73e2329b4c27bf24bc34257e0ccceba))
- Catalog): review disclosure for swarm-studio ([`7baf0e3f`](https://github.com/NousResearch/hermes-agent/commit/7baf0e3fd9955937a3d613c7e1688662e23a5311))
- Map contributor email for Im5tu ([`d642847a`](https://github.com/NousResearch/hermes-agent/commit/d642847ac2f51c73dfac59836c78a7cb6d0b1756))
- Catalog): review disclosure for onehaus ([`0b83291b`](https://github.com/NousResearch/hermes-agent/commit/0b83291bd877f6bad7be617e0b223b75a1b7d97a))
- Map contributor email for Fiction000 ([`2f9bb931`](https://github.com/NousResearch/hermes-agent/commit/2f9bb9317dfd986d215a822644b6642c783793d4))
- Catalog): review disclosure for its-in-your-head ([`75cda183`](https://github.com/NousResearch/hermes-agent/commit/75cda183d237287a51e1301e25ed633009f85b4b))
- Catalog): review disclosure for hermes-memory-ui ([`906327df`](https://github.com/NousResearch/hermes-agent/commit/906327df44c383d7c20474527e8c99399e759dde))
- Catalog): update hermes-memory-ui pin to v0.7.1 ([`44766ca8`](https://github.com/NousResearch/hermes-agent/commit/44766ca8156b43f6fdbb39e950d2d826bd70d050)) — @xraysight
- Catalog): update hermes-memory-ui to v0.7.0 ([`0c877537`](https://github.com/NousResearch/hermes-agent/commit/0c8775372c1bd76efb7ffa785814aa505378f656)) — @xraysight
- Map contributor email for hendkai ([`9a715caa`](https://github.com/NousResearch/hermes-agent/commit/9a715caa68f5f2fc38f4e8ac7b0f54c52435d559))
- Catalog): review disclosure for credential-pool-switcher ([`8e50e07b`](https://github.com/NousResearch/hermes-agent/commit/8e50e07b394955c371fff986f640413d7adddcdb))
- Plugin-catalog): neural-mesh image URLs use the pinned sha ([`1d28c6cd`](https://github.com/NousResearch/hermes-agent/commit/1d28c6cd80e0ee30a2401feea3ddeb955c18e70d))
- Catalog): review disclosure for composer-predictions ([`5ed4ec5a`](https://github.com/NousResearch/hermes-agent/commit/5ed4ec5acc7e9d0e19ffbf18caf3ec3c390ce763))
- Map contributor email for sesantanajr ([`01d69eed`](https://github.com/NousResearch/hermes-agent/commit/01d69eed9b5c0b8a505a681929fb5a9896110e54))
- Catalog): review disclosure for hermes-atlas-evolution ([`f8de6f8a`](https://github.com/NousResearch/hermes-agent/commit/f8de6f8acb1f674aac978c44e3fbb1b4d08f9932))
- Map contributor email for jacobhausler ([`659aa0b4`](https://github.com/NousResearch/hermes-agent/commit/659aa0b48f6e6d606931c96c640ca4c246b2236d))
- Plugin-catalog): pinned-folders v0.1.15 (sha d5707a8b) ([`ac2c0de9`](https://github.com/NousResearch/hermes-agent/commit/ac2c0de9834dd1e0370ba8811a47dfe23583070b)) — @jacobhausler
- Catalog): review disclosure for hermes-officecraft ([`d060423a`](https://github.com/NousResearch/hermes-agent/commit/d060423a339f90d0a6586294fc810a9f6a53f089))
- Map contributor email for sicruse ([`8a34faba`](https://github.com/NousResearch/hermes-agent/commit/8a34faba531259b2f1f6f1dc00071760a636d06a))
- Catalog): review disclosure for hermes-program-status ([`926f68f7`](https://github.com/NousResearch/hermes-agent/commit/926f68f75eb54897457024d35a7053ce8ceffd02))
- Plugin-catalog): bump bitquery to 1.0.1 (access-token sign-in) ([`a2484ce5`](https://github.com/NousResearch/hermes-agent/commit/a2484ce56b167b252f65e86bd4088532b4159937)) — @divyasshree-BQ
- Ceo-pack to v0.4.1 ([`080e9249`](https://github.com/NousResearch/hermes-agent/commit/080e92494d52f15d7b653d73667bbda1abee99a6)) — @tradersurfer
- Map contributor email for optiq-bot ([`7ebcdb83`](https://github.com/NousResearch/hermes-agent/commit/7ebcdb83a8fb01d19376e8b4399f66cb81e59de0))
- Catalog): review disclosure for holographic ([`916b981e`](https://github.com/NousResearch/hermes-agent/commit/916b981ed4abb23bf6cc305f7b8d5a2fdac42c43))
- Catalog): bump kiro-provider to v1.2.0 ([`37ec743f`](https://github.com/NousResearch/hermes-agent/commit/37ec743fd9f4161bcb994ee47fe1ab5ae715ecbf)) — @anpicasso
- Catalog): review disclosure for proofable-mcp ([`4f3e3926`](https://github.com/NousResearch/hermes-agent/commit/4f3e39268686549ea25648fa589d71f1e0b606d9))
- Plugin-catalog): bump proofable-mcp to 0.1.12 ([`0801e6f6`](https://github.com/NousResearch/hermes-agent/commit/0801e6f6d0767451538d28038c3614677338be6c)) — @chrisjleal
- Catalog): bump caduceus to v0.4.2 ([`73e24631`](https://github.com/NousResearch/hermes-agent/commit/73e2463150d10bb8e62fc565a6085bbdd0329014)) — @100yenadmin
- Catalog): bump caduceus to v0.4.1 ([`d56e7ce6`](https://github.com/NousResearch/hermes-agent/commit/d56e7ce67c137f9cd734cd99b2d59a220eb3ad01)) — @100yenadmin
- Catalog): bump caduceus to v0.4.0 ([`3f0c97b7`](https://github.com/NousResearch/hermes-agent/commit/3f0c97b775c58f8892eda25f91ddfa11d11f3233)) — @100yenadmin
- Catalog): update genealogy recipes to v1.23.0 ([`108b6b10`](https://github.com/NousResearch/hermes-agent/commit/108b6b10d76a4f547f27f74273a46c8376290d10)) — @lazyants
- Catalog): update genealogy recipes to v1.22.0 ([`f3195b74`](https://github.com/NousResearch/hermes-agent/commit/f3195b748d93c4e905307dadf1c69b3d7ba40f3c)) — @lazyants
- Catalog): review disclosure for agora ([`455089e3`](https://github.com/NousResearch/hermes-agent/commit/455089e35cdae0055fb6affa31a8cb62cca52bab))
- Catalog): review disclosure for kanzo-board ([`6af9d21a`](https://github.com/NousResearch/hermes-agent/commit/6af9d21a3ab91b78778d9ab197bbbe437606797c))
- Map contributor email for alessandromoretti90 ([`e1b783d5`](https://github.com/NousResearch/hermes-agent/commit/e1b783d5c74016829a901a3e8c2f68813d1c3b92))
- Map contributor email for aldemaroc ([`7f4fbce3`](https://github.com/NousResearch/hermes-agent/commit/7f4fbce3c3baea77fd7f6ca63871e05b13c7750a))
- Catalog): review disclosure for web-forage ([`33a6aa87`](https://github.com/NousResearch/hermes-agent/commit/33a6aa87c002a26459bfe9dd8ed5a6d6cbc9ed49))
- Map contributor email for RajaRenga ([`6162d669`](https://github.com/NousResearch/hermes-agent/commit/6162d669b72b2c68ac95c698fc5588317067bbdb))
- Catalog): review disclosure for iacg-board, iacg-desk ([`894a4f8f`](https://github.com/NousResearch/hermes-agent/commit/894a4f8f7a9c78b21855c6d1293d8a8549a6cd34))
- Plugin-catalog): bump hermes-zotero to 0.2.1 ([`d285b673`](https://github.com/NousResearch/hermes-agent/commit/d285b673c994929bfaea77061b49ecc37d7ab89e)) — @gerdosi
- Catalog): review disclosure for token-usage ([`275cf0fe`](https://github.com/NousResearch/hermes-agent/commit/275cf0fe9935257559ed2f10c34003b63b9a443e))
- Catalog): review disclosure for promptli-comms ([`75ce4696`](https://github.com/NousResearch/hermes-agent/commit/75ce4696321d08761823de669e8198adb29b441b))
- Plugin-catalog): bump zerofactory to v1.4.1 (f50356eb) ([`9e37cf85`](https://github.com/NousResearch/hermes-agent/commit/9e37cf85c115657ff129c4807c9b7d444c3aeb7c)) — @ntsd
- Plugin-catalog): update zerofactory to v1.4.0 ([`b46da99d`](https://github.com/NousResearch/hermes-agent/commit/b46da99d424b00c2899f27db76d66086fe7ffe01)) — @ntsd
- Catalog): review disclosure for gnani ([`6f386fd0`](https://github.com/NousResearch/hermes-agent/commit/6f386fd04094102208bbb2ab29bc28a0abda6ccb))
- Catalog): pin PLUR1BUS 7.20.1-hermes.0 ([`705aa1f6`](https://github.com/NousResearch/hermes-agent/commit/705aa1f6e156134442fbe047c6c3c57740dbe0bd)) — @Cyb3rb1ade
- Catalog): review disclosure for hermes-kame-provider, hermes-kame-api-rotation ([`906f3d75`](https://github.com/NousResearch/hermes-agent/commit/906f3d75279d19eba6e49ae929274575859f28cb))
- Plugin-catalog): bump local-scout to 1.9.0 (cc05bcf) ([`bd026551`](https://github.com/NousResearch/hermes-agent/commit/bd026551ead3634615c9e5fe448068b826f56906)) — @Angerosteles
- Map contributor email for smallmj ([`c5feeda9`](https://github.com/NousResearch/hermes-agent/commit/c5feeda9f2a1356b54292fe7114b8694e912eb85))
- Catalog): review disclosure for hermes-chat-share ([`6504e06b`](https://github.com/NousResearch/hermes-agent/commit/6504e06b00c58ca2100ecae4f23f3177191f15e4))
- Catalog): review disclosure for webgraft ([`204ae0ab`](https://github.com/NousResearch/hermes-agent/commit/204ae0ab87c879363b6ef20459d5a2cd5043e11c))
- Catalog): review disclosure for ctxprune ([`a433c6ba`](https://github.com/NousResearch/hermes-agent/commit/a433c6ba6fd85b6866c3583339f847fbabafe2ca))
- Catalog): review disclosure for openmail ([`a7e35b34`](https://github.com/NousResearch/hermes-agent/commit/a7e35b340f3a911c490f53d3dc8130f186b195ff))
- Catalog): bump qdrant plugin sha c16cf44-&gt;f995c90 ([`0994e7f3`](https://github.com/NousResearch/hermes-agent/commit/0994e7f32860624c3b5d9a5220a4b033c2a8da7c)) — @YLChen-007
- Catalog): review disclosure for doubleword-provider ([`31edccfb`](https://github.com/NousResearch/hermes-agent/commit/31edccfb59ea27f022ff7ae32d1de1e50d11f045))
- Catalog): review disclosure for adaptlypost ([`3c385718`](https://github.com/NousResearch/hermes-agent/commit/3c3857184cacfce0cf1e3a459afa5f198f686585))
- Plugin-catalog): bump adaptlypost to 1.23.0 ([`95bd05ec`](https://github.com/NousResearch/hermes-agent/commit/95bd05ecd79c8d581ffbf98dc9af7d323c588b14)) — @TarasShyn
- Map contributor email for Novada-proxy ([`2d93c9ef`](https://github.com/NousResearch/hermes-agent/commit/2d93c9efd35931bd0f8add53ad6003bcb4dd40d2))
- Catalog): review disclosure for hermes-pushover-deliverables ([`d3209c15`](https://github.com/NousResearch/hermes-agent/commit/d3209c1572264155009ad925a5e94c140e051cc4))
- Map contributor emails ([`1d779ee4`](https://github.com/NousResearch/hermes-agent/commit/1d779ee43ae0d9786b66a88ff9d30999336580fa)) — @meeting-ai
- Plugin-catalog): pin meeting-ai to v1.0.5 ([`af1222fc`](https://github.com/NousResearch/hermes-agent/commit/af1222fca0dfce9bb229427a13857c85cc819547)) — @meeting-ai
- Catalog): bump cursor-provider to v0.6.0 ([`c02d6e5a`](https://github.com/NousResearch/hermes-agent/commit/c02d6e5aed05c9492273a154800c37c5db8aad01)) — @anpicasso
- Catalog): review disclosure for next-prompt ([`88738bee`](https://github.com/NousResearch/hermes-agent/commit/88738bee9af3cc876df6b2227e0bc2ff627bd1b7))
- Plugin-catalog): bump next-prompt to 0.3.5 ([`4731eba5`](https://github.com/NousResearch/hermes-agent/commit/4731eba523cbfbe9e3d171065fef72bb5280a63d)) — @soymarketing
- Plugin-catalog): bump next-prompt to 0.3.4 ([`bfe7b86e`](https://github.com/NousResearch/hermes-agent/commit/bfe7b86e0d01baeb65c6a6d3430a4697d1ea8800)) — @soymarketing
- Map contributor email for clance1 ([`9e7b973a`](https://github.com/NousResearch/hermes-agent/commit/9e7b973a565a40af7b23a752b9d36cf12cb21470))
- Map contributor email for Sandeep85Das ([`1856a0ad`](https://github.com/NousResearch/hermes-agent/commit/1856a0add953224f9b5dc53803e9f6dbc45f460f))
- Catalog): bump jev-approvals to v0.5.1 ([`1d96991a`](https://github.com/NousResearch/hermes-agent/commit/1d96991a4748ea152f98a5bead14f43efc237d16)) — @anpicasso
- Catalog): bump jev-approvals to v0.5.0 ([`353af932`](https://github.com/NousResearch/hermes-agent/commit/353af93254b52cb4ca86db94537eea39436eb425)) — @anpicasso
- Plugin-catalog): update aamio to 0.7.47 ([`e6d35214`](https://github.com/NousResearch/hermes-agent/commit/e6d3521403259f7257b6bd107a90c90c5963617f)) — @aisenseapi
- Map contributor email for drvt69talati ([`d8074711`](https://github.com/NousResearch/hermes-agent/commit/d80747113ae5416218c9f7b5431ca1468bf20e44))
- Catalog): review disclosure for testerswap ([`3386fbac`](https://github.com/NousResearch/hermes-agent/commit/3386fbace8a900450acefd3c03fa0f601a5c5256))
- Catalog): review disclosure for treg-jobs ([`e74f5728`](https://github.com/NousResearch/hermes-agent/commit/e74f572829888cc6ac85afe25bca67d91e20a0a4))
- Treg-jobs to 0.4.0: pay block ([`edf22618`](https://github.com/NousResearch/hermes-agent/commit/edf226189acbc9a2916a2034e30447f3c2d9a976)) — @YAN-XBT
- Treg-jobs to 0.3.9: panel as a right-zone tab ([`6f02f008`](https://github.com/NousResearch/hermes-agent/commit/6f02f00850b4323fae1642bed8c3b4b8056d716d)) — @YAN-XBT
- Treg-jobs to 0.3.8: single surface ([`d96f2b47`](https://github.com/NousResearch/hermes-agent/commit/d96f2b47841772e7f5200d0b8205cd7bbcb67804)) — @YAN-XBT
- Treg-jobs to 0.3.7: single surface ([`5687df83`](https://github.com/NousResearch/hermes-agent/commit/5687df83d21fca004f059151a4a6110bda21086a)) — @YAN-XBT
- Treg-jobs to 0.3.6: narrow-pane truncation ([`a163794e`](https://github.com/NousResearch/hermes-agent/commit/a163794e53c2ba86e763027b9394f75b760e260e)) — @YAN-XBT
- Treg-jobs to 0.3.5: status picker, profile block ([`ad479d67`](https://github.com/NousResearch/hermes-agent/commit/ad479d679b792c7f37ee5c222b73568227109bb6)) — @YAN-XBT
- Treg-jobs to 0.3.3: narrow-pane layout fix ([`2680b431`](https://github.com/NousResearch/hermes-agent/commit/2680b4311f304561f51db7d175b7ccd8145740cd)) — @YAN-XBT
- Treg-jobs to 0.3.2: employer domain + address cross-check ([`117bc009`](https://github.com/NousResearch/hermes-agent/commit/117bc0094a4a01e5734bca981c43de2ef48405f7)) — @YAN-XBT
- Treg-jobs to 0.3.1: the pane docks beside the chat ([`6f7573f7`](https://github.com/NousResearch/hermes-agent/commit/6f7573f7050891d0b5f3de744b8e4611cfe24d2b)) — @YAN-XBT
- Catalog): update hermes-egm to v0.4.0 ([`56b024d5`](https://github.com/NousResearch/hermes-agent/commit/56b024d5bcd0e135a5dfc02293c658e5c0ac24fa)) — @willbohn
- Map contributor email for tiptophelmet ([`5e6eea4c`](https://github.com/NousResearch/hermes-agent/commit/5e6eea4c13c40826cf3a5feda389d2f444927e6b))
- Catalog): review disclosure for eachlabs ([`dd906da6`](https://github.com/NousResearch/hermes-agent/commit/dd906da63d15bcd843c4d57afe9b22354b1e1781))
- Catalog): bump my-github pin to 1.2.6 ([`bca5e557`](https://github.com/NousResearch/hermes-agent/commit/bca5e557eaeaa9766a250305875c392599c8d5f8)) — @tomekdot
- Map contributor email for godzillacode0000 ([`c33a0370`](https://github.com/NousResearch/hermes-agent/commit/c33a037077a0495913895527116638220d6d3b8a))
- Catalog): review disclosure for tradersagent-plugin ([`aa733259`](https://github.com/NousResearch/hermes-agent/commit/aa7332599c24ddf56cbac5e3b13adb62f6c4d02a))
- Map contributor email for Thaeland ([`cbcd0022`](https://github.com/NousResearch/hermes-agent/commit/cbcd00220ccd1b93cd15e0a96b58195c23431277))
- Catalog): review disclosure for oh-my-pi-terminal-backend ([`64afa3b0`](https://github.com/NousResearch/hermes-agent/commit/64afa3b0dc4568273b0af97565d80507421b6a0b))
- Map contributor email for mr-pewpy ([`637f5c9c`](https://github.com/NousResearch/hermes-agent/commit/637f5c9c23eec8f0ed5d6a2aebc7283d7554f2a4))
- Catalog): review disclosure for model-forge-desktop, model-forge-image, model-forge-providers, model-forge-video, model-forge ([`bb97df4e`](https://github.com/NousResearch/hermes-agent/commit/bb97df4ed041206fa2771a8eb0605561305fa822))
- Map contributor email for niyonx ([`969088f4`](https://github.com/NousResearch/hermes-agent/commit/969088f48d061339078342f6d889835f8a0c0d49))
- Catalog): review disclosure for postonce ([`024b1cbd`](https://github.com/NousResearch/hermes-agent/commit/024b1cbd47072a9e0f8de1f03a8c99671b22064f))
- Map contributor email for hajimemanila ([`1ebe4dfb`](https://github.com/NousResearch/hermes-agent/commit/1ebe4dfbfde2c942bc31c4dbc3222113116239dd))
- Catalog): review disclosure for hermes-pilot ([`f4f5225f`](https://github.com/NousResearch/hermes-agent/commit/f4f5225f78b19bdc0c8613b7fcd3a1cb7026cb28))
- Catalog): review disclosure for threadpacket ([`e93c09aa`](https://github.com/NousResearch/hermes-agent/commit/e93c09aa76e63df8e6d7f63dbe192b7bfa965f01))
- Map contributor email for rahlquist ([`26880d57`](https://github.com/NousResearch/hermes-agent/commit/26880d573ee3f42b4ba4d3a227519e335413063e))
- Catalog): review disclosure for perf-lab ([`9d7d983a`](https://github.com/NousResearch/hermes-agent/commit/9d7d983a12bdafa1bbe7828af08831dbbecaafe6))
- Plugin-catalog): kanban-gantt disclosure at merge ([`c1354463`](https://github.com/NousResearch/hermes-agent/commit/c1354463369f86ba1ea46cdbe19f8196878b7765))
- Catalog): review disclosure for hermes-unlimited ([`25aac37a`](https://github.com/NousResearch/hermes-agent/commit/25aac37a03f8a89cf7c5c94de9b1cb4094b76862))
- Catalog): pin live-tested Socratic Council and disclose excerpt limits ([`060659af`](https://github.com/NousResearch/hermes-agent/commit/060659af50ae605620a36152f498da7bdd295be3)) — @nsolland
- Catalog): pin fully tested Hermes Unlimited review fixes ([`d082c219`](https://github.com/NousResearch/hermes-agent/commit/d082c219290e1ec86b076748ebb94c38172b3b81)) — @nsolland
- Catalog): pin reviewed host-only alpha.6 source with clean validator ([`9dd41345`](https://github.com/NousResearch/hermes-agent/commit/9dd413451c9c289bd7fc187f827257a5b909d97b)) — @nsolland
- Catalog): repin alpha.6 draft to host-worker-only merged source ([`024be011`](https://github.com/NousResearch/hermes-agent/commit/024be0119f6984704030e768be8b11061874086e)) — @nsolland
- Plugin-catalog): prepare Hermes Unlimited alpha.6 rrglab repin for review ([`e652b42a`](https://github.com/NousResearch/hermes-agent/commit/e652b42afd2a14a66b0501b7ad4871f59e526d3e)) — @nsolland
- Map contributor email for Ratz00007 ([`06cf35e1`](https://github.com/NousResearch/hermes-agent/commit/06cf35e1d7122617a2c9115f15d06bb7d76ad036))
- Map contributor email for Ratz00007 ([`89fc026f`](https://github.com/NousResearch/hermes-agent/commit/89fc026f10e7f322a57441ce03f10d21fc33e32e))
- Catalog): pin phoenix to 7e8b3c1 and soften exactly-once wording ([`fdaf666c`](https://github.com/NousResearch/hermes-agent/commit/fdaf666c3bbc93cd63d54b69120976635fcc0f19)) — @Ratz00007
- Catalog): review disclosure for hermes-make-it-smart ([`f43eb42c`](https://github.com/NousResearch/hermes-agent/commit/f43eb42cab2667d6e24daea5d52bcc9516e5b3e2))
- Map contributor email for Kattegat-crew ([`d506893b`](https://github.com/NousResearch/hermes-agent/commit/d506893bb0fa89176d1410b02dbddebea38967af))
- Map contributor email for Kattegat-crew ([`ceeee6fd`](https://github.com/NousResearch/hermes-agent/commit/ceeee6fdd06cb29ab50ae8ca0f8b68d179e134a3))
- Catalog): review disclosure for focus ([`0f8a27f9`](https://github.com/NousResearch/hermes-agent/commit/0f8a27f96d3eb1e6dfe1c98f062830a3f36cf3e4))
- Catalog): re-pin focus to bd78490 (v0.1.1) ([`3b828d64`](https://github.com/NousResearch/hermes-agent/commit/3b828d6466ecef46bd3c902230a2de9f662c2e8e)) — @Jemadiar1
- Catalog): re-pin focus to baebf1c (v0.1.1) ([`7b95622d`](https://github.com/NousResearch/hermes-agent/commit/7b95622ddd76cae16e3ba33c509868b02b8d44c3)) — @Jemadiar1
- Catalog): re-pin focus to da49306 (v0.1.1) ([`ed5ff253`](https://github.com/NousResearch/hermes-agent/commit/ed5ff25300651a02637bcc1848449ed82419da34)) — @Jemadiar1
- Catalog): re-pin focus to 23e7843 (v0.1.1) ([`480c16f3`](https://github.com/NousResearch/hermes-agent/commit/480c16f36c73f763bdb880776c93dbed1484ff3a)) — @Jemadiar1
- Catalog): re-pin focus to 34bbac4 (v0.1.1) ([`35a8ecfd`](https://github.com/NousResearch/hermes-agent/commit/35a8ecfd2513f76266ed01643853d4ab611fd341)) — @Kattegat-crew
- Catalog): review disclosure for sieve ([`a36f9cef`](https://github.com/NousResearch/hermes-agent/commit/a36f9cefd51e530e393115022f44c5190060a47c))
- Catalog): review disclosure for preflight ([`a3ea7f85`](https://github.com/NousResearch/hermes-agent/commit/a3ea7f85771834707a8045696aeef4860ed04247))
- Map contributor email for k58v2hbzkk-del ([`4829926d`](https://github.com/NousResearch/hermes-agent/commit/4829926da710cf2e322d43c7b2aa581a67fcc11f))
- Catalog): review disclosure for callit ([`8f4e700b`](https://github.com/NousResearch/hermes-agent/commit/8f4e700bec4ede4cc4a447911e945a1667bc67ee))
- Catalog): review disclosure for harness2 ([`45c8c71a`](https://github.com/NousResearch/hermes-agent/commit/45c8c71abab8b1e242ba5f68100e0ebe62ef4453))
- Catalog): review disclosure for model-leaderboard ([`e134f89c`](https://github.com/NousResearch/hermes-agent/commit/e134f89c9980ce76463d9bf2de14481dc5e8654d))
- Contributors): map demianad email for #146673 salvage ([#146673](https://github.com/NousResearch/hermes-agent/pull/146673)) — @BearHuddleston

## 📦 Other Changes

- Catalog: rom-studio 0.3.0 ([`d7a6e228`](https://github.com/NousResearch/hermes-agent/commit/d7a6e2285f4d0a729e52f9f2bf25a98d8360a304)) — @erosika
- Swarm-studio: re-pin to 0.4.1 (b79a6fa0) ([`65fc774d`](https://github.com/NousResearch/hermes-agent/commit/65fc774df52b8a05135b474ddded2178a6e8afb7)) — @Pukujan
- Plugin-catalog(swarm-studio): re-pin to 5462f4d after review fixes; disclosure updated ([`a1d6a990`](https://github.com/NousResearch/hermes-agent/commit/a1d6a99052dbae54f09a10f219ce563b16a74e1d)) — @Pukujan
- Swarm-studio: pin e56eebc (0.3.0) ([`bded142f`](https://github.com/NousResearch/hermes-agent/commit/bded142fc892bc07f26323f6ecd82a3a86edac75)) — @Pukujan
- Plugin-catalog: tenure 1.1.1 → 1.1.2 (#7 follow-up) ([#7](https://github.com/NousResearch/hermes-agent/pull/7)) — @otsoa-dubief
- Plugin-catalog: tenure 1.1.0 → 1.1.1 (secrets typed in terminal commands masked) ([`36aba92d`](https://github.com/NousResearch/hermes-agent/commit/36aba92d733aa8e0d2160d823a37a4eda1343c31)) — @otsoa-dubief
- Plugin-catalog: its-in-your-head v0.1.31 (official art, value-first description, mood cards) ([`be27d3bb`](https://github.com/NousResearch/hermes-agent/commit/be27d3bb7ab64c49994c5b039bb6daf3d675acfa)) — @hi4c0ck
- Repin hermes-vision-inline to 1.1.1 ([`3f21cfab`](https://github.com/NousResearch/hermes-agent/commit/3f21cfab07ed282a1e04086cf0f09567ea661a32)) — @BrokeSkill
- Plugin-catalog: bump credential-pool-switcher to 1.3.1 ([`6aee62b6`](https://github.com/NousResearch/hermes-agent/commit/6aee62b6ef0fed78010be33d03d65b6d8ccd4aea)) — @hendkai
- Plugin-catalog: re-pin neural-mesh to 93f98fd (v0.46.0 upstream, no code change) ([`7c3efafe`](https://github.com/NousResearch/hermes-agent/commit/7c3efafe2b2c4e16d86f0a4eb90655057c6fca2f)) — @D0xedDevi0
- Plugin-catalog: re-pin neural-mesh to v0.45.0 (281b7b38) ([`736c3ea9`](https://github.com/NousResearch/hermes-agent/commit/736c3ea95ee02c9dc3024fb1743886e5f56c7713)) — @D0xedDevi0
- Plugin-catalog: bump plan-mode to 1.6.0 ([`d010175b`](https://github.com/NousResearch/hermes-agent/commit/d010175bf2b5bc887948b8963a0461cec7664fa9)) — @100yenadmin
- Plugin-catalog: holographic 0.30.0 ([`fa58ac39`](https://github.com/NousResearch/hermes-agent/commit/fa58ac39436cc508fc1e06bf59ec00d0da94634f)) — @itpartypattaya
- Plugin-catalog: holographic 0.29.3 ([`4f474590`](https://github.com/NousResearch/hermes-agent/commit/4f4745901654ce6100ecf2915be71e107928162f)) — @itpartypattaya
- Catalog: pin Yandex presentation updates to merged commits ([`b5bf69e2`](https://github.com/NousResearch/hermes-agent/commit/b5bf69e258e57dedd03e9b644ce91d0e62cbc947)) — @akinfold
- Catalog: use lighter Yandex banners and inline README badges ([`6f59e5c3`](https://github.com/NousResearch/hermes-agent/commit/6f59e5c3ef8f1fcdb5599fd32e3c4d1734bf4a80)) — @akinfold
- Catalog: bump antigravity-subscription-directsdk pin to v1.0.29 ([`fd1b5873`](https://github.com/NousResearch/hermes-agent/commit/fd1b5873bc2749ea21a6d914de3bee0402b77e8b)) — @soyelmismo
- Catalog: bump antigravity-subscription-directsdk pin to v1.0.28 ([`2692bdcb`](https://github.com/NousResearch/hermes-agent/commit/2692bdcbcae81fa03d91b0d92216616c8809d079)) — @soyelmismo
- Cobrain: mark server untrusted, re-pin to 8010aef ([`ccea4b85`](https://github.com/NousResearch/hermes-agent/commit/ccea4b85b63efd2ca1df851e3f70b40932b2296d)) — @alessandromoretti90
- Cobrain: descriptive title ([`99388ce7`](https://github.com/NousResearch/hermes-agent/commit/99388ce7b1f2c51340253de672a12b253dd35fa4)) — @alessandromoretti90
- Web-forage: re-pin to 1.3.0 ([`349f5028`](https://github.com/NousResearch/hermes-agent/commit/349f50289ff765c033e32086f8ba025053b65df1)) — @aldemaroc
- Web-forage: re-pin to 1.2.2 (private target policy) ([`8f62bd57`](https://github.com/NousResearch/hermes-agent/commit/8f62bd57726cc10f06d4615600d8f5694ae48667)) — @aldemaroc
- Catalog: re-pin iacg-desk + iacg-board to 7ba880e (address security review) ([`e24aad6b`](https://github.com/NousResearch/hermes-agent/commit/e24aad6bf194f74bfbc59048785a7922e110fa95)) — @RajaRenga
- Catalog: re-pin iacg entries to af56feb (S3 sync + pickup + filesystem board) ([`f731ce2f`](https://github.com/NousResearch/hermes-agent/commit/f731ce2f094b62cd673d262dcc320358418e7c79)) — @RajaRenga
- Catalog: re-pin iacg entries to 263e7b7 (Continue in chat button) ([`d231a65b`](https://github.com/NousResearch/hermes-agent/commit/d231a65b499744e1cf0c0b770697f69be82f5e1e)) — @RajaRenga
- Catalog: re-pin iacg entries to b8d7104 (board readiness guidance + workflow guide) ([`f2c1d61a`](https://github.com/NousResearch/hermes-agent/commit/f2c1d61a6a657863362fc03fb544d68415fa72d0)) — @RajaRenga
- Catalog: re-pin iacg entries to 89bd572 (LF release archive) ([`9a2b6345`](https://github.com/NousResearch/hermes-agent/commit/9a2b6345e3c98d761ca14ae6600777291912405d)) — @RajaRenga
- Catalog: re-pin iacg entries to 9462664 (knowledge onboarding in intake) ([`8dbfb3b9`](https://github.com/NousResearch/hermes-agent/commit/8dbfb3b9b94a5f5a5fe2aafa043b9a3e9f7bfb1d)) — @RajaRenga
- Catalog: re-pin iacg entries to ae7f994 (profile knowledge); IaCGenius naming ([`c0c7cde9`](https://github.com/NousResearch/hermes-agent/commit/c0c7cde95ac67dd5a044c552cf421468b309cd1f)) — @RajaRenga
- Catalog: re-pin iacg entries to 5c1f1f2; use the marketplace banner image ([`164b3b69`](https://github.com/NousResearch/hermes-agent/commit/164b3b693afca8f42f2b2b03555c7c7e38586809)) — @RajaRenga
- Create token-usage.yaml for plugin configuration ([`9f1f6900`](https://github.com/NousResearch/hermes-agent/commit/9f1f690053baf62008c7ddb8d2ebd9e95971d7f8)) — @priyankarpal
- Catalog: bump pilot to 0.4.1 (a1459dd -&gt; 3724e8f) ([`f02d146b`](https://github.com/NousResearch/hermes-agent/commit/f02d146b66aebd3debe9afd1df20777e8f4ab665)) — @LangerSword
- Plugin-catalog: bump solverforge-planner to 0.4.1 ([`98663faa`](https://github.com/NousResearch/hermes-agent/commit/98663faa95f993e161fc68ae1e07777ec5d3425d)) — @blackopsrepl
- Plugin-catalog: re-pin kumi to 9ab8a1ed ([`9a2a81eb`](https://github.com/NousResearch/hermes-agent/commit/9a2a81eb85a0be6f98ee326f67907cc4c12ebe6d)) — @user1303836
- Plugin-catalog: re-pin mock-review to v2.1.0 ([`1448f666`](https://github.com/NousResearch/hermes-agent/commit/1448f6665df75bf1b3735b5cc9c1257ede415c60)) — @arspesk
- Plugin-catalog: keep the mock-review showcase screenshot from v1.2.0 ([`b26c9ee3`](https://github.com/NousResearch/hermes-agent/commit/b26c9ee3a986e236fb5ab3e9e61a1d61770bde57)) — @arspesk
- Plugin-catalog: re-pin mock-review to v2.0.0 ([`f436d8e4`](https://github.com/NousResearch/hermes-agent/commit/f436d8e4d83ef8bf9cc12099427bcf9267edb93b)) — @arspesk
- Catalog: hermes-chat-share 1.2.0 ([`c2a7f879`](https://github.com/NousResearch/hermes-agent/commit/c2a7f8793cfaea813403d9af9d2e2084a1c55126)) — @smallmj
- Webgraft: re-pin to 28f80fc (0.3.2, tests green on Linux too) ([`4b44229f`](https://github.com/NousResearch/hermes-agent/commit/4b44229f15c902d3d2a5f6f31b21f62603c86979)) — @ElSerda
- Plugin-catalog: bump flightdeck to 0.1.2 (120b9932) ([`ef8f151e`](https://github.com/NousResearch/hermes-agent/commit/ef8f151ed83a4d822debf94def507a3c855bb16a)) — @Freeman-Consulting
- Plugin-catalog: bump memtomem-memory to 0.2.2 ([`7112205a`](https://github.com/NousResearch/hermes-agent/commit/7112205abf70cc7fbb10fd1b96071fb2acfa46a3)) — @memtomem
- Plugins: pin inline 1.2.1 for inbound delivery recovery ([`5b209088`](https://github.com/NousResearch/hermes-agent/commit/5b209088f2027c295e5241d3358ae6cca4cc1f59)) — @morajabi
- Plugin-catalog: bump hermes-custodian to 0.1.1 ([`339d9176`](https://github.com/NousResearch/hermes-agent/commit/339d917633cd5e3231283c90c48d88696181b5c5)) — @Cam-AcitveIce
- Plugin-catalog: agent-security-guard 0.6.0 ([`eb183917`](https://github.com/NousResearch/hermes-agent/commit/eb183917f945377c3edd37645b4ffcb40497acb5)) — @xMannixx
- Plugin-catalog: bump traceverse_hermes_otel to 2.1.0 ([`e720721c`](https://github.com/NousResearch/hermes-agent/commit/e720721c7d936ee4fe78646057cfca6966ccd429)) — @Mandark-droid
- Plugin-catalog: heartbeat2 0.4.28 ([`be493df8`](https://github.com/NousResearch/hermes-agent/commit/be493df8fbb2bc93fa8b007ef3dfb8ab73d6c960)) — @100yenadmin
- Plugin-catalog: tldr 6.0.1 (clearer ELI5 on decision cards) ([`616d7ff1`](https://github.com/NousResearch/hermes-agent/commit/616d7ff117ee89d05ffaad3427586cfe54446d4e)) — @ShawnCRMer
- Catalog: pin idealphase-elevenlabs-audio-tags to v0.1.2 ([`03afe5fa`](https://github.com/NousResearch/hermes-agent/commit/03afe5fa65de0b726c0a8549bbd08f6fb7d24f20)) — @telnetaisha
- Pin Game Lab translation dimension checks ([`cd8ac511`](https://github.com/NousResearch/hermes-agent/commit/cd8ac51101cf73b2002e05073d88e96599f5aa8c)) — @flabanabba8
- Point the entry at the renamed repository ([`e9040b4e`](https://github.com/NousResearch/hermes-agent/commit/e9040b4eb1008afbdaef282a5ab33c4639b45c16)) — @YAN-XBT
- Plugin-catalog: breadcrumbs 0.5.0 -&gt; bundle 4824735 (the plugin is its own repository, breadcrumbs-hermes-release) ([`b85b303a`](https://github.com/NousResearch/hermes-agent/commit/b85b303a81c9bf63fc2433e1ce02b9916cb44781)) — @jnorthrup
- Pin nyx-wiki-recall to the hook-registration fix. ([`27b2ce15`](https://github.com/NousResearch/hermes-agent/commit/27b2ce1503cb705104e14fc3385dfeded49f79aa)) — @blacksmithFF
- Catalog: bump prompt-firewall pin to 1.1.6 (7c2dcdd6) ([`ad20cb22`](https://github.com/NousResearch/hermes-agent/commit/ad20cb22999eeb6f4ea723f645a614037b789d47)) — @Gaijin-01
- Catalog: re-pin tradersagent-plugin to 3c92721 (console agent bridge removed) ([`bb6f7bd8`](https://github.com/NousResearch/hermes-agent/commit/bb6f7bd8323fb7cea0cd327b9fc541493e5c24cb)) — @godzillacode0000
- Catalog/omp: re-pin sha (round-3 review fixes) ([`5f4671f5`](https://github.com/NousResearch/hermes-agent/commit/5f4671f53b7ccb56b4bb6cd8366bfd56ad8e42c8)) — @Thaeland
- Catalog/omp: repo renamed to Thaeland/oh-my-pi-terminal-backend, re-pin sha ([`682d5206`](https://github.com/NousResearch/hermes-agent/commit/682d5206c1d9462b446881e1c13a03d96fc9a2b2)) — @Thaeland
- Catalog: rename omp -&gt; oh-my-pi-terminal-backend, re-pin sha ([`1e87fe5a`](https://github.com/NousResearch/hermes-agent/commit/1e87fe5ae4e8df1b097ecb6f6b785db8b6161e15)) — @Thaeland
- Catalog/omp: platforms +windows (verified on Win11 Pro), re-pin sha ([`c51f9693`](https://github.com/NousResearch/hermes-agent/commit/c51f9693f65b430620ba7959322520028365af46)) — @Thaeland
- Catalog/omp: re-pin sha (probe + remediation message polish) ([`b847e4ba`](https://github.com/NousResearch/hermes-agent/commit/b847e4bad669a3157c9e1505d5bc18fd635bf140)) — @Thaeland
- Catalog/omp: re-pin sha (Windows-ready changes + probe script) ([`ab30774d`](https://github.com/NousResearch/hermes-agent/commit/ab30774d0aaa70a07f1ba5f84f7416a13df53bc1)) — @Thaeland
- Catalog/omp: re-pin sha (README install-compatibility note) ([`3e542261`](https://github.com/NousResearch/hermes-agent/commit/3e542261ae927eb57f380bc851853df1a2967ff1)) — @Thaeland
- While: re-pin to the commit that marks the server untrusted; setup step adds trust: untrusted ([`d75e39ab`](https://github.com/NousResearch/hermes-agent/commit/d75e39ab332c984fc90aaca16436484a15d4afa2)) — @while-sh
- While.sh: deploy and share tools built with AI (your team, a client or everyone) ([`64e51a85`](https://github.com/NousResearch/hermes-agent/commit/64e51a8572047fef89111eba6902e0c5867c8245)) — @while-sh
- Plugin-catalog: while, one address (free to try without an account), pinned to the current public repo ([`54f00e9f`](https://github.com/NousResearch/hermes-agent/commit/54f00e9f2d96ca1dea09934e3a4e4fddc4ebeea0)) — @while-sh
- Plugin-catalog: re-pin Model Forge packages to 7b56449 (v1.1.0 review fixes) ([`57b19fd3`](https://github.com/NousResearch/hermes-agent/commit/57b19fd37111860180198b412a94aefde39fb5ec)) — @mr-pewpy
- Plugin-catalog: re-pin Model Forge entries to v1.1.0 ([`82e63ee0`](https://github.com/NousResearch/hermes-agent/commit/82e63ee04e5ae095be35e583cddc71de56e2cc4b)) — @mr-pewpy
- Plugin-catalog: re-pin postonce to 41fbb6e ([`5e54e432`](https://github.com/NousResearch/hermes-agent/commit/5e54e432215f80439eca648e75bf728749c95f24)) — @niyonx
- Catalog(goneby): re-pin to v1.1.1 (99a7099) — profile isolation restored ([`62720338`](https://github.com/NousResearch/hermes-agent/commit/627203381ce5e0b38b9a2fac06bd1c693ac20640)) — @rahlquist
- Catalog: perf-lab re-pinned to 5fd7214 (run approval, minimal env, stricter command checks) ([`82797020`](https://github.com/NousResearch/hermes-agent/commit/82797020b5cd5adc6a5b5b19f923986d66243487)) — @Murali-lns
- Catalog: perf-lab pin 2d81810 (speed-word fix) ([`6bc83f46`](https://github.com/NousResearch/hermes-agent/commit/6bc83f46a8b319ecb66306779b576e1324b2891f)) — @Murali-lns
- Catalog: perf-lab disclosure wording ([`81415618`](https://github.com/NousResearch/hermes-agent/commit/81415618706904bdb5ee20f6ab55f9a5ca868770)) — @Murali-lns
- Plugin-catalog: nexus (#157188) ([#157188](https://github.com/NousResearch/hermes-agent/pull/157188)) — @Neboy72
- Plugin-catalog: fotor (#157252) ([#157252](https://github.com/NousResearch/hermes-agent/pull/157252)) — @jovijovi
- Plugin-catalog: air-agent-kya (#157762) ([#157762](https://github.com/NousResearch/hermes-agent/pull/157762)) — @armanmamyan
- Plugin-catalog: kanban-gantt (#157179) ([#157179](https://github.com/NousResearch/hermes-agent/pull/157179)) — @blavenie
- Plugin-catalog: hermes-studiotwin (#157072) ([#157072](https://github.com/NousResearch/hermes-agent/pull/157072)) — @dbitzas
- Plugin-catalog: re-pin ficelle to 0b7c0fa (drop connector recommendation) ([`3dc23b29`](https://github.com/NousResearch/hermes-agent/commit/3dc23b294fc51153988c64ef00ba720234c4bacd)) — @TheBlueHouse75
- Plugin-catalog: pin Hermes Unlimited beta.7 packaged import fix ([`04cf65e3`](https://github.com/NousResearch/hermes-agent/commit/04cf65e3ef22110ec8723fee7ca971bc90e3f9cd)) — @nsolland
- Plugin-catalog: pin official rrglab beta.6 economic scenarios (17 tools) ([`099881b4`](https://github.com/NousResearch/hermes-agent/commit/099881b4bb58f956bf74c56fc1a15b129afcea2c)) — @nsolland
- Plugin-catalog: pin official rrglab beta.5 compatible with stock Hermes ([`15a11ba3`](https://github.com/NousResearch/hermes-agent/commit/15a11ba3d28ffb568a359f94714227bbf35b4456)) — @nsolland
- Plugin-catalog: pin rrglab verified beta.4 (16 bounded tools) ([`fd8b6c9b`](https://github.com/NousResearch/hermes-agent/commit/fd8b6c9b85bb492640c334dd0de899e365139a9c)) — @nsolland
- Plugin-catalog: pin rrglab verified beta.3 with 15 bounded tools ([`615239ce`](https://github.com/NousResearch/hermes-agent/commit/615239ceb37668a304d073bd4e4a6032e5a1177a)) — @nsolland
- Plugin-catalog: pin verified rrglab beta.2 (14 bounded tools) ([`a2d7afa9`](https://github.com/NousResearch/hermes-agent/commit/a2d7afa9825a4c11f924e433cc600684262bbaa5)) — @nsolland
- Plugin-catalog: repin Hermes Unlimited to verified rrglab alpha.4 release ([`00b07b3c`](https://github.com/NousResearch/hermes-agent/commit/00b07b3c78da2c5176ddcfff6c3a5bcd84b715e9)) — @nsolland
- Plugin-catalog: repin Hermes Unlimited to reviewed rrglab alpha.8 (20 tools, 3 hooks) ([`b4f39431`](https://github.com/NousResearch/hermes-agent/commit/b4f39431f3010232cd2d7495e12dac356012830f)) — @nsolland
- Catalog: pin hermes-make-it-smart to b005782 (v0.32.0) ([`c588bc9f`](https://github.com/NousResearch/hermes-agent/commit/c588bc9f7271ef720c5fc88a0afc4fe9fd078026)) — @tesla963
- Catalog: bump hermes-make-it-smart to v0.31.0 (12d586d) and correct the disclosure ([`cad5ef30`](https://github.com/NousResearch/hermes-agent/commit/cad5ef30cad98458f3d388bbbf27fdfe748274ad)) — @tesla963
- Catalog: bump hermes-make-it-smart to v0.30.0 (f0f7970) ([`2581b85d`](https://github.com/NousResearch/hermes-agent/commit/2581b85db7aa694c0fd0fc825a56246415dadae3)) — @tesla963
- Catalog: bump hermes-make-it-smart to v0.29.0 (4598aef) ([`dd32d626`](https://github.com/NousResearch/hermes-agent/commit/dd32d626ca13184e41598353ffc542cfade64883)) — @tesla963
- Catalog: bump hermes-make-it-smart to v0.27.3 (4b2df66) ([`6e79201a`](https://github.com/NousResearch/hermes-agent/commit/6e79201ab0f9db5bcf4eb175144096e7d32e5aea)) — @tesla963
- Catalog: bump hermes-make-it-smart to v0.27.2 (072cb42) ([`cfcfba39`](https://github.com/NousResearch/hermes-agent/commit/cfcfba398d3c65663439162dc6470a144d06c578)) — @tesla963
- Catalog: bump hermes-make-it-smart to v0.27.1 (96c1645) ([`cdc6e4ec`](https://github.com/NousResearch/hermes-agent/commit/cdc6e4ecfe6ee178628dea53f1eeddf2a3d3dfe1)) — @tesla963
- Catalog: bump hermes-make-it-smart to v0.27.0 (d365b1b) ([`057e435e`](https://github.com/NousResearch/hermes-agent/commit/057e435e95436cd079105b87a4c02ee5ff8d5c4b)) — @tesla963
- Catalog: bump hermes-make-it-smart to v0.26.1 (57a9e2a) ([`665e032c`](https://github.com/NousResearch/hermes-agent/commit/665e032c91ea44c32163e2b2f78445e5940d460b)) — @tesla963
- Catalog: bump hermes-make-it-smart to v0.26.0 (50a2a9b) ([`c9cd88d1`](https://github.com/NousResearch/hermes-agent/commit/c9cd88d17b267d7ea94cab49f37cf75e9b11c40f)) — @tesla963
- Catalog(focus): pin sha c34c1fb with markdown section hierarchy and two-phase grounding ([`a00ed781`](https://github.com/NousResearch/hermes-agent/commit/a00ed78127407f36a34dc5c28ab9700c4d21ca60)) — @Jemadiar1
- Catalog(focus): pin sha 746abb8 with reasoning truncation resilience ([`ce996a62`](https://github.com/NousResearch/hermes-agent/commit/ce996a62fbe4e064d6d7063c958ca8ef6a0e159c)) — @Jemadiar1
- Pin sieve to the private-by-default build (9d9ca4c) ([`a8251b55`](https://github.com/NousResearch/hermes-agent/commit/a8251b552c8004afed06238cfa18e376cd39cfbc)) — @VGFreakXBL
- Pin sieve to the honest push-gate reason build ([`18d2aa6e`](https://github.com/NousResearch/hermes-agent/commit/18d2aa6eb2be2e868ac3ffa06b6f6af965e4ec9d)) — @VGFreakXBL
- Pin sieve to the build with its matrix gallery shot ([`53698f3f`](https://github.com/NousResearch/hermes-agent/commit/53698f3fb45d4560d6abe9cf3559c89d720850fd)) — @VGFreakXBL
- Catalog: re-pin preflight to 53d5c40 (review ronda 3) ([`ce239153`](https://github.com/NousResearch/hermes-agent/commit/ce239153efe8dc576a1898935fc054c077ef6a54)) — @soyluisarca
- Core: re-pin preflight sha e1ce0c0 (F1 legible review, 52 PASS) ([`606fbf2b`](https://github.com/NousResearch/hermes-agent/commit/606fbf2b316af7bfad693f853c5393b3ab257ed7)) — @soyluisarca
- Core: re-pin preflight sha 569fd6b (security hardening rondas 4-6) ([`05609620`](https://github.com/NousResearch/hermes-agent/commit/05609620bd9904d603676ff1575f22fc5eddb93a)) — @soyluisarca
- Preflight: re-pin sha to 655440f (rounds 1-3 fixes, 36/36 PASS) ([`01d7bfca`](https://github.com/NousResearch/hermes-agent/commit/01d7bfca02d0077dea89a2621c35fdf6d2ffdca8)) — @soyluisarca
- Preflight: pin to 2840289 (final docs) ([`f821857a`](https://github.com/NousResearch/hermes-agent/commit/f821857a53cc1638bc3356d8f1072ba6ab025c7d)) — @soyluisarca
- Preflight: pin to 6a22c00 (hardening) + english description ([`1a93b804`](https://github.com/NousResearch/hermes-agent/commit/1a93b804956fb7f39a39c27a6e13207b1f71845c)) — @soyluisarca
- Catalog: preflight — final pin a12aa573874c6d322f59d66b68bade3cee6f7082 ([`544eb999`](https://github.com/NousResearch/hermes-agent/commit/544eb999daa772262b954c3058c2a8e622ea7d86)) — @soyluisarca
- Catalog: preflight — bump pin to 1d9b19d (apply --yes fix) ([`d733c75c`](https://github.com/NousResearch/hermes-agent/commit/d733c75c930878e3a8706cc30c3a1f89da41c9f0)) — @soyluisarca
- Plugin-catalog: pin hermetic 1.6.0 to 06a3fca ([`d5d9db20`](https://github.com/NousResearch/hermes-agent/commit/d5d9db2088f099b42a044a0fa76ccf646fa0ad53)) — @forefy
- Plugin-catalog: bump hermetic to 1.5.0 ([`24cb5713`](https://github.com/NousResearch/hermes-agent/commit/24cb5713972ed911fc12c66cb9ee6f4a8cb7c520)) — @forefy
- Callit: pin 0510902 (review fixes) ([`a187665c`](https://github.com/NousResearch/hermes-agent/commit/a187665c28af9b093eb1c2aaf5029d841a323987)) — @k58v2hbzkk-del
- Callit: pin f8893c6ab03b70a0ed6899bc8028e8b4045b94c9 ([`c695ee85`](https://github.com/NousResearch/hermes-agent/commit/c695ee859c0033a0796c187f81ad18e991abc9e7)) — @claude
- Re-pin harness2 catalog entry to ab03ab8 (delegation leaf allowlist) ([`94c85ca1`](https://github.com/NousResearch/hermes-agent/commit/94c85ca1de2a765a2f531869000e66a825512180)) — @shrinedogg
- Re-pin harness2 catalog entry to 0000b1b (overlay allowlist fix) ([`b5925700`](https://github.com/NousResearch/hermes-agent/commit/b5925700ef003187e3958d2c751861b227abee3c)) — @shrinedogg
- Harness2 catalog: plain-English description ([`2c120d5f`](https://github.com/NousResearch/hermes-agent/commit/2c120d5fc210f424f024301099bef6105081313c)) — @shrinedogg
- Probe: verify token write scope (throwaway file) ([`8055adcd`](https://github.com/NousResearch/hermes-agent/commit/8055adcd3564b5899cd84fa82d976b9fae79dacf)) — @shrinedogg
- Plugin-catalog: re-pin harness2 to 1e26638 (README rewrite) ([`41fa31a1`](https://github.com/NousResearch/hermes-agent/commit/41fa31a1927a39565b142cbc80b9b56416238c20)) — @shrinedogg
- Plugin-catalog: bump opendockit to 0.3.11 ([`2843d6e0`](https://github.com/NousResearch/hermes-agent/commit/2843d6e0d82e4881a4c9845a517b0712036d1f0e)) — @hyeonsang010716
- Plugin-catalog: bump opendockit to 0.3.10 ([`e09fbbd1`](https://github.com/NousResearch/hermes-agent/commit/e09fbbd159da17c0823b68c6da3d6f286cbcc79a)) — @hyeonsang010716

## 👥 Contributors

Thank you to everyone who contributed to this release!

- @BearHuddleston (30 commits)
- @nsolland (15 commits)
- @tesla963 (12 commits)
- @YAN-XBT (11 commits)
- @c2h5oh (9 commits)
- @RajaRenga (9 commits)
- @soyluisarca (9 commits)
- @meeting-ai (8 commits)
- @Thaeland (8 commits)
- @itpartypattaya (7 commits)
- @Jemadiar1 (7 commits)
- @shrinedogg (7 commits)
- @while-sh (6 commits)
- @100yenadmin (5 commits)
- @Adolanium (5 commits)
- @unsupportedpastels (4 commits)
- @kshitijk4poor (4 commits)
- @Pukujan (4 commits)
- @anpicasso (4 commits)
- @Murali-lns (4 commits)
- @Ratz00007 (4 commits)
- @aadilghani1 (3 commits)
- @xraysight (3 commits)
- @AbigailDavised (3 commits)
- @alessandromoretti90 (3 commits)
- @aldemaroc (3 commits)
- @seanflynnfilm (3 commits)
- @arspesk (3 commits)
- @KOnaitis (3 commits)
- @abundantbeing (3 commits)
- @VGFreakXBL (3 commits)
- @otsoa-dubief (2 commits)
- @D0xedDevi0 (2 commits)
- @Sandeep85Das (2 commits)
- @akinfold (2 commits)
- @soyelmismo (2 commits)
- @lazyants (2 commits)
- @0sahil (2 commits)
- @ntsd (2 commits)
- @Kame696 (2 commits)
- @morajabi (2 commits)
- @soymarketing (2 commits)
- @rodricksz4h5 (2 commits)
- @TakeshiTGAL (2 commits)
- @flabanabba8 (2 commits)
- @tiptophelmet (2 commits)
- @godzillacode0000 (2 commits)
- @mr-pewpy (2 commits)
- @kvnloo (2 commits)
- @hajimemanila (2 commits)
- @blavenie (2 commits)
- @nicolasdmolina (2 commits)
- @TheBlueHouse75 (2 commits)
- @forefy (2 commits)
- @hyeonsang010716 (2 commits)
- @andyylin (2 commits)
- @Likivik (1 commit)
- @emozilla (1 commit)
- @erosika (1 commit)
- @Kesuek (1 commit)
- @OutThisLife (1 commit)
- @dawidope (1 commit)
- @Im5tu (1 commit)
- @Fiction000 (1 commit)
- @hi4c0ck (1 commit)
- @BrokeSkill (1 commit)
- @hendkai (1 commit)
- @xuhuawork (1 commit)
- @sesantanajr (1 commit)
- @jacobhausler (1 commit)
- @KosmGit (1 commit)
- @sicruse (1 commit)
- @divyasshree-BQ (1 commit)
- @RudiFreeman (1 commit)
- @tradersurfer (1 commit)
- @optiq-bot (1 commit)
- @hlplanet (1 commit)
- @chrisjleal (1 commit)
- @yzy806806 (1 commit)
- @EmotionalThrifty (1 commit)
- @gerdosi (1 commit)
- @priyankarpal (1 commit)
- @promptli-dev (1 commit)
- @ANAMASGARD (1 commit)
- @pswong661-eng (1 commit)
- @obkaro (1 commit)
- @Cyb3rb1ade (1 commit)
- @mu1ze (1 commit)
- @LangerSword (1 commit)
- @Angerosteles (1 commit)
- @blackopsrepl (1 commit)
- @W4-NERF (1 commit)
- @user1303836 (1 commit)
- @smallmj (1 commit)
- @ElSerda (1 commit)
- @riceharvest (1 commit)
- @yusupsupriyadi (1 commit)
- @madsb (1 commit)
- @Freeman-Consulting (1 commit)
- @memtomem (1 commit)
- @YLChen-007 (1 commit)
- @jaedmunt (1 commit)
- @TarasShyn (1 commit)
- @Cam-AcitveIce (1 commit)
- @xMannixx (1 commit)
- @Novada-proxy (1 commit)
- @pugarte7 (1 commit)
- @Mandark-droid (1 commit)
- @Jessy-Boo (1 commit)
- @clance1 (1 commit)
- @ShawnCRMer (1 commit)
- @aisenseapi (1 commit)
- @drvt69talati (1 commit)
- @d8joseph (1 commit)
- @sohhamm (1 commit)
- @hendrykcosta75 (1 commit)
- @telnetaisha (1 commit)
- @jnorthrup (1 commit)
- @willbohn (1 commit)
- @blacksmithFF (1 commit)
- @Gaijin-01 (1 commit)
- @tomekdot (1 commit)
- @36North (1 commit)
- @niyonx (1 commit)
- @evgolsh (1 commit)
- @rahlquist (1 commit)
- @Neboy72 (1 commit)
- @jovijovi (1 commit)
- @armanmamyan (1 commit)
- @dbitzas (1 commit)
- @Kattegat-crew (1 commit)
- @k58v2hbzkk-del (1 commit)
- @claude (1 commit)
- @antoinersx (1 commit)
- @33hodl (1 commit)
- @ychampion (1 commit)
- Paul Hill (1 commit)
- @kwchia (1 commit)
- @whyyagswhy (1 commit)
- @demianad (1 commit)
- @yashiels (1 commit)

**Full Changelog**: [v0.23.2+canary.20261119T064637Z...v0.23.3+canary.20261120T064609Z](https://github.com/NousResearch/hermes-agent/compare/v0.23.2+canary.20261119T064637Z...v0.23.3+canary.20261120T064609Z)</content>
    <ore:provenance>
      <ore:sourceId>hermes-agent-releases</ore:sourceId>
      <ore:sourceName>Hermes Agent GitHub Releases</ore:sourceName>
      <ore:sourceType>github_releases</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://github.com/NousResearch/hermes-agent/releases</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://api.github.com/repos/NousResearch/hermes-agent/releases</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://github.com/NousResearch/hermes-agent/releases/tag/v0.23.3%2Bcanary.20261120T064609Z</ore:originalUrl>
      <ore:upstreamId>RE_kwDOPRF1G84a9mkY</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hatena-bookmark-technology:826555ccc6a929aba1d6575f40a3101f</id>
    <title>国産AIノエトラ支援、半導体高騰で8000億円膨張　国の負担重く - 日本経済新聞</title>
    <updated>2026-11-20T07:33:21Z</updated>
    <published>2026-11-20T07:33:21Z</published>
    <link rel="alternate" href="https://www.nikkei.com/article/DGXZQOUA164VE0W6A111C2000000/" />
    <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    <category scheme="urn:ore-news:sources" term="hatena-bookmark-technology" label="Hatena Bookmark Technology" />
    <author>
      <name>Hatena Bookmark Technology</name>
    </author>
    <source>
      <id>urn:ore-news:source:hatena-bookmark-technology</id>
      <title>Hatena Bookmark Technology</title>
      <link rel="alternate" href="https://b.hatena.ne.jp/hotentry/it" />
      <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hatena-bookmark-technology</ore:sourceId>
      <ore:sourceName>Hatena Bookmark Technology</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://b.hatena.ne.jp/hotentry/it</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://b.hatena.ne.jp/hotentry/it.rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://www.nikkei.com/article/DGXZQOUA164VE0W6A111C2000000/</ore:originalUrl>
      <ore:upstreamId>https://www.nikkei.com/article/DGXZQOUA164VE0W6A111C2000000/</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hatena-bookmark-technology:94b809d75c5bb77a9995d97e429251c3</id>
    <title>メモリ圧縮を使えばCPUの処理能力を少し犠牲にするだけでメモリ使用量を大幅に削減できる</title>
    <updated>2026-11-20T06:24:44Z</updated>
    <published>2026-11-20T06:24:44Z</published>
    <link rel="alternate" href="https://gigazine.net/news/20261120-memory-compress/" />
    <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    <category scheme="urn:ore-news:sources" term="hatena-bookmark-technology" label="Hatena Bookmark Technology" />
    <author>
      <name>Hatena Bookmark Technology</name>
    </author>
    <source>
      <id>urn:ore-news:source:hatena-bookmark-technology</id>
      <title>Hatena Bookmark Technology</title>
      <link rel="alternate" href="https://b.hatena.ne.jp/hotentry/it" />
      <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hatena-bookmark-technology</ore:sourceId>
      <ore:sourceName>Hatena Bookmark Technology</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://b.hatena.ne.jp/hotentry/it</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://b.hatena.ne.jp/hotentry/it.rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://gigazine.net/news/20261120-memory-compress/</ore:originalUrl>
      <ore:upstreamId>https://gigazine.net/news/20261120-memory-compress/</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:8442fb0e3aead0ff8553375c5d308b93</id>
    <title>Amazon FSx for NetApp ONTAP launches a new generation of file systems with up to 3.6x higher performance</title>
    <updated>2026-11-20T05:00:00Z</updated>
    <published>2026-11-20T05:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/amazon-fsx-for-netapp-ontap-third-generation/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;Today, we're announcing third-generation Amazon FSx for NetApp ONTAP file systems, which deliver up to 216 GB/s of throughput and 8.6 million SSD IOPS per file system, up to 3x more throughput and up to 3.6x more SSD IOPS than previous-generation file systems. Built on the latest AWS compute and storage technologies, third-generation file systems give you even more flexibility to scale performance as your workloads and usage patterns evolve.&lt;/p&gt; 
&lt;p&gt;FSx for ONTAP is the first and only storage service that allows you to launch and run fully managed, fully featured ONTAP file systems in the cloud. FSx for ONTAP file systems are powered by up to 12 highly available (HA) pairs of file servers to deliver storage and performance scalability.&amp;nbsp;With previous-generation file systems, each HA pair delivers up to 6 GB/s of throughput and 200,000 SSD IOPS. With third-generation file systems, each HA pair delivers up to 18 GB/s of throughput and 720,000 SSD IOPS, giving you even more flexibility to scale your most demanding ONTAP workloads, such as chip design and verification, media rendering and video editing, and mission-critical databases.&lt;/p&gt; 
&lt;p&gt;FSx for ONTAP third-generation file systems are available today in the following AWS Regions: US East (N. Virginia, Ohio) and US West (Oregon). To learn more, visit the &lt;a href="https://aws.amazon.com/fsx/netapp-ontap/"&gt;Amazon FSx for NetApp ONTAP product page&lt;/a&gt; and &lt;a href="https://docs.aws.amazon.com/fsx/latest/ONTAPGuide/what-is-fsx-ontap.html"&gt;user guide&lt;/a&gt;.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/amazon-fsx-for-netapp-ontap-third-generation/</ore:originalUrl>
      <ore:upstreamId>4f3ce89748d2819ec2015b6952b6189e2a134e70</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hatena-bookmark-technology:62360267e14946bc5f8ac6d549dcfbc4</id>
    <title>MetaのAIアシスタント搭載小型デバイス「Muse Charm」の価格は4万円台か</title>
    <updated>2026-11-20T04:45:14Z</updated>
    <published>2026-11-20T04:45:14Z</published>
    <link rel="alternate" href="https://gigazine.net/news/20261120-muse-charm-may-cost-300-usd/" />
    <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    <category scheme="urn:ore-news:sources" term="hatena-bookmark-technology" label="Hatena Bookmark Technology" />
    <author>
      <name>Hatena Bookmark Technology</name>
    </author>
    <source>
      <id>urn:ore-news:source:hatena-bookmark-technology</id>
      <title>Hatena Bookmark Technology</title>
      <link rel="alternate" href="https://b.hatena.ne.jp/hotentry/it" />
      <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hatena-bookmark-technology</ore:sourceId>
      <ore:sourceName>Hatena Bookmark Technology</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://b.hatena.ne.jp/hotentry/it</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://b.hatena.ne.jp/hotentry/it.rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://gigazine.net/news/20261120-muse-charm-may-cost-300-usd/</ore:originalUrl>
      <ore:upstreamId>https://gigazine.net/news/20261120-muse-charm-may-cost-300-usd/</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hatena-bookmark-technology:453df97fb0b57c280fce3ddd6cbaf1d8</id>
    <title>QRコードに「Webアプリ丸ごと」を圧縮して焼き込む狂気。サーバー代0円で一生消えない「紙の資格試験カートリッジ」を妄想してみた｜ぬこやぽち┃キャリアコンサルタント</title>
    <updated>2026-11-20T04:20:14Z</updated>
    <published>2026-11-20T04:20:14Z</published>
    <link rel="alternate" href="https://note.com/nukoya_pochi/n/n889b2db947e4" />
    <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    <category scheme="urn:ore-news:sources" term="hatena-bookmark-technology" label="Hatena Bookmark Technology" />
    <author>
      <name>Hatena Bookmark Technology</name>
    </author>
    <source>
      <id>urn:ore-news:source:hatena-bookmark-technology</id>
      <title>Hatena Bookmark Technology</title>
      <link rel="alternate" href="https://b.hatena.ne.jp/hotentry/it" />
      <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hatena-bookmark-technology</ore:sourceId>
      <ore:sourceName>Hatena Bookmark Technology</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://b.hatena.ne.jp/hotentry/it</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://b.hatena.ne.jp/hotentry/it.rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://note.com/nukoya_pochi/n/n889b2db947e4</ore:originalUrl>
      <ore:upstreamId>https://note.com/nukoya_pochi/n/n889b2db947e4</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:cloudflare-blog:6187951253b0c8e91cabf55a1edf9b96</id>
    <title>nginx2root: Five new nginx vulnerabilities, and how Cloudflare protects origins from the worst of them</title>
    <updated>2026-11-20T01:58:29Z</updated>
    <published>2026-11-20T01:58:29Z</published>
    <link rel="alternate" href="https://blog.cloudflare.com/nginx2root/" />
    <link rel="via" href="https://blog.cloudflare.com/rss/" />
    <category scheme="urn:ore-news:sources" term="cloudflare-blog" label="Cloudflare Blog" />
    <author>
      <name>Cloudflare Blog</name>
    </author>
    <source>
      <id>urn:ore-news:source:cloudflare-blog</id>
      <title>Cloudflare Blog</title>
      <link rel="alternate" href="https://blog.cloudflare.com/" />
      <link rel="via" href="https://blog.cloudflare.com/rss/" />
    </source>
    <content type="html">&lt;p&gt;On November 18, 2026, F5 and nginx.org disclosed ten vulnerabilities in nginx. Five of them, detailed by the Xint research team and published under the name &lt;strong&gt;nginx2root&lt;/strong&gt;, are memory corruption flaws that an unauthenticated attacker can use to crash an nginx worker or, per Xint&amp;#x27;s research, run commands on the server. Xint also found a Linux kernel bug that turns that foothold into root on the host, including from inside a Docker container. Other teams found the two HTTP/2 bugs independently: F5 also credits Rapid7, Wiz Research and Ikotas Labs for CVE-2026-123007, and Metnir, Wiz Research, and Palo Alto Networks Unit 42 for CVE-2026-123633.&lt;/p&gt;&lt;p&gt;nginx is an HTTP web server that also serves as reverse proxy, content cache, load balancer, TCP/UDP proxy server, and mail proxy server. nginx runs a large share of the world&amp;#x27;s web servers, so this is a patch-now event. But if your nginx server is reachable only through Cloudflare&amp;#x27;s proxy, attackers cannot reach the vulnerable code paths for the most serious of these bugs, giving you protection while you update your servers.&lt;/p&gt;&lt;p&gt;Here is where Cloudflare stands, what that protection covers, where it stops, and how the bugs work.&lt;/p&gt;&lt;h2&gt;The short version&lt;/h2&gt;&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Cloudflare&amp;#x27;s edge is not affected.&lt;/strong&gt; Much of the proxy that handles customer traffic at our edge now runs on FL2, written in Rust. We reviewed the parts still built on our heavily modified nginx fork against all five bugs before disclosure, and an update closing the related code paths finished rolling out globally before the vulnerabilities were published. The same releases fix five other nginx CVEs, including CVE-2026-118899, an infinite loop while reading a request body over TLS 1.3.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Origins behind Cloudflare&amp;#x27;s HTTP proxy are shielded from the HTTP/2 and HTTP/3 attacks.&lt;/strong&gt; For proxied hostnames, Cloudflare terminates every client HTTP/2 and HTTP/3 connection at our edge and opens a separate connection to your origin. The attacker&amp;#x27;s frames never reach your nginx.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;The resolver and mail proxy vulnerabilities depend on specific configuration.&lt;/strong&gt; Many configurations of nginx will not be vulnerable, but the safest way to be sure is to update your install or disable features.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;You should still patch.&lt;/strong&gt; Update to nginx 1.30.7 or 1.31.9 (or your vendor&amp;#x27;s fixed build) and restart. Some configurations, covered below, are not protected by the proxy.&lt;/li&gt;&lt;/ul&gt;&lt;h2&gt;What was disclosed&lt;/h2&gt;&lt;p&gt;nginx2root is five independent bugs. Each one works on its own and each one needs a different configuration.&lt;/p&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;CVE&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;Bug class&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;Affected configuration&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;First affected release&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;CVE-2026-123007&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Integer overflow leading to out-of-bounds heap read/write&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;HTTP/2 enabled&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;1.9.5 (2015)&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;CVE-2026-123633&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Use-after-free&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;HTTP/2 with &lt;code&gt;proxy_pass&lt;/code&gt; to a backend, worker low on &lt;code&gt;worker_connections&lt;/code&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;1.19.7&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;CVE-2026-121810&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Use-after-free&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;HTTP/3 (QUIC) with &lt;code&gt;proxy_pass&lt;/code&gt; to a backend&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;1.25.0&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;CVE-2026-123634&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Use-after-free&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;&lt;code&gt;resolver&lt;/code&gt; + &lt;code&gt;proxy_pass&lt;/code&gt; with variables + a subrequest (&lt;code&gt;mirror&lt;/code&gt; or SSI)&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;0.6.18&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;CVE-2026-113425&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Use-after-free&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Mail proxy with &lt;code&gt;proxy on&lt;/code&gt; and &lt;code&gt;auth_http&lt;/code&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;0.5.33&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;F5 rates each one High (CVSS 3.1: 8.1) and Critical (CVSS 4.0: 9.2), and notes that code execution requires disabling or bypassing &lt;a href="https://en.wikipedia.org/wiki/Address_space_layout_randomization"&gt;&lt;span style="text-decoration:underline"&gt;ASLR&lt;/span&gt;&lt;/a&gt; (Address Space Layout Randomization). For CVE-2026-123007, Xint&amp;#x27;s write-up shows how it leaked memory addresses to do exactly that.&lt;/p&gt;&lt;p&gt;CVE-2026-123007 is the one to worry about most. It only needs HTTP/2 turned on, which is commonly enabled on TLS deployments, and it has been in every nginx release since HTTP/2 support shipped in 1.9.5. Xint ran the exploit over the public Internet against servers on AWS, GCP and Azure. Xint searched Shodan on November 10, before the disclosure, and found 56.7 million hosts matching &lt;code&gt;product:nginx&lt;/code&gt;. Of the 11.94 million that reported a version, 98.9% fell in the affected range. As of November 19, Censys&amp;#x27;s &lt;a href="https://nginx2root.censys.com/"&gt;&lt;span style="text-decoration:underline"&gt;nginx2root exposure tracker&lt;/span&gt;&lt;/a&gt; counts about 8.8 million services running a potentially affected version with HTTP/2 enabled. Version strings don&amp;#x27;t prove a host is vulnerable, since distributions backport fixes, but the exposure is large.&lt;/p&gt;&lt;p&gt;The same nginx releases also fix five other bugs. The most serious, CVE-2026-118899, is an infinite loop when reading a request body over TLS 1.3 that lets an unauthenticated attacker stall a worker, in nginx 1.13.0 and later.&lt;/p&gt;&lt;p&gt;The Linux kernel bug is the sixth part of nginx2root. Xint found a use-after-free in the kernel&amp;#x27;s SCTP send path, present since Linux 4.15 (2018): while a send operation waits, its SCTP association can be moved to another socket, and the waiting send can then free it. An attacker who already runs code as the nginx worker can use it to gain root on the host, and Xint did this from an nginx running inside a Docker container. Many distributions load the SCTP module automatically the first time a program opens an SCTP socket, so hosts that never use SCTP can still be exposed. As of November 18, no kernel fix was available and Xint was withholding the details until there is one.&lt;/p&gt;&lt;p&gt;As of November 19, none of the five nginx2root CVEs is in CISA&amp;#x27;s Known Exploited Vulnerabilities catalog, and we have not seen reports of exploitation in the wild. Xint and Wiz Research have not released their exploits. Rapid7 has published a proof of concept, which it describes as suitable only for demonstrating the attack against a freshly started local container. Fake &amp;#x27;exploits&amp;#x27; are also circulating on GitHub.&lt;/p&gt;&lt;h2&gt;Why Cloudflare&amp;#x27;s proxy protects your origin&lt;/h2&gt;&lt;p&gt;nginx2root&amp;#x27;s most dangerous bugs live in how nginx parses and manages HTTP/2 and HTTP/3 connections. To trigger them, an attacker has to send a carefully ordered stream of protocol frames directly to the nginx process: billions of &lt;code&gt;WINDOW_UPDATE&lt;/code&gt; frames, a SETTINGS frame that holds response data back, PING frames that fill the send buffers, partial HEADERS frames, &lt;code&gt;RST_STREAM&lt;/code&gt; at exactly the right moment.&lt;/p&gt;&lt;p&gt;When your DNS record is proxied through Cloudflare, that connection ends at our edge.&lt;/p&gt;&lt;!-- unsupported block: image --&gt;&lt;p&gt;Cloudflare reads the client&amp;#x27;s HTTP request, applies your security and caching rules, and then makes its own request to your origin over a connection Cloudflare controls. The flow-control frames, pings, settings, and stream resets that the attacker sends are consumed by our edge. They are not forwarded. Your nginx only ever sees the requests Cloudflare chooses to send, framed the way Cloudflare frames them. This also holds when Cloudflare connects to your origin over HTTP/2: Cloudflare runs its own flow control on that connection and sends &lt;code&gt;WINDOW_UPDATE&lt;/code&gt; and &lt;code&gt;RST_STREAM&lt;/code&gt; frames only as its own traffic needs, so a client can&amp;#x27;t make it relay the billions of &lt;code&gt;WINDOW_UPDATE&lt;/code&gt; frames the attack requires.&lt;/p&gt;&lt;p&gt;Rapid7 makes the same point in its analysis of CVE-2026-123007: if the HTTP/2 connection is proxied, the attacker&amp;#x27;s frames &amp;quot;will likely not be retransmitted&amp;quot; in a way that allows exploitation. This breaks each of the HTTP/2 and HTTP/3 attacks.&lt;/p&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;CVE&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;What the attacker needs&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;Behind Cloudflare&amp;#x27;s HTTP proxy&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;CVE-2026-123007&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Direct control over HTTP/2 &lt;code&gt;WINDOW_UPDATE&lt;/code&gt;, &lt;code&gt;SETTINGS&lt;/code&gt;, &lt;code&gt;PING&lt;/code&gt; and &lt;code&gt;RST_STREAM&lt;/code&gt; on one connection to nginx&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Protected. Control frames terminate at Cloudflare&amp;#x27;s edge.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;CVE-2026-123633&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;The first part of a HEADERS frame on a direct HTTP/2 connection, plus the ability to exhaust nginx connection slots and reset the TCP connection&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Protected. The client&amp;#x27;s HTTP/2 connection terminates at Cloudflare.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;CVE-2026-121810&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;A direct QUIC/HTTP/3 connection to nginx&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Protected. HTTP/3 terminates at Cloudflare&amp;#x27;s edge. We do not communicate to origins over HTTP/3&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;CVE-2026-123634&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;A request and its mirror or SSI subrequest waiting on the same DNS lookup, and the main request ending while the answer is processed. In Xint&amp;#x27;s exploit, nginx&amp;#x27;s resolver had to reach the attacker&amp;#x27;s DNS server.&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Not fully protected. Depends on how your config builds &lt;code&gt;proxy_pass&lt;/code&gt;. Patch.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;CVE-2026-113425&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;A direct IMAP/POP3/SMTP connection to the nginx mail proxy&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Not protected. Cloudflare&amp;#x27;s HTTP proxy does not carry mail traffic.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;There is one condition to be protected by Cloudflare here: &lt;strong&gt;your origin must not be reachable directly.&lt;/strong&gt; If an attacker can find your origin&amp;#x27;s IP and connect to it directly (TCP 443 or 80 for HTTP/2, UDP 443 for HTTP/3, or the mail ports), Cloudflare isn&amp;#x27;t in the path and the protection doesn&amp;#x27;t apply. You should ensure that your origin servers can only be accessed through Cloudflare’s proxies, using one of the following approaches:&lt;/p&gt;&lt;ul&gt;&lt;li&gt;&lt;strong&gt;&lt;a href="https://developers.cloudflare.com/tunnel/"&gt;&lt;span style="text-decoration:underline"&gt;Cloudflare Tunnel&lt;/span&gt;&lt;/a&gt;.&lt;/strong&gt; Your origin makes an outbound-only connection to Cloudflare and exposes no inbound ports.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Firewall to Cloudflare IP ranges.&lt;/strong&gt; Accept inbound HTTP/HTTPS only from &lt;a href="https://www.cloudflare.com/ips/"&gt;&lt;span style="text-decoration:underline"&gt;Cloudflare&amp;#x27;s published IP ranges&lt;/span&gt;&lt;/a&gt;. This must be done using an IP firewall, not based on configuration in your nginx server.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;&lt;a href="https://developers.cloudflare.com/ssl/origin-configuration/authenticated-origin-pull/"&gt;&lt;span style="text-decoration:underline"&gt;Authenticated Origin Pulls&lt;/span&gt;&lt;/a&gt; (mTLS).&lt;/strong&gt; Your origin rejects any TLS connection that doesn&amp;#x27;t present Cloudflare&amp;#x27;s client certificate.&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;Xint&amp;#x27;s own exposure check makes the same point: &amp;quot;If a CDN or reverse proxy sits in front of nginx, the test only reaches the proxy, so also run it directly against the nginx server.&amp;quot;&lt;/p&gt;&lt;h3&gt;Where the protection does not apply&lt;/h3&gt;&lt;p&gt;There are several situations in which Cloudflare’s HTTP proxy does not provide protection.&lt;/p&gt;&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Spectrum TCP/UDP applications.&lt;/strong&gt; For these configurations, traffic from the Internet is passed unmodified through to your origin. If your origin is running nginx, patch or disable the affected features.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;nginx mail proxy.&lt;/strong&gt; Cloudflare&amp;#x27;s HTTP proxy does not carry IMAP, POP3 or SMTP. Restrict mail listeners to trusted networks until patched.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;CVE-2026-123634 (resolver).&lt;/strong&gt; This depends on how your configuration builds the &lt;code&gt;proxy_pass&lt;/code&gt; target from the request, combined with a carefully timed cancellation of an HTTP request. Passing your traffic through Cloudflare’s proxy makes it harder to exploit this, but does not provide full protection. Update regardless.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;DNS-only (grey-cloud), internal or non-proxied nginx.&lt;/strong&gt; Any nginx server an attacker can reach without going through Cloudflare, including internal services behind a compromised host, needs to be patched.&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;&lt;strong&gt;Cloudflare’s WAF rules are not relevant to these vulnerabilities.&lt;/strong&gt; These are protocol-level bugs. Because Cloudflare’s proxy handles parsing the HTTP protocol messages, and creates new messages to fetch information from origin servers, origins behind Cloudflare&amp;#x27;s HTTP proxy are protected from the HTTP/2 and HTTP/3 bugs without needing a rule. We have therefore not released a managed rule. The protection comes from connection termination, not from pattern matching.&lt;/p&gt;&lt;h2&gt;What to do now&lt;/h2&gt;&lt;ol&gt;&lt;li&gt;&lt;strong&gt;Find every nginx server.&lt;/strong&gt; Include nginx Plus, distribution packages, container images and appliances. Run &lt;code&gt;nginx -V&lt;/code&gt; and &lt;code&gt;nginx -T&lt;/code&gt; on each and note HTTP/2, HTTP/3/QUIC listeners, &lt;code&gt;proxy_pass&lt;/code&gt; with variables plus SSI or &lt;code&gt;mirror&lt;/code&gt;, and any &lt;code&gt;mail&lt;/code&gt; block.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Patch.&lt;/strong&gt; Update nginx Open Source to 1.30.7 or 1.31.9, nginx Plus to 37.0.8.1 or 37.3.0.1, or your distribution&amp;#x27;s fixed package. F5 lists nginx Plus R34 to R36 as affected with no fixed build, so move those to a fixed 37.x release. Then &lt;strong&gt;restart&lt;/strong&gt; nginx or complete a binary upgrade. A config reload does not replace the running binary.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Check backport versions carefully.&lt;/strong&gt; Distributions often patch without changing the version &lt;code&gt;nginx -v&lt;/code&gt; reports. Compare the full package version against your distribution&amp;#x27;s advisory.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Make sure your origin is only reachable through Cloudflare.&lt;/strong&gt; Use Tunnel, IP allowlisting or Authenticated Origin Pulls.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;If you can&amp;#x27;t patch yet, disable what you don&amp;#x27;t need.&lt;/strong&gt; &lt;code&gt;http2 off;&lt;/code&gt; (nginx 1.25.1 and later; on older versions, remove &lt;code&gt;http2&lt;/code&gt; from the &lt;code&gt;listen&lt;/code&gt; directive) blocks CVE-2026-123007 and CVE-2026-123633. Removing QUIC listeners and setting &lt;code&gt;http3 off;&lt;/code&gt; blocks CVE-2026-121810. Point &lt;code&gt;proxy_pass&lt;/code&gt; at fixed upstream groups for CVE-2026-123634. Don&amp;#x27;t rely on &lt;code&gt;mirror_request_body&lt;/code&gt; alone: Xint&amp;#x27;s tested setup set it to &lt;code&gt;off&lt;/code&gt;, and the default &lt;code&gt;on&lt;/code&gt; stopped that exploit, but SSI and other subrequests can still reach the bug. Bind mail listeners to trusted networks for CVE-2026-113425. Restart so old connections close.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Block SCTP if you don&amp;#x27;t use it.&lt;/strong&gt; Add &lt;code&gt;install sctp /bin/false&lt;/code&gt; to a file in &lt;code&gt;/etc/modprobe.d/&lt;/code&gt; to stop the kernel module from loading. This doesn&amp;#x27;t unload an already-loaded module or disable SCTP built into the kernel. When your distribution ships a kernel update for the SCTP bug, install it and reboot. Blocking the module is a stopgap until then.&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;The Cloudflare Radar &lt;a href="https://radar.cloudflare.com/zero-wire/nginx2root"&gt;&lt;span style="text-decoration:underline"&gt;Zero Wire entry for nginx2root&lt;/span&gt;&lt;/a&gt; has the full checklist, a prompt you can give an agent to run a read-only assessment of your fleet, and links to every vendor advisory.&lt;/p&gt;&lt;h2&gt;Technical deep dive&lt;/h2&gt;&lt;p&gt;Let’s dig into the details of the five bugs by looking through the code. We’re looking at nginx 1.31.8 (commit 140aa94) which was the most recent code published before the fixes, and comparing this to the fixes in 1.31.9 (which were also included in release 1.30.7 on the stable branch).&lt;/p&gt;&lt;p&gt;A note on methodology: we based our analysis on the public advisories, and to verify our reading of the code, we built the public 1.31.8 and 1.31.9 releases with AddressSanitizer and ran tests for four of the five bugs (flow control, HTTP/2 use-after-free, resolver and mail proxy). Each one faults on 1.31.8 and runs clean on 1.31.9. We did not reproduce the HTTP/3 bug; that section is based on the fix commit and the published analysis.&lt;/p&gt;&lt;h3&gt;One pattern, in four places&lt;/h3&gt;&lt;p&gt;Four of the five bugs are use-after-free bugs. This is a common issue with programs that manually manage memory without language support: one part of the code frees an object that another part is still using.&lt;/p&gt;&lt;p&gt;nginx is event driven. A handler runs, calls other code, and that code returns to the handler. Three of the bugs occur when the called code tears down the connection or request the handler is working on. In the fourth, a second connection still holds a pointer to the object.&lt;/p&gt;&lt;ul&gt;&lt;li&gt;&lt;strong&gt;CVE-2026-123633 and CVE-2026-121810.&lt;/strong&gt; A request needs a connection slot to reach its upstream. nginx is low on slots, so it closes an idle connection to free one. The connection it chooses is the one the request belongs to.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;CVE-2026-123634.&lt;/strong&gt; A resolver callback ends a request. Cleanup of that request frees a second resolver context that the resolver is about to call next.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;CVE-2026-113425.&lt;/strong&gt; When a write to a mail client fails, the client connection is closed while the connection to the authentication service still points at its session.&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;F5 rates all four as potential code execution if address space layout randomization (ASLR) is disabled or bypassed, and in its tests Xint reports code execution with the privileges of the nginx worker.&lt;/p&gt;&lt;p&gt;The fifth bug, CVE-2026-123007, is of a different kind: an accounting error that becomes a length error. &lt;/p&gt;&lt;h3&gt;CVE-2026-123007: two flow-control pieces that each look correct&lt;/h3&gt;&lt;p&gt;HTTP/2 flow control limits the amount of response data a server may send. nginx tracks a send window for each stream and one for the connection, &lt;code&gt;h2c-&amp;gt;send_window&lt;/code&gt;. The client enlarges a window with a WINDOW_UPDATE frame, and the protocol caps every window at 2^31 − 1.&lt;/p&gt;&lt;p&gt;nginx enforces that cap when a WINDOW_UPDATE arrives (ngx_http_v2_state_window_update()):&lt;/p&gt;&lt;pre&gt;&lt;code class="language-plaintext"&gt;if (window &amp;gt; NGX_HTTP_V2_MAX_WINDOW - h2c-&amp;gt;send_window) {
   /* logs &amp;quot;client violated connection flow control&amp;quot; */
   return ngx_http_v2_connection_error(h2c, NGX_HTTP_V2_FLOW_CTRL_ERROR);
}&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;On its own, this check is correct. But the connection window also grows in a second place. When nginx queues DATA frames for a stream, it subtracts their length from the window. If the stream is canceled before those frames go out, &lt;code&gt;ngx_http_v2_filter_cleanup()&lt;/code&gt; takes them off the queue and returns the credit:&lt;/p&gt;&lt;pre&gt;&lt;code&gt;h2c-&amp;gt;send_window += window;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;Nothing caps this line. As the fix commit describes, if the client enlarges the connection window after the frames are queued and before the stream is terminated, the refund pushes the window past 2^31 − 1.&lt;/p&gt;&lt;p&gt;From that point the first check no longer works. &lt;code&gt;h2c-&amp;gt;send_window&lt;/code&gt; is an unsigned &lt;code&gt;size_t&lt;/code&gt;, so &lt;code&gt;NGX_HTTP_V2_MAX_WINDOW - h2c-&amp;gt;send_window&lt;/code&gt; wraps around to a very large number and every subsequent WINDOW_UPDATE is accepted. The client can then raise the window as far as it wants.&lt;/p&gt;&lt;p&gt;The window is unsigned, but the code that sizes DATA frames compares it as a signed value (&lt;code&gt;ngx_http_v2_send_chain()&lt;/code&gt;):&lt;/p&gt;&lt;pre&gt;&lt;code class="language-plaintext"&gt;if (limit == 0 || limit &amp;gt; (off_t) h2c-&amp;gt;send_window) {
   limit = h2c-&amp;gt;send_window;
}
...
if ((off_t) frame_size &amp;gt; limit) {
   frame_size = (size_t) limit;
}&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;After the window passes 2^63, it is negative as an &lt;code&gt;off_t&lt;/code&gt;. The frame size becomes the window value itself, a number between 2^63 and 2^64, and nginx builds a buffer whose &lt;code&gt;last&lt;/code&gt; pointer lies before its &lt;code&gt;pos&lt;/code&gt; pointer.&lt;/p&gt;&lt;p&gt;Over TLS, that buffer reaches a &lt;code&gt;memcpy()&lt;/code&gt; in &lt;code&gt;ngx_ssl_send_chain()&lt;/code&gt; with that length. Our TLS test stops at that point under AddressSanitizer. Xint&amp;#x27;s write-up explains how, with the window pushed close to 2^64, this turns into a controlled out-of-bounds write and an address leak, and Xint, Rapid7, and Wiz each report code execution from it. This post goes no further than the fault.&lt;/p&gt;&lt;p&gt;Over cleartext HTTP/2, the same invalid buffer follows a different output path. Our cleartext test also faults under AddressSanitizer on 1.31.8 and runs clean on 1.31.9. The public write-ups address the TLS case.&lt;/p&gt;&lt;h4&gt;How much traffic the known attacks require&lt;/h4&gt;&lt;p&gt;The biggest step a WINDOW_UPDATE can take is 2^31 − 1, and a WINDOW_UPDATE frame is 13 bytes. Bringing a 64-bit window near its top therefore requires about 2^33 frames: roughly 8.6 billion frames, or about 112 GB (104 GiB).&lt;/p&gt;&lt;p&gt;Rapid7, which published a proof of concept, gives the same figure and adds that nginx limits control-frame traffic relative to other traffic on the connection, so its run also sends about 15 GiB of other request traffic. Its total comes to approximately 128 GB of HTTP/2 data: about two minutes on a 10 Gbit/s link and about seventeen minutes at 1 Gbit/s. Rapid7 estimates the WINDOW_UPDATE traffic needed to reach 2^63 at about 2^32 frames, or 52 GiB, half of the 104 GiB figure. It also notes that these figures describe its route and are not a proven minimum.&lt;/p&gt;&lt;p&gt;For defenders, this is the useful fact about the bug. At this volume, the known attacks are hard to hide: nginx receives tens of gigabytes from a single client over one long-lived connection and sends little back, much more than the requests in the access log account for.&lt;/p&gt;&lt;h4&gt;Why it was difficult to find&lt;/h4&gt;&lt;p&gt;The refund line has existed in nginx since HTTP/2 support arrived in 1.9.5 in 2015. Two things made it difficult to notice.&lt;/p&gt;&lt;p&gt;First, each piece looks correct on its own. The check on WINDOW_UPDATE is the right check. The refund is the right refund. The bug is that the check relies on an assumption the refund does not preserve.&lt;/p&gt;&lt;p&gt;Second, testing that waits for a crash is very unlikely to reach it, because a crash requires tens of gigabytes of input. The bad state itself can be reached with very little traffic: Censys published a cleartext test that reaches what it calls the corrupted flow-control state with a 5.69 MB capture. A test that asserts &amp;quot;the send window never exceeds its protocol maximum&amp;quot; after every frame would flag the bad state as soon as a test sequence got there. A test that waits for memory corruption would not.&lt;/p&gt;&lt;h4&gt;The fix&lt;/h4&gt;&lt;p&gt;The fix (6 lines added) introduces a counter, &lt;code&gt;h2c-&amp;gt;send_queued&lt;/code&gt;, for DATA that is queued but not yet sent. The WINDOW_UPDATE check now includes those bytes in the window:&lt;/p&gt;&lt;pre&gt;&lt;code&gt;if (window &amp;gt; NGX_HTTP_V2_MAX_WINDOW - h2c-&amp;gt;send_window - h2c-&amp;gt;send_queued) {&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;From the client&amp;#x27;s perspective, queued frames still count toward the window, so the client can no longer refill credit that nginx is about to refund. On a fixed version the attempt is rejected with a flow-control error.&lt;/p&gt;&lt;h3&gt;CVE-2026-123633: where two protections interact&lt;/h3&gt;&lt;p&gt;An nginx worker has a fixed number of connection slots (&lt;code&gt;worker_connections&lt;/code&gt;), which the client and upstream connections share. Since 1.19.2, when free slots run low (1/16 of the total or fewer), &lt;code&gt;ngx_get_connection()&lt;/code&gt; calls &lt;code&gt;ngx_drain_connections()&lt;/code&gt;, which closes connections marked &amp;quot;reusable&amp;quot;: connections with nothing in progress, such as idle keep-alive connections.&lt;/p&gt;&lt;p&gt;This works only if a reusable connection truly has nothing in progress. For HTTP/2 that was not always the case. Two commits landed on the same day in February 2021 and were released together in 1.19.7:&lt;/p&gt;&lt;ul&gt;&lt;li&gt;&amp;quot;HTTP/2: fixed reusing connections with active requests&amp;quot; fixed a case in which a cleartext HTTP/2 connection could remain reusable while it had a request.&lt;/li&gt;&lt;li&gt;&amp;quot;HTTP/2: reuse of connections with incomplete frames&amp;quot; registered a connection as reusable while it waits for the remainder of a partly received frame, so that a client cannot hold slots with partial frames.&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;The second change is the relevant one here. As the fix commit explains, if the remainder of that frame is a HEADERS frame, a stream is created, but the reusable status was not reset until the connection next went idle. The connection then has a request and remains in the reusable queue.&lt;/p&gt;&lt;p&gt;If that request is proxied, nginx requests a slot for the upstream connection. If slots are short, the drain runs inside that call and can choose this same connection. The drain instructs the connection to close and nginx attempts to send GOAWAY. If that send fails, nginx frees the connection and every stream on it. Control then goes back to the upstream code, which continues to use the request it was called for.&lt;/p&gt;&lt;p&gt;Each change made sense on its own. The interaction between them was subtle and stayed unnoticed until this year. F5&amp;#x27;s advisory credits Albert Ebb of Metnir, Nir Ohfeld at Wiz Research, Xint.io and memN0ps of Palo Alto Networks Unit 42; nginx.org&amp;#x27;s changelog credits Albert of Vexera AI.&lt;/p&gt;&lt;h4&gt;The fix&lt;/h4&gt;&lt;p&gt;Two lines added: &lt;code&gt;ngx_http_v2_create_stream()&lt;/code&gt; now calls &lt;code&gt;ngx_reusable_connection(h2c-&amp;gt;connection, 0)&lt;/code&gt;. A connection that has a stream is never reusable, regardless of the state it was in before.&lt;/p&gt;&lt;h3&gt;CVE-2026-121810: the same idea, in QUIC&lt;/h3&gt;&lt;p&gt;According to the fix commit and Xint&amp;#x27;s analysis, the HTTP/3 bug reaches the same result by a different route.&lt;/p&gt;&lt;p&gt;In nginx&amp;#x27;s QUIC code, each QUIC connection uses one connection slot and each stream uses another. A QUIC connection may be drained only when every stream remaining in its tree can be cancelled, and nginx determines this by walking the connection&amp;#x27;s tree of streams.&lt;/p&gt;&lt;p&gt;&lt;code&gt;ngx_quic_create_stream()&lt;/code&gt; removes the QUIC connection from the reusable queue and then requests a slot for the new stream. Before the fix, the new stream was added to the tree only after that. If the slot request triggered a drain that closed another, idle stream of the same QUIC connection, the code handling the closed stream walked the tree, did not find the stream being created, concluded the connection was idle, and made it reusable again. A later drain, for example when the new request connects to its upstream, could then close the QUIC connection while that request was running.&lt;/p&gt;&lt;p&gt;F5&amp;#x27;s advisory states that exploitation &amp;quot;also depends on conditions beyond the attacker&amp;#x27;s control&amp;quot;. Xint writes that the bug &amp;quot;is triggered by a slightly different mechanism&amp;quot; from the HTTP/2 one.&lt;/p&gt;&lt;h4&gt;The fix&lt;/h4&gt;&lt;p&gt;Four lines added: the stream goes into the tree before the slot is requested, and is taken out again on the error paths.&lt;/p&gt;&lt;h3&gt;CVE-2026-123634: freeing the next item of a list during the walk&lt;/h3&gt;&lt;p&gt;When &lt;code&gt;proxy_pass&lt;/code&gt; contains a variable, nginx resolves the host name while handling the request. If a lookup for the same name is already in progress, the new request waits on the same resolver node. When the answer arrives, nginx detaches the list of waiting contexts and calls each in turn:&lt;/p&gt;&lt;pre&gt;&lt;code class="language-plaintext"&gt;next = rn-&amp;gt;waiting;
rn-&amp;gt;waiting = NULL;

while (next) {
   ctx = next;
   ...
   next = ctx-&amp;gt;next;

   ctx-&amp;gt;handler(ctx);
}&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;The loop stores &lt;code&gt;next&lt;/code&gt; before the handler call, so a handler may free its own context. The trouble starts when a handler frees a different context in the same list. This happens when two contexts belong to one request, as with a request and its &lt;code&gt;mirror&lt;/code&gt; subrequest resolving the same name (the case Xint tested; F5 also lists SSI subrequests). If the first handler ends the request, the request&amp;#x27;s cleanup calls &lt;code&gt;ngx_resolve_name_done()&lt;/code&gt; for the second context. That function searches the node&amp;#x27;s waiting list for the context, does not find it because the list has been detached, and frees the context regardless. The loop then advances to the freed context. &lt;/p&gt;&lt;p&gt;Usually nginx logs this. On vulnerable versions, when the search fails, it writes&lt;/p&gt;&lt;pre&gt;&lt;code&gt;could not cancel &amp;lt;name&amp;gt; resolving&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;to the error log at alert level. This line is worth searching for. It is not proof either way: the fix commit notes that one variant, while following a CNAME, produced no alert.&lt;/p&gt;&lt;h4&gt;The fix&lt;/h4&gt;&lt;p&gt;A context cancelled while it sits in a detached list is no longer freed immediately. Its handler is swapped for one that frees it when the loop gets to it (31 lines added). The fix also downgrades the alert to a debug message, so the line above shows up at alert level only on unpatched versions.&lt;/p&gt;&lt;h3&gt;CVE-2026-113425: two connections, one session&lt;/h3&gt;&lt;p&gt;With &lt;code&gt;auth_http&lt;/code&gt;, the mail proxy asks an HTTP service to verify each login. During the wait, it holds two connections for one session: the client connection and the connection to the authentication service. The second points at the session and uses the memory pool of the client connection.&lt;/p&gt;&lt;p&gt;Before the fix, the reply the protocol handler had prepared for the client remained queued while the authentication request was in progress, and the client&amp;#x27;s write handler was still &lt;code&gt;ngx_mail_send()&lt;/code&gt;. If that handler ran and the write failed because the client had reset the connection, it closed the client connection and destroyed the session. The authentication connection still pointed at the session, and the next event on that connection used freed memory.&lt;/p&gt;&lt;p&gt;Xint describes two conditions for this: the client&amp;#x27;s write event must already be registered (for example, because the client stopped reading replies), and the login command and the reset must be handled in the same pass of the event loop. Valid credentials are not needed, because this happens before the login is checked.&lt;/p&gt;&lt;h4&gt;The fix&lt;/h4&gt;&lt;p&gt;Two added lines discard the queued reply when the authentication request begins. The same release contains three further commits that block client writes while the proxy waits for the authentication response, while it connects to the upstream and reads its greeting, and while it resolves an SMTP client&amp;#x27;s address and name.&lt;/p&gt;&lt;h3&gt;What the fixes share&lt;/h3&gt;&lt;p&gt;The five fixes each involve minor corrections to the code. They add between 2 and 31 lines each, and the mail proxy fix came with three further commits. There is no design change needed. Each fix restores an invariant that the rest of the code already depended on:&lt;/p&gt;&lt;ul&gt;&lt;li&gt;a send window never goes above the protocol maximum&lt;/li&gt;&lt;li&gt;a connection with a request in progress is never reusable&lt;/li&gt;&lt;li&gt;an object that other code is about to use is not freed out from under it&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;In every case, one code path failed to keep a rule that the rest of the code relied on, and the fix makes that path keep it. As code is modified over time, it is very easy for these kinds of rules to become broken.&lt;/p&gt;&lt;h3&gt;What to watch for&lt;/h3&gt;&lt;p&gt;Attempts to exploit this will typically trigger some characteristic log messages. Three of these messages (the two at &lt;code&gt;info&lt;/code&gt; and the one at &lt;code&gt;warn&lt;/code&gt;) fall below nginx&amp;#x27;s default &lt;code&gt;error_log&lt;/code&gt; level of &lt;code&gt;error&lt;/code&gt; and appear only if a lower level is set. The &lt;code&gt;alert&lt;/code&gt; messages are logged by default.&lt;/p&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;Bug&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;Log messages or other signals&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;CVE-2026-123007&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;A single long-lived HTTP/2 connection on which nginx receives tens of gigabytes from a client and sends little back, much more than its logged requests account for. On fixed versions a rejected attempt logs &lt;code&gt;client violated connection flow control: received WINDOW_UPDATE frame with window increment ... not allowed for window ...&lt;/code&gt; (level &lt;code&gt;info&lt;/code&gt;; older versions have the same message for ordinary violations). &lt;code&gt;http2 flood detected&lt;/code&gt; (level &lt;code&gt;info&lt;/code&gt;) on such a connection can be a failed attempt, but nginx also logs that message for several other limits.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;CVE-2026-123633, CVE-2026-121810&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;&lt;code&gt;worker process &amp;lt;pid&amp;gt; exited on signal 11&lt;/code&gt; (level &lt;code&gt;alert&lt;/code&gt;) on servers that accept HTTP/2 or HTTP/3 and proxy to an upstream, along with &lt;code&gt;worker_connections are not enough, reusing connections&lt;/code&gt; (level &lt;code&gt;warn&lt;/code&gt;). A use-after-free does not always crash.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;CVE-2026-123634&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;&lt;code&gt;could not cancel &amp;lt;name&amp;gt; resolving&lt;/code&gt; (level &lt;code&gt;alert&lt;/code&gt;, unpatched versions only). The absence of this message does not rule the bug out.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;CVE-2026-113425&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Worker crashes in a mail proxy using &lt;code&gt;auth_http&lt;/code&gt;, with client connections reset during login.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;All five&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Unexpected programs launched by an nginx worker process, for example from an &lt;code&gt;auditd&lt;/code&gt; rule on &lt;code&gt;execve&lt;/code&gt; for the worker&amp;#x27;s user. Xint recommends this check, and it is the strongest sign of a successful attack.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;h2&gt;Timeline&lt;/h2&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;Date (UTC)&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;Event&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;Oct 11, 2026&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Xint discovers the vulnerabilities&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;Oct 16, 2026&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Reported to F5 via HackerOne&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;Oct 27, 2026&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Reports delivered to the nginx development team&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;Nov 10, 2026&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Xint completes patch validation&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;Nov 18, 2026&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Public disclosure; nginx 1.30.7 and 1.31.9 released&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;h2&gt;The bugs will keep coming&lt;/h2&gt;&lt;p&gt;CVE-2026-123007 sat in nginx for more than ten years. The SCTP bug has been in the Linux kernel since 2018. Xint says one of its researchers found CVE-2026-123007 by hand and an automated Xint scan found the other four nginx bugs. Several other teams found the two HTTP/2 bugs independently. Meanwhile, nginx&amp;#x27;s advisory list has gone from two entries in 2025 to 36 so far this year. AI-assisted research is finding bugs in heavily reviewed code faster than before, and more disclosures like this one are coming.&lt;/p&gt;&lt;p&gt;That&amp;#x27;s a large part of why it&amp;#x27;s worth putting Cloudflare in front of your origin. A protocol bug in your web server becomes much less of a risk when the attacker can&amp;#x27;t speak that protocol to your server directly. Our edge is not affected, and the HTTP/2 and HTTP/3 attacks against your nginx end at our network. Patch anyway, lock down your origin so Cloudflare is the only way in, and use the &lt;a href="https://radar.cloudflare.com/zero-wire/nginx2root"&gt;&lt;span style="text-decoration:underline"&gt;Radar Zero Wire page&lt;/span&gt;&lt;/a&gt; to check your fleet.&lt;/p&gt;&lt;h2&gt;Sources&lt;/h2&gt;&lt;ul&gt;&lt;li&gt;&lt;a href="https://radar.cloudflare.com/zero-wire/nginx2root"&gt;&lt;span style="text-decoration:underline"&gt;Cloudflare Radar Zero Wire: nginx2root&lt;/span&gt;&lt;/a&gt;&lt;/li&gt;&lt;li&gt;&lt;a href="https://nginx2root.com/"&gt;&lt;span style="text-decoration:underline"&gt;nginx2root.com&lt;/span&gt;&lt;/a&gt;&lt;/li&gt;&lt;li&gt;&lt;a href="https://xint.io/blog/nginx2root-remote-code-execution"&gt;&lt;span style="text-decoration:underline"&gt;Xint: NGINX2Root technical write-up&lt;/span&gt;&lt;/a&gt;&lt;/li&gt;&lt;li&gt;&lt;a href="https://my.f5.com/manage/s/article/K000164058"&gt;&lt;span style="text-decoration:underline"&gt;F5 advisory index K000164058&lt;/span&gt;&lt;/a&gt;&lt;/li&gt;&lt;li&gt;&lt;a href="https://nginx.org/en/security_advisories.html"&gt;&lt;span style="text-decoration:underline"&gt;nginx security advisories&lt;/span&gt;&lt;/a&gt;&lt;/li&gt;&lt;li&gt;&lt;a href="https://www.rapid7.com/blog/post/ve-cve-2026-123007-critical-nginx-http-2-integer-underflow-leads-to-rce-fixed/"&gt;&lt;span style="text-decoration:underline"&gt;Rapid7: CVE-2026-123007 analysis and proof of concept&lt;/span&gt;&lt;/a&gt;&lt;/li&gt;&lt;li&gt;&lt;a href="https://censys.com/blog/nginx2root-simple-test"&gt;&lt;span style="text-decoration:underline"&gt;Censys: nginx2root simple test&lt;/span&gt;&lt;/a&gt;&lt;/li&gt;&lt;li&gt;&lt;a href="https://www.wiz.io/blog/nginx-http2-rce-vulnerabilities"&gt;&lt;span style="text-decoration:underline"&gt;Wiz: nginx HTTP/2 RCE vulnerabilities&lt;/span&gt;&lt;/a&gt;&lt;/li&gt;&lt;li&gt;&lt;a href="https://nginx2root.censys.com/"&gt;&lt;span style="text-decoration:underline"&gt;Censys: nginx2root exposure tracker&lt;/span&gt;&lt;/a&gt;&lt;/li&gt;&lt;/ul&gt;&lt;h6&gt;&lt;/h6&gt;&lt;p&gt;&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>cloudflare-blog</ore:sourceId>
      <ore:sourceName>Cloudflare Blog</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://blog.cloudflare.com/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://blog.cloudflare.com/rss/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://blog.cloudflare.com/nginx2root/</ore:originalUrl>
      <ore:upstreamId>01M7V6MST3Z48AB8DBH1WGS8EX</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hermes-agent-releases:4712aaca896740e34a884a3c0af5268d</id>
    <title>Hermes Agent v0.23.3</title>
    <updated>2026-11-20T00:34:38Z</updated>
    <published>2026-11-20T00:34:38Z</published>
    <link rel="alternate" href="https://github.com/NousResearch/hermes-agent/releases/tag/v0.23.3" />
    <link rel="via" href="https://api.github.com/repos/NousResearch/hermes-agent/releases" />
    <category scheme="urn:ore-news:sources" term="hermes-agent-releases" label="Hermes Agent GitHub Releases" />
    <author>
      <name>Hermes Agent GitHub Releases</name>
    </author>
    <source>
      <id>urn:ore-news:source:hermes-agent-releases</id>
      <title>Hermes Agent GitHub Releases</title>
      <link rel="alternate" href="https://github.com/NousResearch/hermes-agent/releases" />
      <link rel="via" href="https://api.github.com/repos/NousResearch/hermes-agent/releases" />
    </source>
    <content type="text"># Hermes Agent v0.23.3

**Release Date:** November 19, 2026

&gt; Patch release. This tag rolls up the ~370 PRs merged since v0.23.2 into a stable release for the GitHub release (CLI and installers), the Microsoft Store app, Docker and Hermes Cloud. Full curated notes for this window ship with v0.24.0.

&lt;!-- HERMES_BUILDS_TABLE --&gt;

## About this release

Measured at commit `caafe5389ae`, the window since v0.23.2 contains **1,657 non-merge commits** across **3,948 changed files** (+222,379 / −96,154), **370 merged PRs** and **60 closed issues**.

Also in the window, undocumented here on purpose: one prompt-cache lifecycle controller (warming through long tool runs, compaction of idle chats before the 1h cache expires, Nous Portal on the full 1h lifecycle, `prompt_caching.cache_ttl` defaulting to `auto`), compaction that archives the tool results it drops, the proactive tool-result prune on by default, a one-question first-run CLI setup with the free tier included, GPT-6.2 Astra and Sol (+ Pro) on OpenRouter and Nous Portal, a "Waiting on teammates" strip above Bot Chat composers, the Linux AppImage agent payload run from a stable per-build copy, the storage layer split behind a persistence interface with its SQLite backend, dependency security bumps (oauthlib, opentelemetry, tornado), and a large batch of new plugin-catalog entries.

**Full curated release notes for this window ship with v0.24.0**, which will document everything from v0.23.0 onward — highlights, feature areas, and complete contributor credits. Nothing in this window is skipped.

## Updating

- Microsoft Store app: updates through the Store.
- Desktop app installed from the installer (.exe / .dmg): no change in this release; it updates with the next bundled release.
- CLI: `hermes update`, or re-run the installer one-liner.
- Docker / Hermes Cloud: `nousresearch/hermes-agent:stable` (or `:latest`).

**Full Changelog**: [v0.23.2...v0.23.3](https://github.com/NousResearch/hermes-agent/compare/v0.23.2...v0.23.3)</content>
    <ore:provenance>
      <ore:sourceId>hermes-agent-releases</ore:sourceId>
      <ore:sourceName>Hermes Agent GitHub Releases</ore:sourceName>
      <ore:sourceType>github_releases</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://github.com/NousResearch/hermes-agent/releases</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://api.github.com/repos/NousResearch/hermes-agent/releases</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://github.com/NousResearch/hermes-agent/releases/tag/v0.23.3</ore:originalUrl>
      <ore:upstreamId>RE_kwDOPRF1G84a8F1A</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:32717ffbb3fff7aafe963f9983a1a29b</id>
    <title>AWS DevOps Agent now supports Slack code channels and Microsoft Teams two-way conversations</title>
    <updated>2026-11-19T22:30:00Z</updated>
    <published>2026-11-19T22:30:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/aws-devops-agent-slack-code-channels-teams-two-way/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;AWS DevOps Agent now supports dedicated Slack code channels and two-way conversations in Microsoft Teams, so on-call engineers and DevOps teams can investigate and resolve incidents where they already work together. AWS DevOps Agent investigates incidents across AWS, multicloud, and on-premises environments.&lt;/p&gt; 
&lt;p&gt;Slack code channels give each investigation its own channel. Choose &lt;b&gt;Open in code channel&lt;/b&gt; on an investigation card, and your team and the agent work on the investigation together in that channel. You can ask follow-up questions without @mentioning the agent. If you registered your Slack workspace before this launch, update your Slack permissions to use code channels.&lt;/p&gt; 
&lt;p&gt;For Microsoft Teams, before this launch, users received only one-way notifications from AWS DevOps Agent. Now you can mention AWS DevOps Agent in a connected private or shared channel to ask questions, explore your AWS resources, and steer investigations. The agent replies in a thread under your message. To get started, turn on Bidirectional mode when you associate the channel with your Agent Space. A channel member then authorizes the association before the agent posts.&lt;/p&gt; 
&lt;p&gt;These capabilities are available in all commercial AWS Regions where AWS DevOps Agent is currently supported.&lt;/p&gt; 
&lt;p&gt;To get started, see the following resources:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;p&gt;&lt;a href="https://docs.aws.amazon.com/devopsagent/latest/userguide/connecting-to-ticketing-and-chat-using-slack-code-channels.html"&gt;Using Slack code channels&lt;/a&gt;&lt;/p&gt; &lt;/li&gt; 
 &lt;li&gt;&lt;p&gt;&lt;a href="https://docs.aws.amazon.com/devopsagent/latest/userguide/connecting-to-ticketing-and-chat-connecting-microsoft-teams.html"&gt;Connecting Microsoft Teams&lt;/a&gt;&lt;/p&gt; &lt;/li&gt; 
 &lt;li&gt;&lt;p&gt;&lt;a href="https://aws.amazon.com/devops-agent/"&gt;AWS DevOps Agent product page&lt;/a&gt;&lt;/p&gt; &lt;/li&gt; 
&lt;/ul&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/aws-devops-agent-slack-code-channels-teams-two-way/</ore:originalUrl>
      <ore:upstreamId>cd0339545addd598b2efec11c8688986991c0161</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:17e9ad887648aea979ae9bdcd0200f0c</id>
    <title>AWS Partner Central guides now available in the console and through AWS Partner Central Agents</title>
    <updated>2026-11-19T21:51:00Z</updated>
    <published>2026-11-19T21:51:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/partner-central-guides-mcp/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;AWS announces AWS Partner Central guides with access through the &amp;nbsp;&lt;a href="https://us-east-1.console.aws.amazon.com/partnercentral/content?region=us-east-1"&gt;AWS Partner Central console&amp;nbsp;&lt;/a&gt; and the AWS Partner Central Agents Model Context Protocol (MCP) server. The guides give AWS Partners one place to search, read, and share content that AWS organizes to help partners grow and expand their business. The guides hold authoritative, partner-specific knowledge on programs, benefits, technical topics, marketing, funding, and more, which requires sign-in and permissions. Partners benefit from more accurate answers about programs, benefits, and requirements.&lt;/p&gt; 
&lt;p&gt;Partners can browse by topic, search instantly across every guide, and see content based on their recent activity and AWS program updates. Partners can also ask AWS Partner Central Agents questions in their own words, such as "Which guides explain the requirements for the AWS Foundational Technical Review?" or "Show me everything in Migration Acceleration Program quick reference." Partner Central guides complement the public information about AWS Partner Central features in AWS documentation.&lt;/p&gt; 
&lt;p&gt;AWS Partner Central guides are available to all AWS Partners in the AWS Partner Central console and through the AWS Partner Central Agents MCP server in the US East (N. Virginia) Region in English. Partners can bring these guides into tools such as Kiro, AWS Quick, CRM systems, and other AI clients. To learn more, visit &amp;nbsp;&lt;a href="https://docs.aws.amazon.com/partner-central/latest/getting-started/guides.html"&gt;Guides in the AWS Partner Central console&amp;nbsp;&lt;/a&gt; or &amp;nbsp;&lt;a href="https://docs.aws.amazon.com/partner-central/latest/developer-guide/mcp-getting-started.html"&gt;Getting started with the Partner Central Agents MCP server&amp;nbsp;&lt;/a&gt;.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/partner-central-guides-mcp/</ore:originalUrl>
      <ore:upstreamId>fe57fa6c24e0f7f418d3c74921fecd335c863daa</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:8782ff3554adb4b289fbde832fd61122</id>
    <title>AWS Marketplace now supports agentic payments with AgentCore</title>
    <updated>2026-11-19T21:30:00Z</updated>
    <published>2026-11-19T21:30:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/marketplace-agentic-payments-agentcore/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;AWS Marketplace now supports agentic payments over the x402 protocol, so AI agents can discover and buy select products and pay per request in US dollars through AgentCore payments, part of Amazon Bedrock AgentCore. Agents often need paid APIs, data, or content mid-task, but access usually requires a person to sign up, add a payment method, and create an API key. With agentic payments, customers skip that per-seller setup, and charges settle on their existing AWS bill with no crypto wallet required.&lt;/p&gt; 
&lt;p&gt;Customers enable the AWS Marketplace payment connector in AgentCore payments, then they or their agents find listings through the AWS Marketplace connector in AgentCore Gateway. For example, a research agent can buy a single web search, or a coding agent can call a paid guardrail service. Customers can set spending limits, approved sellers, and guardrails before agents transact, Private Marketplace policies still apply, and transactions appear in AWS CloudTrail and AWS Cost Explorer.&lt;/p&gt; 
&lt;p&gt;AWS Marketplace sellers can charge AI agents per request without building a sign-up flow or billing system. They register with AWS Marketplace, configure agentic payments for their listings, and integrate the &lt;a href="https://github.com/aws/fiat-extension-for-x402/blob/main/docs/sdk-guide.md"&gt;AWS Marketplace x402 SDK&lt;/a&gt;. AWS Marketplace collects customer payments and pays sellers through their AWS Marketplace seller disbursements, like other AWS Marketplace transactions.&lt;/p&gt; 
&lt;p&gt;The capability is available in all AWS Regions where AgentCore payments is available. To learn more, see &lt;a href="https://aws.amazon.com/marketplace/solutions/ai-agents-and-tools?ams%23interactive-card-vertical%23pattern-data-843993407.filters=((id:GLOBAL%23local-tags-aws-marketplace-agentic-ai-x402-support.and,value:(x402-support)))"&gt;AWS Marketplace&lt;/a&gt; and the &lt;a href="https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/payments-process-payment.html" target="_blank" rel="noopener noreferrer"&gt;Amazon Bedrock AgentCore Developer Guide&lt;/a&gt;. To list as a seller, see the &lt;a href="https://docs.aws.amazon.com/marketplace/latest/userguide/agentic-commerce-products.html" target="_blank" rel="noopener noreferrer"&gt;AWS Marketplace Seller Guide.&lt;/a&gt;&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/marketplace-agentic-payments-agentcore/</ore:originalUrl>
      <ore:upstreamId>799e717c67fea2f9dcb8fe4218d4349d4e353d02</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:4a840e471ef0b32c7f9f8d39ee3d9014</id>
    <title>Amazon Cognito now supports client ID metadata documents</title>
    <updated>2026-11-19T21:00:00Z</updated>
    <published>2026-11-19T21:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/cognito-client-id-metadata-documents/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;&lt;a href="https://aws.amazon.com/cognito/"&gt;Amazon Cognito&lt;/a&gt; now supports OAuth client ID metadata documents (CIMD). Amazon Cognito helps you implement secure sign-in and access control for users, AI agents, and microservices in minutes. With CIMD, Model Context Protocol (MCP) clients and AI agents can sign users in to your user pool without registering a separate app client. Previously, each external client needed its own app client, either created in advance or through dynamic client registration, and you had to manage and clean up those clients over time.&lt;/p&gt;
&lt;p&gt;With CIMD, a client uses an HTTPS URL as its client ID and publishes a JSON metadata document at that URL. When the client starts sign-in, Cognito fetches and validates the document and uses it to identify the client and validate its sign-in request. You decide which clients to accept with CIMD policies that map URL patterns to one of your app clients, and Cognito grants only the scopes and grant types that both the app client and the metadata document allow. For example, a company that runs an MCP server can accept an AI assistant by allowing the URL where that assistant publishes its metadata without creating or maintaining an app client for it.&lt;/p&gt;
&lt;p&gt;CIMD is available on the Essentials and Plus feature plans in all &lt;a href="https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/"&gt;AWS Regions&lt;/a&gt; where Amazon Cognito is available. To learn more, see &lt;a href="https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-pools-client-id-metadata.html" target="_blank"&gt;Client ID metadata documents (CIMD)&lt;/a&gt; in the Amazon Cognito Developer Guide.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/cognito-client-id-metadata-documents/</ore:originalUrl>
      <ore:upstreamId>ad9942991b58d39d2fc5ed02f47ff0b66c69d266</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:1dc3ef77ab5432348623f99724206710</id>
    <title>Amazon Aurora DSQL now delivers up to 50% higher write throughput</title>
    <updated>2026-11-19T20:53:00Z</updated>
    <published>2026-11-19T20:53:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/aurora-dsql-higher-write-throughput/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;With upgrades to its storage layer, &lt;a href="https://aws.amazon.com/rds/aurora/dsql/"&gt;Amazon Aurora DSQL&lt;/a&gt; now delivers up to 50% higher write throughput for many transactional workloads. Data loads finish sooner, and tables whose primary key always increases, such as tables keyed by a timestamp, an identity column, or a time-ordered ID like ULID or UUIDv7, see even greater benefits.&lt;/p&gt; 
&lt;p&gt;Applications such as audit logs, ledgers, and event feeds are read in time order, and keying them by time keeps those reads fast. You can now use that design for write-heavy tables too. In our tests, an audit log table keyed by event time accepted up to 200% more inserts per second.&lt;/p&gt; 
&lt;p&gt;The improvement is available in all &lt;a href="https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/"&gt;AWS Regions&lt;/a&gt; where Aurora DSQL is available, for new and existing clusters, at no additional cost. To learn more, see the &lt;a href="https://docs.aws.amazon.com/aurora-dsql/latest/userguide/what-is-aurora-dsql.html"&gt;Aurora DSQL User Guide&lt;/a&gt;.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/aurora-dsql-higher-write-throughput/</ore:originalUrl>
      <ore:upstreamId>88c1fdb2bd1964c9c8075fa93d9ed629651a4ac9</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:5ba9df94506f662ac6b7a513884f579c</id>
    <title>Amazon CloudFront adds IP based routing and connection logs to SaaS Manager</title>
    <updated>2026-11-19T20:26:00Z</updated>
    <published>2026-11-19T20:26:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/cloudfront-ip-based-routing-connection-logging" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;Amazon CloudFront now allows web development and SaaS platforms to serve different tiers of customers on the same wildcard domain by using IP addresses to route them to the right configuration. For example, these platforms can serve premium and pro customers from dedicated Anycast static IP address lists, each with its own configuration, and serve free-tier customers on the shared CloudFront IP addresses, all under *.&lt;a href="http://example.com"&gt;example.com&lt;/a&gt;. Additionally, these customers also have visibility into viewer connections with connection logging.&lt;/p&gt; 
&lt;p&gt;Previously, CloudFront chose the configuration from the domain name alone, so the same domain always went to the same configuration. With address-based selection, you can register the same wildcard domain on several IP lists and send each list to its own tenant. Because you control which clients resolve to which IP list, you can shift traffic between your service tiers without your customers needing to make any changes. You can also serve IoT devices, embedded SDKs, and older TLS clients that connect by IP address without sending a domain name in the TLS handshake (Server Name Indication, or SNI). With viewer fallback, you choose a distribution to accept these connections, and CloudFront uses the Host header in each request to serve the right content. Connection logs now also record HTTPS connections to these tenants which helps you troubleshoot how clients connect.&lt;/p&gt; 
&lt;p&gt;These features are available at all CloudFront edge locations. To learn more, see &lt;a href="https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/address-based-selection.html"&gt;Address-based selection&lt;/a&gt; and &lt;a href="https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/connection-logs.html"&gt;Connection Logs&lt;/a&gt; in the Amazon CloudFront Developer Guide.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/cloudfront-ip-based-routing-connection-logging</ore:originalUrl>
      <ore:upstreamId>933ab4118c3faf5c583fd0378c463fdb22a14d77</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:d505dcd5ab784b9c84b6b7faae658441</id>
    <title>Amazon CloudFront simplifies domain moves and onboarding for SaaS Manager</title>
    <updated>2026-11-19T20:22:00Z</updated>
    <published>2026-11-19T20:22:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/cloudfront-domain-moves-distribution-tenants" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;Amazon CloudFront now lets web development platforms and SaaS providers move a customer's domain to their platform in a single request with no downtime, and serve requests to the domain while the TLS certificate is being configured. The CloudFront multi-tenant distributions allow these platforms to serve many customer domains from one shared configuration. Together, these features help move existing AWS customers to multi-tenant distributions without impacting their traffic.&lt;/p&gt; 
&lt;p&gt;Previously, moving a domain that was already in use required disabling the original distribution, using a wildcard workaround, or contacting AWS Support. Now you can bring customer domains onto your multi-tenant setup as part of creating or updating a tenant. With the new OnDomainTakeover option, CloudFront checks domain ownership through DNS records and then moves one or more domains in a single request. This works within an AWS account or across accounts. If you add a domain before its certificate is issued, CloudFront serves it over HTTP until you attach a certificate. That gives you time to validate the domain with AWS Certificate Manager (ACM) or another certificate authority and attach the certificate once it's issued.&lt;/p&gt; 
&lt;p&gt;These features are available in all edge locations at no additional cost. To learn more, see &lt;a href="https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/alternate-domain-names-move-options.html"&gt;Move domains&lt;/a&gt; and &lt;a href="https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/tenant-domains-without-certificate.html"&gt;Domains without a certificate&lt;/a&gt; in the Amazon CloudFront Developer Guide.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/cloudfront-domain-moves-distribution-tenants</ore:originalUrl>
      <ore:upstreamId>0265b42490e15e06862edf8086e1478e3b460cd1</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:048228fb908a66ed0d295e02879de84a</id>
    <title>Amazon Connect launches Resolutions, an agentic solution for high-volume operational work</title>
    <updated>2026-11-19T20:06:00Z</updated>
    <published>2026-11-19T20:06:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/amazon-connect-resolutions/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;Amazon Connect Customer announces the general availability of Resolutions, an agentic operations solution that resolves high-volume work end-to-end, including refund requests, transaction disputes, fraud investigations, and insurance claims. Resolutions helps businesses reduce resolution times and cost to serve by combining the reasoning of AI agents with the reliability of deterministic workflows. Every request follows business policy, gets the oversight it requires, and ends in a verifiable outcome.&lt;/p&gt; 
&lt;p&gt;Managers describe a process in natural language or upload standard operating procedures (SOPs), and Resolutions generates a Work plan in minutes. As it builds the Work plan, Resolutions asks clarifying questions that surface exceptions, set decision rules, and define approval thresholds, closing the gaps an SOP leaves open. Resolutions then opens a Resolutions Case for each incoming request and applies the right Work plan. AI agents gather information, apply policy, act across your business applications, and ask customers for missing details to drive every Case to completion. Each Step can run on prebuilt AI agents, AI agents configured in Amazon Connect Customer, or your own, while human specialists handle approvals and exceptions with the context they need to act.&lt;/p&gt; 
&lt;p&gt;For example, a bank resolving a transaction dispute can have AI agents pull the transaction history, check the claim against chargeback rules, email the cardholder for a missing receipt, and issue a provisional credit, so a specialist reviews only the disputes that need judgment. Resolutions verifies each outcome and records every action and decision, giving operations leaders an auditable, real-time view of progress, workload, and service level risk.&lt;/p&gt; 
&lt;p&gt;To learn more, visit our &lt;a href="https://docs.aws.amazon.com/connect/latest/adminguide/amazon-connect-get-started.html"&gt;documentation,&lt;/a&gt; &lt;a href="https://aws.amazon.com/products/connect/customer/?trk=25b81a8c-c9b1-4866-9ba5-f9cb1c5e792a&amp;amp;sc_channel=ps&amp;amp;ef_id=Cj0KCQiA2frXBhC_ARIsAPTFcdPy7k_--3zFXuoVNfszpx_W8hiYrEB8MQvqdwmwAyaVmbZVy16FsEcaAlx0EALw_wcB:G:s&amp;amp;gclid=Cj0KCQiA2frXBhC_ARIsAPTFcdPy7k_--3zFXuoVNfszpx_W8hiYrEB8MQvqdwmwAyaVmbZVy16FsEcaAlx0EALw_wcB"&gt;webpage&lt;/a&gt;, and &lt;a href="https://aws.amazon.com/products/connect/customer/pricing/appendix/?refid=758059ab-77e5-44fc-8a4a-1be845ee42b9"&gt;pricing page&lt;/a&gt;.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/amazon-connect-resolutions/</ore:originalUrl>
      <ore:upstreamId>14838e985dc5ad7ce8cab53c9c8615631026d66f</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:d424e10be4574f19efee44001d6eece6</id>
    <title>AWS Lambda durable functions now supports OpenTelemetry tracing</title>
    <updated>2026-11-19T20:00:00Z</updated>
    <published>2026-11-19T20:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/lambda-durable-otel/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;AWS Lambda announces OpenTelemetry (OTel) support for Lambda durable functions. You can now trace your durable executions and emit traces to Amazon CloudWatch and other industry-standard observability tools.&amp;nbsp;This helps you find bottlenecks in your system, root cause failures faster, and understand how your workflows behave in production.&lt;/p&gt; 
&lt;p&gt;With Lambda durable functions, you can build resilient, multi-step applications and AI workflows that run for up to one year, with built-in checkpointing and automatic retries. Durable functions can run for&amp;nbsp;hours, or days, suspending and resuming across many Lambda invocations. The new OpenTelemetry plugin emits a unified trace that spans a full durable execution, including steps, waits, callbacks, and chained function invocations. You can use the trace to gain operational insights across your executions including step durations, retries, and failures across executions.&amp;nbsp;&amp;nbsp;&lt;/p&gt; 
&lt;p&gt;The OpenTelemetry plugin is available for the TypeScript, Python, and Java SDKs. You can enable OpenTelemetry support by adding the OpenTelemetry plugin package alongside the Durable Execution SDK and register it on your durable handler or using an environment variable. OpenTelemetry support for Lambda durable functions is available in all AWS Regions that support Lambda durable functions.&lt;/p&gt; 
&lt;p&gt;To get started, see the&amp;nbsp; &lt;a href="https://docs.aws.amazon.com/durable-execution/sdk-reference/observability/opentelemetry"&gt;OpenTelemetry plugin documentation&lt;/a&gt;, the &lt;a href="https://docs.aws.amazon.com/durable-execution/sdk-reference/observability/plugins/"&gt;plugin interface documentation&lt;/a&gt;, and the &lt;a href="https://github.com/aws-samples/sample-lambda-durable-functions-otel-tracing"&gt;sample application&lt;/a&gt;. To learn more, read &lt;a href="https://aws.amazon.com/blogs/compute/aws-lambda-durable-functions-observability-with-opentelemetry/"&gt;the blog post&lt;/a&gt;.&amp;nbsp;&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/lambda-durable-otel/</ore:originalUrl>
      <ore:upstreamId>ed283d59f8064ee4267113d8c8f71ca342cdee09</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:8adeb5715319ceb49549a8c11d76ce83</id>
    <title>AWS Marketplace agent mode now helps you assess, buy, and deploy solutions</title>
    <updated>2026-11-19T20:00:00Z</updated>
    <published>2026-11-19T20:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/aws-marketplace/aws-marketplace-agent-mode-expansion" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;You can now assess a seller's security, buy, and deploy supported products in one conversation with AWS Marketplace agent mode, the conversational AI experience for procuring cloud solutions. You share your requirement once, and agent mode applies them as it guides you through discovery, purchase, and deployment.&lt;/p&gt; 
&lt;p&gt;Describe your use case in natural language to get recommended software, services, AI agents and tools, and multi-product solutions that fit your business needs. To assess a seller's security, request documents such as System and Organization Controls (SOC) 2 reports, and get a criterion-by-criterion assessment against a standard cloud security questionnaire, the Consensus Assessments Initiative Questionnaire (CAIQ).&lt;/p&gt; 
&lt;p&gt;When you're ready to buy, sign in with your AWS account. Agent mode explains pricing and terms so you know what you're committing to, shows your organizations' purchase requirements, and completes the purchase after you review the terms and confirm. For supported products, agent mode reviews your AWS environment, proposes a deployment plan with the estimated monthly cost, and deploys after you approve. It then shows you how to start using the product and helps you troubleshoot if a step fails.&lt;/p&gt; 
&lt;p&gt;Agent mode is available in all AWS Regions where AWS Marketplace is available.&lt;/p&gt; 
&lt;p&gt;To get started, open &lt;a href="https://aws.amazon.com/marketplace/agentmode"&gt;agent mode&lt;/a&gt; on the AWS Marketplace website. To learn more, see &lt;a href="https://docs.aws.amazon.com/marketplace/latest/buyerguide/agent-mode.html"&gt;Agent mode for AWS Marketplace&lt;/a&gt; in the AWS Marketplace Buyer Guide.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/aws-marketplace/aws-marketplace-agent-mode-expansion</ore:originalUrl>
      <ore:upstreamId>57e5d9662829ced41138cd9d655385c2563dbb17</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:3bdcc53fb49eb1330d2adbb5c89f3bcb</id>
    <title>Amazon WorkSpaces Applications now supports WebAuthn redirection</title>
    <updated>2026-11-19T19:57:00Z</updated>
    <published>2026-11-19T19:57:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/amazon-workspaces-applications-webauthn-redirection/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;Amazon WorkSpaces Applications now supports WebAuthn redirection, so users can sign in to websites and applications in their streaming session with a FIDO2 authenticator on their local device, such as a security key, Windows Hello, or Touch ID. Previously, an authenticator attached to the user's computer was not available inside the streaming session, so organizations that require phishing-resistant multi-factor authentication (MFA) had to use weaker sign-in methods or keep those applications off WorkSpaces Applications. This helps organizations with FIDO2 requirements stream those applications.&lt;/p&gt; 
&lt;p&gt;When an application in the session makes a WebAuthn request, WorkSpaces Applications forwards it to the user's device, where the authenticator signs it and returns the response. Private keys never leave the user's device. Administrators turn it on per stack in the console or API, and on Windows fleets can limit it to an allow list of processes. For example, a bank can let employees sign in to Microsoft 365 in their streaming session with the same security key they use on their laptop.&lt;/p&gt; 
&lt;p&gt;WebAuthn redirection is available at no additional charge in all AWS commercial Regions and AWS GovCloud (US) Regions where WorkSpaces Applications is available.&lt;/p&gt; 
&lt;p&gt;To get started, select Enable WebAuthn redirection under User Settings for your stack, use an image with the WorkSpaces Applications agent released on or after October 20, 2026, and connect with the WorkSpaces Applications client for Windows (1.5.0 or later) or macOS (1.6.0 or later). To learn more, see &lt;a href="https://docs.aws.amazon.com/appstream2/latest/developerguide/feature-support-webauthn-redirection.html" target="_blank"&gt;WebAuthn redirection&lt;/a&gt; in the Amazon WorkSpaces Applications Administration Guide, or visit the &lt;a href="https://aws.amazon.com/workspaces/applications/" target="_blank"&gt;Amazon WorkSpaces Applications&lt;/a&gt; product page.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/amazon-workspaces-applications-webauthn-redirection/</ore:originalUrl>
      <ore:upstreamId>e7edf120a215bc3c5ba3eb455c05ac6b659984d3</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:c940aa8b7f5bcebe094318360e827e1c</id>
    <title>Amazon Route 53 now supports health checks for private endpoints</title>
    <updated>2026-11-19T19:50:00Z</updated>
    <published>2026-11-19T19:50:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/route-53-private-endpoint-health-checks/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;div class="OutlineElement Ltr SCXW180369299 BCX2" style="direction: ltr;"&gt;
 &lt;p class="Paragraph SCXW180369299 BCX2" lang="EN-US" style="font-weight: normal; font-style: normal; vertical-align: baseline; background-color: transparent; color: windowtext; text-align: justify; margin: 0px 0px 16px; padding-left: 0px; padding-right: 0px; text-indent: 0px;"&gt;&lt;span style="color: rgb(0, 0, 0); font-size: 11pt; line-height: 17.4375px; font-family: Calibri, &amp;quot;Calibri_EmbeddedFont&amp;quot;, &amp;quot;Calibri_MSFontService&amp;quot;, sans-serif; font-weight: normal;" data-contrast="none" lang="EN-US" class="TextRun SCXW180369299 BCX2"&gt;&lt;span class="NormalTextRun SCXW180369299 BCX2"&gt;Amazon Route 53 now offers Private Endpoint Health Checks, enabling business-critical workloads that never touch the public internet, such as internal APIs, databases, and self-hosted nodes behind internal load balancers or in private subnets, to use native health monitoring and automatic DNS failover. Customers can health-check any reachable private target by IP address, domain, or port over HTTP, HTTPS, or TCP. Customers can associate these health checks with Route 53 DNS records across routing policies in private hosted zones, so Route 53 routes traffic only to healthy endpoints and manages failover automatically.&lt;/span&gt;&lt;/span&gt;&lt;span class="EOP Selected SCXW180369299 BCX2" style="font-size: 11pt; line-height: 17.4375px; font-family: Calibri, &amp;quot;Calibri_EmbeddedFont&amp;quot;, &amp;quot;Calibri_MSFontService&amp;quot;, sans-serif; color: rgb(0, 0, 0);" data-ccp-props="{&amp;quot;134233117&amp;quot;:false,&amp;quot;134233118&amp;quot;:false,&amp;quot;335551550&amp;quot;:6,&amp;quot;335551620&amp;quot;:6,&amp;quot;335559738&amp;quot;:0,&amp;quot;335559739&amp;quot;:240}"&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt; 
&lt;/div&gt; 
&lt;div class="OutlineElement Ltr SCXW180369299 BCX2" style="direction: ltr;"&gt;
 &lt;p class="Paragraph SCXW180369299 BCX2" style="font-weight: normal; font-style: normal; vertical-align: baseline; background-color: transparent; color: windowtext; text-align: justify; margin: 16px 0px; padding-left: 0px; padding-right: 0px; text-indent: 0px;"&gt;&lt;span style="color: rgb(0, 0, 0); font-size: 11pt; line-height: 17.4375px; font-family: Calibri, &amp;quot;Calibri_EmbeddedFont&amp;quot;, &amp;quot;Calibri_MSFontService&amp;quot;, sans-serif; font-weight: normal;" data-contrast="none" lang="EN-US" class="TextRun SCXW180369299 BCX2"&gt;&lt;span class="NormalTextRun SCXW180369299 BCX2"&gt;Previously, teams built custom control loops using Amazon CloudWatch alarms, AWS Lambda functions, and the Route 53 API to achieve DNS failover for private resources. With t&lt;/span&gt;&lt;span class="NormalTextRun CommentStart SCXW180369299 BCX2"&gt;his approach&lt;/span&gt;&lt;span class="NormalTextRun SCXW180369299 BCX2"&gt;, failover took several minutes and added &lt;/span&gt;&lt;span class="NormalTextRun ContextualSpellingAndGrammarErrorV2Themed SCXW180369299 BCX2"&gt;operational&lt;/span&gt;&lt;span class="NormalTextRun SCXW180369299 BCX2"&gt; burden. Detection and DNS failover with Private Endpoint Health Checks are designed to complete in seconds rather than &lt;/span&gt;&lt;span class="NormalTextRun ContextualSpellingAndGrammarErrorV2Themed SCXW180369299 BCX2"&gt;minutes,&lt;/span&gt;&lt;span class="NormalTextRun SCXW180369299 BCX2"&gt; the service is fully managed, and nothing is exposed to the public internet.&lt;/span&gt;&lt;/span&gt;&lt;span class="EOP Selected SCXW180369299 BCX2" style="font-size: 11pt; line-height: 17.4375px; font-family: Calibri, &amp;quot;Calibri_EmbeddedFont&amp;quot;, &amp;quot;Calibri_MSFontService&amp;quot;, sans-serif; color: rgb(0, 0, 0);" data-ccp-props="{&amp;quot;134233117&amp;quot;:false,&amp;quot;134233118&amp;quot;:false,&amp;quot;335551550&amp;quot;:6,&amp;quot;335551620&amp;quot;:6,&amp;quot;335559738&amp;quot;:240,&amp;quot;335559739&amp;quot;:240}"&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt; 
&lt;/div&gt; 
&lt;div class="OutlineElement Ltr SCXW180369299 BCX2" style="direction: ltr;"&gt;
 &lt;p class="Paragraph SCXW180369299 BCX2" style="font-weight: normal; font-style: normal; vertical-align: baseline; background-color: transparent; color: windowtext; text-align: justify; margin: 16px 0px; padding-left: 0px; padding-right: 0px; text-indent: 0px;"&gt;&lt;span style="color: rgb(0, 0, 0); font-size: 11pt; line-height: 17.4375px; font-family: Calibri, &amp;quot;Calibri_EmbeddedFont&amp;quot;, &amp;quot;Calibri_MSFontService&amp;quot;, sans-serif; font-weight: normal;" data-contrast="none" lang="EN-US" class="TextRun SCXW180369299 BCX2"&gt;&lt;span class="NormalTextRun SCXW180369299 BCX2"&gt;The feature supports on-premises and hybrid endpoints reachable from the VPC over AWS Direct Connect or AWS Site-to-Site VPN, enabling resilience patterns such as active-passive disaster recovery and cross-Region DR over AWS Transit Gateway or AWS Cloud WAN. Amazon Route 53 Private Endpoint Health Checks is available today in all AWS commercial regions. To learn more, visit the &lt;/span&gt;&lt;/span&gt;&lt;a class="Hyperlink SCXW180369299 BCX2" style="text-decoration: none; color: inherit;" href="https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/health-checks-private-endpoints.html" target="_blank" rel="noreferrer noopener"&gt;&lt;span style="color: rgb(0, 115, 187); font-size: 12pt; text-decoration: underline; line-height: 22.0875px; font-family: Aptos, &amp;quot;Aptos_EmbeddedFont&amp;quot;, &amp;quot;Aptos_MSFontService&amp;quot;, sans-serif;" data-contrast="none" lang="EN-US" class="TextRun Underlined SCXW180369299 BCX2"&gt;&lt;span class="NormalTextRun CommentStart SCXW180369299 BCX2" data-ccp-charstyle="Hyperlink"&gt;Amazon Route 53 Developer Guide&lt;/span&gt;&lt;/span&gt;&lt;/a&gt;&lt;span data-contrast="auto" style="font-size: 10.5pt; line-height: 20.925px; font-family: &amp;quot;Amazon Ember&amp;quot;, &amp;quot;Amazon Ember_EmbeddedFont&amp;quot;, &amp;quot;Amazon Ember_MSFontService&amp;quot;, sans-serif;" lang="EN-US" class="TextRun SCXW180369299 BCX2"&gt;&lt;span class="NormalTextRun SCXW180369299 BCX2"&gt; and the &lt;/span&gt;&lt;/span&gt;&lt;a style="text-decoration: none; color: inherit;" href="https://aws.amazon.com/route53/pricing/" target="_blank" rel="noreferrer noopener" class="Hyperlink SCXW180369299 BCX2"&gt;&lt;span style="color: rgb(70, 120, 134); font-size: 12pt; text-decoration: underline; line-height: 22.0875px; font-family: Aptos, &amp;quot;Aptos_EmbeddedFont&amp;quot;, &amp;quot;Aptos_MSFontService&amp;quot;, sans-serif;" data-contrast="none" lang="EN-US" class="TextRun Underlined SCXW180369299 BCX2"&gt;&lt;span class="NormalTextRun SCXW180369299 BCX2" data-ccp-charstyle="Hyperlink"&gt;Route 53 pricing page.&lt;/span&gt;&lt;/span&gt;&lt;/a&gt;&lt;span data-contrast="auto" style="font-size: 12pt; line-height: 22.0875px; font-family: Aptos, &amp;quot;Aptos_EmbeddedFont&amp;quot;, &amp;quot;Aptos_MSFontService&amp;quot;, sans-serif;" lang="EN-US" class="TextRun EmptyTextRun SCXW180369299 BCX2"&gt;&lt;/span&gt;&lt;span class="EOP Selected SCXW180369299 BCX2" style="font-size: 12pt; line-height: 22.0875px; font-family: Aptos, &amp;quot;Aptos_EmbeddedFont&amp;quot;, &amp;quot;Aptos_MSFontService&amp;quot;, sans-serif;" data-ccp-props="{&amp;quot;134233117&amp;quot;:false,&amp;quot;134233118&amp;quot;:false,&amp;quot;335551550&amp;quot;:6,&amp;quot;335551620&amp;quot;:6,&amp;quot;335559738&amp;quot;:240,&amp;quot;335559739&amp;quot;:240}"&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt; 
&lt;/div&gt; 
&lt;p&gt;&amp;nbsp;&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/route-53-private-endpoint-health-checks/</ore:originalUrl>
      <ore:upstreamId>d64b7591d2687766b24e50a7852f53af51d31824</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:d2749407fd0180b6296ecac6dfc77b57</id>
    <title>AWS Revenue Measurement now supports deal-level revenue attribution for AWS Marketplace offers and opportunities</title>
    <updated>2026-11-19T19:25:00Z</updated>
    <published>2026-11-19T19:25:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/aws-revenue-measurement-deal-attribution/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;Today, AWS announces deal-level revenue attribution for AWS Revenue Measurement (previously Partner Revenue Measurement) capabilities. AWS Partners can now see how the AWS revenue measured for their products maps to specific AWS Marketplace offers and/or APN Customer Engagements (ACE) opportunities. Until now, partners who implemented AWS Revenue Measurement via &lt;a href="https://docs.aws.amazon.com/PRM/latest/aws-prm-onboarding-guide/resource-tagging.html"&gt;Resource Tagging&lt;/a&gt;, &lt;a href="https://docs.aws.amazon.com/PRM/latest/aws-prm-onboarding-guide/user-agent-string.html"&gt;User Agent String&lt;/a&gt; or &lt;a href="https://docs.aws.amazon.com/PRM/latest/aws-prm-onboarding-guide/marketplace-metering.html"&gt;AWS Marketplace Metering&lt;/a&gt; could view aggregated, product-level attributed revenue. With this launch, partners can view attributed revenue by offers and opportunities on the Attributed Revenue dashboard in AWS Partner Central for components hosted in partners' own AWS accounts. Two new capabilities make this possible: Revenue Attribution IDs and Marketplace Revenue Share.&lt;/p&gt; 
&lt;p&gt;A Revenue Attribution ID is a unique identifier that allows partners to allocate a product's measured AWS revenue to specific offers and opportunities. Partners create a Revenue Attribution ID, associate it with their deals, and enter a monthly attributed revenue allocation percentage for each deal. Partners with SaaS products on AWS Marketplace can automate allocation to offers with Marketplace Revenue Share. Each month, partners enter the percentage of the product's attributed revenue contributed by AWS Marketplace deals in the Revenue Attribution page, and AWS then calculates the attributed revenue for each active offer. Partners can use Revenue Attribution IDs alongside Marketplace Revenue Share to adjust a calculated offer amount or attribute revenue to opportunities for future months. Both capabilities build on AWS Revenue Measurement, so partners can extend their current product-level implementations to gain deal-level insights.&lt;/p&gt; 
&lt;p&gt;Partners can manage &lt;a href="https://docs.aws.amazon.com/PRM/latest/aws-prm-onboarding-guide/revenue-attribution-id.html"&gt;Revenue Attribution IDs&lt;/a&gt; and Marketplace Revenue Share in AWS Partner Central or through the &lt;a href="https://docs.aws.amazon.com/partner-central/latest/developer-guide/working-with-revenue-attribution.html"&gt;AWS Revenue Measurement&lt;/a&gt; and &lt;a href="https://docs.aws.amazon.com/partner-central/latest/developer-guide/working-with-marketplace-revenue-share.html"&gt;Marketplace Revenue Share APIs&lt;/a&gt;. AWS Revenue Measurement is generally available in all commercial Regions. To learn more, review the &lt;a href="https://docs.aws.amazon.com/PRM/latest/aws-prm-onboarding-guide/what-is-service.html"&gt;onboarding guide&lt;/a&gt;. &amp;nbsp;&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/aws-revenue-measurement-deal-attribution/</ore:originalUrl>
      <ore:upstreamId>ca15b1bbf6d7ec86ef578cf963f977d624ceba40</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:fd9a425a46ecbb9634bc2a73ee3a8b57</id>
    <title>IAM Roles Anywhere now supports aliases to simplify workload configuration</title>
    <updated>2026-11-19T19:23:00Z</updated>
    <published>2026-11-19T19:23:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/iam-roles-anywhere-alias/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;&lt;a href="https://aws.amazon.com/iam/roles-anywhere"&gt;AWS Identity and Access Management (IAM) Roles Anywhere&lt;/a&gt; now supports aliases, which are readable names that you assign to trust anchors, profiles, and certificate revocation lists (CRLs). Your workloads can request temporary credentials using a trust anchor or profile alias Amazon Resource Name (ARN) instead of an ARN with a system-generated ID, and you can use alias ARNs in many of the operations that manage these resources. Aliases make configurations easier to read and review: an alias ARN that ends in alias/trust-anchor/production-ca can show which certificate authority (CA) a workload uses.&lt;/p&gt; 
&lt;p&gt;Previously, workload configurations, such as credential helper settings in machine images and configuration management templates, referenced trust anchors and profiles by ARNs that contain system-generated IDs, which differ in every account and Region. With this launch, you can assign the same alias in each account and Region, so one configuration template works across them with only the account and Region values changed. To set an alias, specify an alias name when you create, import, or update a resource using the IAM Roles Anywhere console, AWS SDKs, or AWS CLI.&lt;/p&gt; 
&lt;p&gt;This feature is available at no additional cost in all commercial AWS Regions, the AWS GovCloud (US) Regions, the China Regions, and the AWS European Sovereign Cloud (Germany) Region. To learn more, see &lt;a href="https://docs.aws.amazon.com/rolesanywhere/latest/userguide/resource-aliases.html"&gt;Using aliases for trust anchors, profiles, and CRLs&lt;/a&gt; in the IAM Roles Anywhere User Guide.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/iam-roles-anywhere-alias/</ore:originalUrl>
      <ore:upstreamId>9e727e293e85e1a2299463e33090b98db0be0c28</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:f887a93b517c8dd38c95b9602ff6305e</id>
    <title>AWS Transform combines migration assessment and planning in one experience</title>
    <updated>2026-11-19T19:00:00Z</updated>
    <published>2026-11-19T19:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/aws-transform-assessment-and-planning" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;AWS Transform for migrations now combines migration assessment and migration planning into a single migration job. Previously, you ran separate jobs to build a total cost of ownership (TCO) business case and to plan your migration. With this launch, you upload your on-premises inventory once and use it for both assessment and planning, in any order.&lt;/p&gt; 
&lt;p&gt;After you upload your inventory data, you can estimate your AWS costs and build a business case, group your infrastructure into applications and plan migration waves, or do both. You can rerun either workflow as your data improves. For example, build a business case first and then plan waves from the same inventory, or plan your waves first and then estimate the cost of a single wave. Because assessment and planning share one inventory, your business case and migration plan stay consistent without moving data between jobs. After you finalize your plan and assessment, you can continue in the same job to migrate your networks, deploy landing zones, and migrate servers, storage, and containers.&lt;/p&gt; 
&lt;p&gt;This newest release is available in all &lt;a href="https://docs.aws.amazon.com/transform/latest/userguide/regions.html#default-regions"&gt;AWS Regions where AWS Transform is offered&lt;/a&gt;. To learn more about migrating with AWS Transform, visit the &lt;a href="https://aws.amazon.com/transform/migrations/"&gt;product page&lt;/a&gt;&amp;nbsp;and &lt;a href="https://docs.aws.amazon.com/transform/latest/userguide/transform-migrations-discover-assess-plan.html"&gt;documentation&lt;/a&gt;.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/aws-transform-assessment-and-planning</ore:originalUrl>
      <ore:upstreamId>1f004edcf54d0e0d31304d02efae24cbe457a7a6</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:aae5d82ee7bb1b679b3cde9fb04fc204</id>
    <title>AWS Lambda now supports a 30-minute timeout for on-demand Event Functions</title>
    <updated>2026-11-19T19:00:00Z</updated>
    <published>2026-11-19T19:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/aws-lambda-30-minute-ondemand-event-functions/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;AWS Lambda now supports a 30-minute function timeout for &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/lambda-functions-chapter.html"&gt;Event Functions&lt;/a&gt; that run on demand, doubling the 15-minute limit for &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/invocation-sync.html"&gt;synchronous&lt;/a&gt;, &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/invocation-async.html"&gt;asynchronous&lt;/a&gt;, and &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/invocation-eventsourcemapping.html"&gt;event source mapping (ESM)&lt;/a&gt; invocations. On &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/lambda-managed-instances.html"&gt;Lambda Managed Instances&lt;/a&gt;, synchronous invocations also support up to 30 minutes, while asynchronous and ESM invocations keep the &lt;a href="https://aws.amazon.com/blogs/compute/announcing-90-minute-function-timeout-on-aws-lambda-managed-instances/"&gt;90-minute timeout&lt;/a&gt; launched in September 2026. You can now run long-running workloads such as AI inference, media transcoding, and financial calculations for spiky or steady-state traffic without re-architecting your applications.&lt;/p&gt; 
&lt;p&gt;Customers use&amp;nbsp;Event Functions to build event-driven processors, API backends, and data pipelines. By default, Event Functions run on demand, and Lambda scales them automatically to handle spiky traffic. For steady-state traffic, you can also run them on Lambda Managed Instances, which runs functions on Amazon EC2 instances and&amp;nbsp;maintains&amp;nbsp;the operational simplicity of Lambda.&amp;nbsp;For data-intensive workloads such as AI inference and media processing that run on demand and need longer continuous execution, the 15-minute function timeout had required customers to adopt&amp;nbsp;architectural workarounds. With today's launch, these workloads can run for up to 30 minutes, including when you use &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/durable-functions.html"&gt;Lambda durable functions&lt;/a&gt; or invoke your functions from &lt;a href="https://docs.aws.amazon.com/step-functions/latest/dg/choosing-workflow-type.html"&gt;AWS Step Functions Standard workflows&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;For Event Functions that run on demand, the 30-minute timeout is available in all&amp;nbsp;commercial &lt;a href="https://builder.aws.com/build/capabilities"&gt;AWS Regions&lt;/a&gt;. On Lambda Managed Instances, it is available for synchronous invocations in all Regions where Lambda Managed Instances is available. You can set the function timeout by using the Lambda console, AWS CLI, AWS SDKs, AWS CloudFormation, AWS CDK, or AWS SAM. You can also use coding assistants such as Kiro, Claude Code, or Codex with the &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/agent-setup-guide.html"&gt;Agent Toolkit for AWS&lt;/a&gt;. Standard &lt;a href="https://aws.amazon.com/lambda/pricing/"&gt;AWS Lambda pricing&lt;/a&gt; applies. To learn more, visit the &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/configuration-timeout.html"&gt;AWS Lambda Developer Guide&lt;/a&gt;.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/aws-lambda-30-minute-ondemand-event-functions/</ore:originalUrl>
      <ore:upstreamId>f468b118564dc4cafce64d0115a46d23e4b6f1e9</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:4ddc6c58633c64af6bebdcaf91dbe537</id>
    <title>AWS Transform extends application-centric migration across the lifecycle</title>
    <updated>2026-11-19T19:00:00Z</updated>
    <published>2026-11-19T19:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/aws-transform-application-centric-migration" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;AWS Transform now puts applications at the center of every stage of the migration journey, so you can discover, plan, migrate, validate, and track the applications your business runs on rather than just the servers underneath them. Application-level grouping has been part of AWS rehost workflows for years, and AWS Transform now carries that same view through your entire migration.&lt;/p&gt; 
&lt;p&gt;Enterprise migrations typically involve thousands of servers, but the questions that drive decisions are about applications. Using discovery data, AWS Transform identifies application boundaries and dependencies, then surfaces logical groupings of applications, each with its own total cost of ownership (TCO) and migration tracking. AWS Transform also adds built-in surveys, letting application owners validate ownership, system boundaries, and business criticality.&amp;nbsp;&lt;/p&gt; 
&lt;p&gt;A new migration dashboard keeps everyone aligned as the migration moves forward. It gives your team, partners, and leadership one current view of your applications, inventory, assessments, wave plans, and migration status. The dashboard pulls in data from every job in a workspace and updates as work progresses, so no one has to build or maintain separate status reports. You can customize the dashboard and ask questions about migration progress in chat.&amp;nbsp;&lt;/p&gt; 
&lt;p&gt;With a more connected workflow and improved visibility across the migration, AWS Transform lets you move to the cloud with more confidence.&amp;nbsp;This capability is available in all &lt;a href="https://docs.aws.amazon.com/transform/latest/userguide/regions.html#default-regions"&gt;AWS Regions where AWS Transform is offered&lt;/a&gt;. To learn more about migrating with AWS Transform, visit the &lt;a href="https://aws.amazon.com/transform/migrations/"&gt;product page&lt;/a&gt;.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/aws-transform-application-centric-migration</ore:originalUrl>
      <ore:upstreamId>c478ecce87c779564801365fe5d8847944359ece</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:b8733d7bd4cce9873a44c62a2ba83681</id>
    <title>Amazon IVS Real-Time Streaming now provides a Linux broadcast SDK</title>
    <updated>2026-11-19T18:49:00Z</updated>
    <published>2026-11-19T18:49:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/amazon-ivs-real-time-streaming-linux-broadcast-sdk" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;The Amazon Interactive Video Service (Amazon IVS) Linux broadcast SDK is now available for IVS Real-Time Streaming. Applications running on Linux can join an IVS stage, receive audio from participants, and send audio back to the stage in real time. The SDK provides a C API and Go language bindings.&lt;/p&gt; 
&lt;p&gt;The Linux broadcast SDK is ideal for AI applications that enrich live streams by processing audio, such as transcription, translation, and content moderation, as well as voice agents that converse with participants.&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://aws.amazon.com/ivs/"&gt;Amazon IVS&lt;/a&gt; is a managed live streaming solution designed to make low-latency or real-time video available to viewers around the world. Visit the &lt;a href="https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/"&gt;AWS Region table&lt;/a&gt; for a full list of AWS Regions where the Amazon IVS console and APIs for control and creation of video streams are available.&lt;/p&gt; 
&lt;p&gt;To learn more, see &lt;a href="https://docs.aws.amazon.com/ivs/latest/RealTimeUserGuide/broadcast-linux.html"&gt;IVS Broadcast SDK: Linux Guide&lt;/a&gt;.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/amazon-ivs-real-time-streaming-linux-broadcast-sdk</ore:originalUrl>
      <ore:upstreamId>88cca09c2dc521d99fac2d308aaa28d4c8f8fb9f</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:b4696f0a755c4b6b8cff3046322cc395</id>
    <title>AWS WAF launches new Security Analytics Dashboard for real-time investigations</title>
    <updated>2026-11-19T18:00:00Z</updated>
    <published>2026-11-19T18:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/02/aws-waf-security-analytics-dashboard/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;AWS WAF now gives you one place to find and stop unwanted traffic across every application in your account. The new AWS WAF security analytics dashboard brings together traffic from all of your protection packs (web ACLs), whether they protect Regional resources or Amazon CloudFront distributions, into a single view. The dashboard also lets you search request logs right in the console, with no logging pipeline to build, and includes 21 days of full-fidelity request data at no additional cost. It is available alongside the existing dashboard for each protection pack (WebACL), which continues to work as it does today.&lt;/p&gt; 
&lt;p&gt;Until now, spotting a trend across your applications, such as a bot campaign hitting several endpoints or a spike in blocked requests, meant opening each web ACL in turn or individually querying AWS WAF logs. With the AWS WAF security analytics dashboard, you can analyze traffic data from every protection pack (WebACL) at once. You can filter and group traffic by dimensions such as client IP address, country, ASN, user agent, JA4 fingerprint, host, path, rule triggered, and labels. You can see which endpoints are affected and how traffic is changing across all of them. The data is full-fidelity rather than sampled, and filters apply across the whole dashboard.&lt;/p&gt; 
&lt;p&gt;Investigating individual requests has also required delivering AWS WAF logs to Amazon CloudWatch Logs, Amazon S3, or Amazon Data Firehose and writing queries. AWS WAF Security analytics dashboard includes a logs widget that lets you search and explore raw request logs in the console, down to the full HTTP request, with no log delivery to configure. When you find unwanted traffic, you can block an IP address or a country directly from the page. You can also filter by the labels that managed rules attach to requests to see what a rule in Count mode would block before you enforce it.&lt;/p&gt; 
&lt;p&gt;The AWS WAF security analytics dashboard is available at no additional cost in all commercial AWS Regions where AWS WAF is available. This feature is not available in the AWS GovCloud (US) Regions and China Regions. To get started, open the AWS WAF console and choose Security analytics in the navigation pane.&amp;nbsp;To learn more, see the &lt;a href="https://docs.aws.amazon.com/waf/latest/developerguide/web-acl-security-analytics.html" target="_blank" rel="noopener noreferrer"&gt;AWS WAF Developer Guide&lt;/a&gt;&amp;nbsp;and &lt;a href="https://aws.amazon.com/blogs/security/introducing-the-new-aws-waf-security-analytics-dashboard/" target="_blank" rel="noopener noreferrer"&gt;launch blog post&lt;/a&gt;.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/02/aws-waf-security-analytics-dashboard/</ore:originalUrl>
      <ore:upstreamId>62a6c490dc41e303b203547df6199e019ba38b12</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:220a60c9ed13650d1d47212f71b69cc6</id>
    <title>Amazon Cognito now supports AWS Secrets Manager for app client secrets</title>
    <updated>2026-11-19T18:00:00Z</updated>
    <published>2026-11-19T18:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/cognito-secrets-manager-integration/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;&lt;a href="https://aws.amazon.com/cognito/"&gt;Amazon Cognito&lt;/a&gt; now integrates with &lt;a href="https://aws.amazon.com/secrets-manager/"&gt;AWS Secrets Manager&lt;/a&gt;, so you can store and manage your user pool app client secrets in Secrets Manager. Amazon Cognito helps you implement secure sign-in and access control for users, AI agents, and microservices in minutes. An app client secret authenticates your application to Cognito. Previously, you had to manage and rotate these secrets in Cognito directly.&lt;/p&gt;
&lt;p&gt;With this integration, you can leverage Secrets Manager for capabilities including rotation, access control with AWS Identity and Access Management (IAM) policies, and encryption with an AWS managed key or your own AWS Key Management Service (AWS KMS) customer managed key. This can help with periodic credential rotation or compliance requirements; this also helps with keeping secrets out of the console. You can enable this integration for either a new or an existing app client, and disable it at any time.&lt;/p&gt;
&lt;p&gt;This integration is available in all &lt;a href="https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/"&gt;AWS Regions&lt;/a&gt; where Amazon Cognito and AWS Secrets Manager are available, except AWS European Sovereign Cloud (Germany). Standard &lt;a href="https://aws.amazon.com/secrets-manager/pricing/"&gt;AWS Secrets Manager charges&lt;/a&gt; apply. To learn more, see the &lt;a href="https://docs.aws.amazon.com/cognito/latest/developerguide/user-pool-settings-client-apps.html" target="_blank"&gt;Amazon Cognito Developer Guide&lt;/a&gt; for instructions.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/cognito-secrets-manager-integration/</ore:originalUrl>
      <ore:upstreamId>e1bef2d44dc47bb4f0fb93cdefb79d81c40b7a20</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:0fcef04495f783416d0c7172550f825b</id>
    <title>AWS Elemental MediaTailor adds Dynamic Avail Sizing for live HLS</title>
    <updated>2026-11-19T18:00:00Z</updated>
    <published>2026-11-19T18:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/aws-elemental-mediatailor-dynamic-avail-sizing-live-hls" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;AWS Elemental MediaTailor now supports Dynamic Avail Sizing, which reduces the slate viewers see when ad breaks, also called avails, in live HLS streams go unfilled. MediaTailor is a server-side ad insertion and channel assembly service that personalizes ads in live and on-demand video streams.&lt;/p&gt; 
&lt;p&gt;When the ad decision server returns fewer ads than a break allows, dynamic avail sizing omits the unfilled time and resumes programming early instead of showing slate. To keep playback continuous, MediaTailor holds back a configurable reserve of content behind the live edge and draws on it when a break ends early. When the reserve runs low, MediaTailor requests extra ad time in later breaks to refill it. Free ad-supported streaming TV (FAST) channel operators can use dynamic avail sizing to keep viewers watching programming instead of filler content.&lt;/p&gt; 
&lt;p&gt;Customers turn on dynamic avail sizing for each playback session by adding query parameters to the session initialization URL, with no change to their playback configuration. To learn more, see &lt;a href="https://docs.aws.amazon.com/mediatailor/latest/ug/dynamic-avail-sizing.html"&gt;Dynamic avail sizing&lt;/a&gt; in the AWS Elemental MediaTailor User Guide.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/aws-elemental-mediatailor-dynamic-avail-sizing-live-hls</ore:originalUrl>
      <ore:upstreamId>a48002a9e5df2d4160bcb0c616b103d4e9133c80</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:c1273ae176a167a096c57c732a31285b</id>
    <title>Amazon Aurora now supports moving clusters to a different VPC</title>
    <updated>2026-11-19T17:00:00Z</updated>
    <published>2026-11-19T17:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/aurora-move-clusters-to-different-vpc/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;Aurora PostgreSQL and Aurora MySQL clusters can now move from one Amazon Virtual Private Cloud (VPC) to another without data migration. You can move a cluster with a single API call or a modify action in the Amazon RDS console. This lets you move a cluster to a VPC with more IP address space or a non-overlapping CIDR range, consolidate your network architecture, or meet changing security and compliance requirements.&lt;/p&gt; 
&lt;p&gt;Previously, moving an Aurora cluster to a different VPC meant creating a new cluster in the target VPC, migrating your data, and updating your applications with new connection strings. Now, a single ModifyDBCluster API call moves your existing cluster to the new VPC. Your data stays in place, your cluster endpoint stays the same, and connectivity is interrupted only briefly during the move. Before you start, turn off features that are tied to the cluster's current VPC, such as Aurora Global Database, Amazon RDS Proxy, and Amazon RDS Blue/Green Deployments. You can set them up again in the new VPC after the move.&lt;/p&gt; 
&lt;p&gt;This feature is available for Aurora PostgreSQL and Aurora MySQL in all &lt;a href="https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/CHAP_GettingStartedAurora.AuroraPostgreSQL.ExpressConfig.html#CHAP_GettingStartedAurora.AuroraPostgreSQL.ExpressConfig.SupportedRegions" target="_blank"&gt;AWS Regions&lt;/a&gt; where Aurora PostgreSQL with express configuration is available. To get started, use the &lt;a href="https://console.aws.amazon.com/rds/home" target="_blank" rel="noopener noreferrer"&gt;Amazon RDS console&lt;/a&gt;, AWS CLI, or AWS SDKs. To learn more, see the &lt;a href="https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_VPC.WorkingWithRDSInstanceinaVPC.html#USER_VPC.WorkingWithRDSInstanceinaVPC.UpdatingVPC" target="_blank" rel="noopener noreferrer"&gt;Aurora User Guide&lt;/a&gt;.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/aurora-move-clusters-to-different-vpc/</ore:originalUrl>
      <ore:upstreamId>be7f58178e94d384fdacba858b1a672bb1613539</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:39a421f2080bbc12f0e492e4f7bcae5b</id>
    <title>Aurora PostgreSQL with express configuration now supports Amazon VPC</title>
    <updated>2026-11-19T17:00:00Z</updated>
    <published>2026-11-19T17:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/aurora-postgresql-express-vpc/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;Aurora PostgreSQL databases created with express configuration can now move into an Amazon Virtual Private Cloud (VPC) with a single API call or a modify action in the Amazon RDS console. This helps you take AI-built prototypes and other applications to production without migrating data, while meeting your security and compliance requirements. You can also create a new database cluster inside a VPC using express configuration.&lt;/p&gt; 
&lt;p&gt;With express configuration, Aurora PostgreSQL lets you create and query a serverless database in seconds. Connectivity runs through an internet access gateway, which makes this a good fit for rapid prototyping and AI agent-driven development. When your application is ready for production, a single ModifyDBCluster API call moves the cluster into a VPC and turns off the internet access gateway. That gives you security groups, private subnets, and features such as Aurora Global Database, Amazon RDS Blue/Green Deployments, and Amazon RDS Proxy. The move requires no data migration, keeps your cluster endpoint the same, and interrupts connectivity only briefly. You can also reverse it with the same API call.&lt;/p&gt; 
&lt;p&gt;This feature is available in all &lt;a href="https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/CHAP_GettingStartedAurora.AuroraPostgreSQL.ExpressConfig.html#CHAP_GettingStartedAurora.AuroraPostgreSQL.ExpressConfig.SupportedRegions" target="_blank" rel="noopener noreferrer"&gt;AWS Regions&lt;/a&gt; where Aurora PostgreSQL with express configuration is available. To get started, use the &lt;a href="https://console.aws.amazon.com/rds/home?refid=35100cff-4aaa-46ac-bc1d-71576bef47be" target="_blank" rel="noopener noreferrer"&gt;Amazon RDS console&lt;/a&gt;, AWS CLI, or AWS SDKs. To learn more, see the &lt;a href="https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/CHAP_GettingStartedAurora.AuroraPostgreSQL.ExpressConfig.html#CHAP_GettingStartedAurora.AuroraPostgreSQL.ExpressConfig.MoveIntoVPC" target="_blank"&gt;Aurora User Guide&lt;/a&gt;.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/aurora-postgresql-express-vpc/</ore:originalUrl>
      <ore:upstreamId>b21e5267df252850fce81dc1155c37953c8a81d0</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:aws-whats-new:0a10c173854980aa0a935bf97e03bd48</id>
    <title>AWS Partner Central now supports AI-assisted listing experience for product, services, and solutions</title>
    <updated>2026-11-19T17:00:00Z</updated>
    <published>2026-11-19T17:00:00Z</published>
    <link rel="alternate" href="https://aws.amazon.com/about-aws/whats-new/2026/11/partner-central-ai-listing/" />
    <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    <category scheme="urn:ore-news:sources" term="aws-whats-new" label="AWS What's New" />
    <author>
      <name>AWS What's New</name>
    </author>
    <source>
      <id>urn:ore-news:source:aws-whats-new</id>
      <title>AWS What's New</title>
      <link rel="alternate" href="https://aws.amazon.com/new/" />
      <link rel="via" href="https://aws.amazon.com/about-aws/whats-new/recent/feed/" />
    </source>
    <content type="html">&lt;p&gt;AWS Marketplace search, Agent Mode, and AWS sales teams use listings to recommend partner offerings to AWS customers. Partners who sell software and services can now create and improve their listings in AWS Partner Central with the new AI-assisted listing experience. It drafts content from a partner's website and other materials, then shows which sections need clearer details, use cases, or evidence of customer outcomes. For single-AMI products, it also drafts the usage instructions buyers see after subscribing. Partners see, for each section, whether it meets what buyers look for, and choose which suggestions to use and review all content before publishing.&lt;/p&gt; 
&lt;p&gt;Partners can position products and professional services as distinct solutions for different industries, use cases, or outcomes. Each solution gets its own AWS Marketplace page, bringing its case studies and AWS Specializations together with the listing's pricing, reviews, and trust information, so buyers can evaluate and buy from the same page. Buyers can filter search results by Specialization. Partners not ready to share public pricing can publish without it using leads-only listings, through which interested customers request a private offer that reaches the partner as a lead in AWS Partner Central. Partners can test metering and billing setup before publishing, and ask the assistant metering questions while integrating.&lt;/p&gt; 
&lt;p&gt;These capabilities are available now to &lt;a href="https://aws.amazon.com/marketplace/"&gt;AWS Marketplace&lt;/a&gt; partners in all AWS Regions, except the AWS GovCloud (US) Regions and the China Regions. To get started, open AWS Partner Central and choose "Products and services" or "Solutions". To learn more, see &lt;a href="https://docs.aws.amazon.com/marketplace/latest/userguide/ai-assisted-listing.html" target="_blank" rel="noopener noreferrer"&gt;AI-assisted listing experience&lt;/a&gt; and &lt;a href="https://docs.aws.amazon.com/marketplace/latest/userguide/deciding-what-to-list.html" target="_blank" rel="noopener noreferrer"&gt;Deciding what to list&lt;/a&gt; in the &lt;a href="https://docs.aws.amazon.com/marketplace/latest/userguide/index.html" target="_blank" rel="noopener noreferrer"&gt;AWS Marketplace Seller Guide&lt;/a&gt;.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>aws-whats-new</ore:sourceId>
      <ore:sourceName>AWS What's New</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://aws.amazon.com/new/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://aws.amazon.com/about-aws/whats-new/recent/feed/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aws.amazon.com/about-aws/whats-new/2026/11/partner-central-ai-listing/</ore:originalUrl>
      <ore:upstreamId>5d6d07eea3f78b84fa0085c10aac5d6096043d1c</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hatena-bookmark-technology:69e3b65e3252f38c9e58b748a09830bc</id>
    <title>columnsプロパティで縦積みのナビゲーションを作る – TAKLOG</title>
    <updated>2026-11-19T16:01:13Z</updated>
    <published>2026-11-19T16:01:13Z</published>
    <link rel="alternate" href="https://www.tak-dcxi.com/article/vertical-navigation-with-columns-property/" />
    <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    <category scheme="urn:ore-news:sources" term="hatena-bookmark-technology" label="Hatena Bookmark Technology" />
    <author>
      <name>Hatena Bookmark Technology</name>
    </author>
    <source>
      <id>urn:ore-news:source:hatena-bookmark-technology</id>
      <title>Hatena Bookmark Technology</title>
      <link rel="alternate" href="https://b.hatena.ne.jp/hotentry/it" />
      <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hatena-bookmark-technology</ore:sourceId>
      <ore:sourceName>Hatena Bookmark Technology</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://b.hatena.ne.jp/hotentry/it</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://b.hatena.ne.jp/hotentry/it.rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://www.tak-dcxi.com/article/vertical-navigation-with-columns-property/</ore:originalUrl>
      <ore:upstreamId>https://www.tak-dcxi.com/article/vertical-navigation-with-columns-property/</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:cloudflare-blog:024ff73a29c08b4bf78e4de36892e3dd</id>
    <title>Internet traffic and attacks during the 2026 U.S. midterm elections</title>
    <updated>2026-11-19T14:00:00Z</updated>
    <published>2026-11-19T14:00:00Z</published>
    <link rel="alternate" href="https://blog.cloudflare.com/internet-traffic-2026-us-election/" />
    <link rel="via" href="https://blog.cloudflare.com/rss/" />
    <category scheme="urn:ore-news:sources" term="cloudflare-blog" label="Cloudflare Blog" />
    <author>
      <name>Cloudflare Blog</name>
    </author>
    <source>
      <id>urn:ore-news:source:cloudflare-blog</id>
      <title>Cloudflare Blog</title>
      <link rel="alternate" href="https://blog.cloudflare.com/" />
      <link rel="via" href="https://blog.cloudflare.com/rss/" />
    </source>
    <content type="html">&lt;p&gt;Visitors to government election websites surged 363% on November 3, the date of the 2026 midterm elections in the United States. Across Cloudflare&amp;#x27;s election protection programs, we also detected a significant shift in the types and timing of cyberattacks throughout 2026.&lt;/p&gt;&lt;p&gt;Unlike what we saw in other recent elections, attackers focused on gaining access to internal systems and data, rather than knocking websites offline. Government election websites faced website vulnerability attempts 180 times more often than denial-of-service (DDoS) attacks, and at roughly ten times the rate of Cloudflare&amp;#x27;s broader customer base. We also found evidence of at least one attempt to exploit a recently disclosed critical PHP vulnerability on a state government voting website in the Western United States.&lt;/p&gt;&lt;p&gt;These attacks peaked in late October, several weeks before the election. Vulnerability exploit attempts climbed steadily throughout 2026: from 200,000 per day in January, to &lt;em&gt;2 million per day&lt;/em&gt; in October. However, on Election Day in the U.S., Cloudflare detected no escalation in attack volume and zero major DDoS incidents across protected election sites, marking a sharp contrast to other recent elections, such as in &lt;a href="https://blog.cloudflare.com/helping-protect-the-2025-moldova-elections/"&gt;&lt;span style="text-decoration:underline"&gt;Moldova&lt;/span&gt;&lt;/a&gt; last year.&lt;/p&gt;&lt;p&gt;Our data regarding cyberattacks on election institutions came from organizations participating in Cloudflare&amp;#x27;s free cybersecurity programs: the &lt;a href="https://www.cloudflare.com/athenian/"&gt;&lt;span style="text-decoration:underline"&gt;Athenian Project&lt;/span&gt;&lt;/a&gt;, &lt;a href="https://www.cloudflare.com/campaigns/usa/"&gt;&lt;span style="text-decoration:underline"&gt;Cloudflare for Campaigns&lt;/span&gt;&lt;/a&gt;, and &lt;a href="https://www.cloudflare.com/galileo/"&gt;&lt;span style="text-decoration:underline"&gt;Project Galileo&lt;/span&gt;&lt;/a&gt;. Together, these initiatives helped protect more than 1,400 election-related websites during the 2026 U.S. midterm elections, including those belonging to state and local governments, candidates, political parties, voting-rights advocates, journalists, and civil society groups.&lt;/p&gt;&lt;p&gt;Cloudflare launched its first election protection program in 2016 after widespread reports of cyberattacks targeting the U.S. elections. A decade later, it is remarkable to see how far governments and campaigns have come in securing their digital infrastructure. We are proud to help protect democratic institutions and are encouraged that cyberattacks were once again not a disruptive factor in 2026.&lt;/p&gt;&lt;p&gt;In this post, we examine traffic and attacks observed against those organizations on Election Day, analyze the most common types of attacks of the 2026 cycle, and provide recommendations based on those findings.&lt;/p&gt;&lt;h2&gt;Election Day: significant voter traffic, minimal attacks&lt;/h2&gt;&lt;p&gt;Ordinary user traffic to state and local government election websites was higher on Election Day (November 3) than any other day in 2026. Traffic to those sites increased to approximately 602 million requests, up from 130 million on November 1. By comparison, traffic across the rest of Cloudflare’s global network rose by only 12% over the same period.&lt;/p&gt;&lt;p&gt;State and local government election websites provide authoritative information to voters on how to register, where to vote, and who won. Because of their critical role, these platforms are often targeted by those seeking to suppress voter turnout, disrupt the reporting of results, or steal sensitive information.&lt;/p&gt;&lt;p&gt;On Election Day itself, Cloudflare did not record a single significant distributed denial-of-service (DDoS) attack across any of its 1,400 election-related websites. The only significant DDoS attack occurred on November 2, targeting a candidate for the U.S. House of Representatives in California and totaled 520,000 requests. By comparison, the Moldovan Election Commission experienced more than 898 million malicious requests in a single 12-hour period on their Election Day in 2025, with attacks peaking at 324,333 requests per second.&lt;/p&gt;&lt;h2&gt;Prior to Election Day: the most common attacks in the 2026 cycle&lt;/h2&gt;&lt;p&gt;Website vulnerability scans were by far the most common attack observed by Cloudflare in the 2026 U.S. election cycle. In the 12 months leading up to the election, Cloudflare mitigated 392 million such attacks on government election websites alone.&lt;/p&gt;&lt;p&gt;Website vulnerability attacks exploit outdated or vulnerable website code to gain access to internal systems and data. For example, cross-site scripting attacks inject malicious code into web pages in order to capture administrator credentials or deface site content. &lt;a href="https://www.cloudflare.com/learning/security/threats/sql-injection/"&gt;&lt;span style="text-decoration:underline"&gt;SQL injection&lt;/span&gt;&lt;/a&gt; manipulates database queries allowing attackers to potentially extract voter records or alter data.&lt;/p&gt;&lt;p&gt;Phishing and other malicious emails targeting political campaigns protected by the company occurred at rates consistent with Cloudflare&amp;#x27;s broader network, but showed signs of sophistication. In the 90 days leading up to the election, 3.9% of emails sent to organizations participating in Cloudflare for Campaigns were identified as malicious, closely tracking the 4.8 percent baseline across other Cloudflare customers. However, nearly 42% of those malicious emails managed to bypass basic email authentication checks, such as verifying sender identity or preventing in-transit tampering. These threats were nonetheless identified by Cloudflare’s advanced phishing detection tools.&lt;/p&gt;&lt;p&gt;Although website vulnerabilities were the most common attack overall, for journalism and election-related civil society organizations, DDoS was the most common. Over the same 12-month period, Cloudflare mitigated over 10.8 billion DDoS requests targeting these groups. The largest single attack occurred on September 10, 2026, hitting a U.S.-based news organization with 3.04 billion requests. This pattern is consistent with &lt;a href="https://cf-assets.www.cloudflare.com/dzlvafdwdttg/5YmIHaAURvy8ZKjJ1CcQo6/1335a737054c44915ace715348e62697/BDES-9187_Cyberattacks_against_civil_society_Project_Galileo_Anniversary_Report.pdf"&gt;&lt;span style="text-decoration:underline"&gt;Cloudflare research&lt;/span&gt;&lt;/a&gt; released earlier this year, which found that among all Project Galileo entities in 120 countries, DDoS were by far the most common attack seen, accounting for 81% of all attacks.&lt;/p&gt;&lt;h2&gt;PHP vulnerability&lt;/h2&gt;&lt;p&gt;On October 21, security researchers disclosed serious vulnerabilities (known as &lt;a href="https://radar.cloudflare.com/zero-wire/php2shell#overview"&gt;&lt;span style="text-decoration:underline"&gt;php2shell&lt;/span&gt;&lt;/a&gt;) in PHP, an open source back-end programming language used by 70% of the world&amp;#x27;s websites. The flaws reportedly could allow attackers to execute malicious code on vulnerable servers, expose customer data, or disrupt services. Cloudflare &lt;a href="https://blog.cloudflare.com/php-vulnerabilities-waf-protection/"&gt;&lt;span style="text-decoration:underline"&gt;deployed&lt;/span&gt;&lt;/a&gt; Web Application Firewall (WAF) protections for all customers, prior to public disclosure of the vulnerability.&lt;/p&gt;&lt;p&gt;On October 22, Cloudflare&amp;#x27;s PHP defense was triggered more than 9,000 times on a state government election website in the Western U.S. This attack was only detected on one election-related site and appears to have been an isolated incident rather than part of a broader trend.&lt;/p&gt;&lt;h2&gt;Recommendations&lt;/h2&gt;&lt;p&gt;Cloudflare research consistently shows that individuals and organizations participating in democratic elections face significant risk of cyberattack. Data gathered during the 2026 U.S. midterm election suggests those attacks continue to evolve, occur throughout an election cycle and not only on Election Day, and can vary depending on the type of organization targeted.&lt;/p&gt;&lt;p&gt;Based on the recent cyberattack trends in the 2026 U.S. midterms and other elections, we make the following recommendations:  &lt;/p&gt;&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Prepare for surges in user traffic&lt;/strong&gt;. Legitimate voter interest can create traffic spikes that overwhelm unprepared infrastructure and make essential election websites inaccessible. Organizations should prepare scalable, efficient infrastructure to handle Election Day traffic increases without straining budgets or staff.  &lt;/li&gt;&lt;li&gt;&lt;strong&gt;Maintain security protections year-round, not just on Election Day. &lt;/strong&gt;Cyberattacks targeting democratic institutions occur across the entire election cycle, not just around voting windows. Defensive postures must remain active continuously rather than treated as a short-term, seasonal measure.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Deploy automated defenses to counter rapid threats. &lt;/strong&gt;AI has made it easier for attackers to find and exploit new vulnerabilities. Organizations should implement security services that update automatically, like &lt;a href="https://developers.cloudflare.com/waf/managed-rules/"&gt;&lt;span style="text-decoration:underline"&gt;managed rules&lt;/span&gt;&lt;/a&gt;, to ensure new protections deploy by default.&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;Ensuring voters have access to reliable information about elections not only helps encourage participation and deliver timely, accurate results, but also protects voter confidence in the democratic process itself. As more officials, more institutions, and the public increasingly rely on the Internet for those services, keeping that digital infrastructure stable, secure, and accessible becomes an essential civic priority.&lt;/p&gt;&lt;p&gt;State and local election offices, political campaigns, party organizations, journalists, and voting rights groups in need of cybersecurity services can access them from Cloudflare at no cost. Visit the &lt;a href="https://www.cloudflare.com/athenian/"&gt;&lt;span style="text-decoration:underline"&gt;Athenian Project&lt;/span&gt;&lt;/a&gt; (for state and local election websites), &lt;a href="https://www.cloudflare.com/campaigns/"&gt;&lt;span style="text-decoration:underline"&gt;Cloudflare for Campaigns&lt;/span&gt;&lt;/a&gt; (for political campaigns), or &lt;a href="https://www.cloudflare.com/galileo/"&gt;&lt;span style="text-decoration:underline"&gt;Project Galileo&lt;/span&gt;&lt;/a&gt; (for civil society, democracy, and journalism organizations) to learn more about eligibility and sign up today.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>cloudflare-blog</ore:sourceId>
      <ore:sourceName>Cloudflare Blog</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://blog.cloudflare.com/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://blog.cloudflare.com/rss/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://blog.cloudflare.com/internet-traffic-2026-us-election/</ore:originalUrl>
      <ore:upstreamId>01M7R5N9JG35DGY66ZG3E9RXSW</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hermes-agent-releases:2d685fd0505ed11d49d89aa4dd471252</id>
    <title>Hermes Agent canary v0.23.2+canary.20261119T064637Z</title>
    <updated>2026-11-19T07:54:29Z</updated>
    <published>2026-11-19T07:54:29Z</published>
    <link rel="alternate" href="https://github.com/NousResearch/hermes-agent/releases/tag/v0.23.2%2Bcanary.20261119T064637Z" />
    <link rel="via" href="https://api.github.com/repos/NousResearch/hermes-agent/releases" />
    <category scheme="urn:ore-news:sources" term="hermes-agent-releases" label="Hermes Agent GitHub Releases" />
    <author>
      <name>Hermes Agent GitHub Releases</name>
    </author>
    <source>
      <id>urn:ore-news:source:hermes-agent-releases</id>
      <title>Hermes Agent GitHub Releases</title>
      <link rel="alternate" href="https://github.com/NousResearch/hermes-agent/releases" />
      <link rel="via" href="https://api.github.com/repos/NousResearch/hermes-agent/releases" />
    </source>
    <content type="text"># Hermes Agent v0.23.2+canary.20261119T064637Z (v0.23.2+canary.20261119T064637Z)

**Release Date:** November 19, 2026

&lt;!-- HERMES_BUILDS_TABLE --&gt;
## Downloads

### Hermes Desktop

| OS | Architecture | Download |
|---|---|---|
| macOS | Apple Silicon (M-series) | [DMG](https://hermes-assets.nousresearch.com/releases/tag/v0.23.2%2Bcanary.20261119T064637Z/HermesBundled-0.23.2%2Bcanary.20261119T064637Z-mac-arm64.dmg) |
| Windows | x86 (64-bit) | [MSIX](https://hermes-assets.nousresearch.com/releases/tag/v0.23.2%2Bcanary.20261119T064637Z/HermesBundled-0.23.2%2Bcanary.20261119T064637Z-win-x64.msix) |
| Windows | ARM (arm64 / aarch64) | [MSIX](https://hermes-assets.nousresearch.com/releases/tag/v0.23.2%2Bcanary.20261119T064637Z/HermesBundled-0.23.2%2Bcanary.20261119T064637Z-win-arm64.msix) |

### Native install/chat smoke

Download availability is independent of smoke status. Each result covers all native legs in that format group. Linux bundles are disabled; unsigned Store envelopes are not install-smoked. No-upload dry tags have no download handoff and are not smoke-qualified.

| Packages | Smoke status |
|---|---|
| macOS DMG + ZIP (arm64) | Passed |
| Windows MSIX (arm64) | Passed |
| Windows MSIX (x64) | Passed |
&lt;!-- /HERMES_BUILDS_TABLE --&gt;

## ✨ Features

- Remedigenius to the plugin catalog ([`a66bd08e`](https://github.com/NousResearch/hermes-agent/commit/a66bd08e2e4cc1c4baecbd4fc546400db4860894)) — @RajaRenga
- Compression): cache-expiry compaction summarises on the conversation's warm prefix ([`4adb21a6`](https://github.com/NousResearch/hermes-agent/commit/4adb21a64e2a4f991b55839b21363a2dc9e83a25))

## 🔧 Improvements

- Caching): prompt_cache_lifecycle becomes a package ([`58d6946d`](https://github.com/NousResearch/hermes-agent/commit/58d6946da593e8c4d7768a3788d95af6ca352c48))

## 🐛 Bug Fixes

- Compression): clean up failed exclusive archives ([`6a5cee05`](https://github.com/NousResearch/hermes-agent/commit/6a5cee0598a4ff2b202b549dee15fc53a88e1a53)) — @100yenadmin
- Terminal): keep session exports under noclobber; make two test files host-independent ([`8a5207ef`](https://github.com/NousResearch/hermes-agent/commit/8a5207efc275c449872596d4f3ff9e4c22cb120a))
- Search_files): honour an inline (?i) prefix on the grep fallback ([`ba0ccdaa`](https://github.com/NousResearch/hermes-agent/commit/ba0ccdaa7d849933380cda3b3d4ea540af96af66))
- Gateway): release the failed accept frame before retry ([`e42af44d`](https://github.com/NousResearch/hermes-agent/commit/e42af44d9d55a587026faa476a88a32a83d1468a)) — @BearHuddleston
- Gateway): retry peer resets reported during accept submission ([`5416cd59`](https://github.com/NousResearch/hermes-agent/commit/5416cd59a55beefe9c9e08f5f6f3a3cceb1d525f)) — @BearHuddleston
- Gateway): skip the accept guard when the private hook is unavailable ([`db77e377`](https://github.com/NousResearch/hermes-agent/commit/db77e37729f30a7e9672c7a8ade9d09ed4d08e8e)) — @BearHuddleston
- Desktop): match gateway units that spell the copy path systemd-quoted ([`6f929bf8`](https://github.com/NousResearch/hermes-agent/commit/6f929bf85d0e7f224ee23d555b36d705471c77cb)) — @BearHuddleston
- Prompt-cache): a managed local model's unload is counted from when its reply finished ([`0e8e4216`](https://github.com/NousResearch/hermes-agent/commit/0e8e42164063bf426af328ef94e2001dcaf9db1f))
- Caching): a clock saved before the two-spec rules restores as the OpenAI spec ([`c5a01770`](https://github.com/NousResearch/hermes-agent/commit/c5a017707d79653e3a49af9a30550e6de652af7b))
- Caching): a queued cache-edge job skips a re-routed key; response usage adds under the totals lock ([`43979ca1`](https://github.com/NousResearch/hermes-agent/commit/43979ca1b106602c54862325794ae3816728c46b))
- Tui): a session cap disabled mid-sweep stops the cap loop ([`b5960c8f`](https://github.com/NousResearch/hermes-agent/commit/b5960c8fada69dd4d07cba6501ac5d9f2d71c64e))
- Compression): the tool results inside the summary window are archived before the summary replaces them ([`ced11ca7`](https://github.com/NousResearch/hermes-agent/commit/ced11ca70ed2d715c1178f0ed5473bfa51eeb323))
- Compression): warm summary names its window by replayed position, writes no new cache entry, runs only when cheaper; large chats need growth before re-compacting ([`ac42c246`](https://github.com/NousResearch/hermes-agent/commit/ac42c246fc23df8ccc6036fc32a77ae549461c6d))
- Caching): auto keeps the source tier and clamps per send; malformed prompt_caching never breaks startup; 1h writes over a 5m prefix price at 1h ([`2828b82f`](https://github.com/NousResearch/hermes-agent/commit/2828b82fa8c5960a24ca5ed309c213da1e2d37d5))
- Gateway): cache-expiry compaction claims the session, binds its profile scope, runs per-session jobs, reaches detached chats ([`6f4aa5e1`](https://github.com/NousResearch/hermes-agent/commit/6f4aa5e1f5ba6230e7def784f42332a10b4e4504))
- Compression): warm-prefix summary honours compression cancellation and explicit refusals ([`512d8765`](https://github.com/NousResearch/hermes-agent/commit/512d87655147f5314a124a5ba2b2035ba805c1f4))

## 📚 Documentation

- Website): file-tool instructions in developer guide; regenerate skill pages ([`928c7180`](https://github.com/NousResearch/hermes-agent/commit/928c718089d6696f83070301124dcd17cdc77b45))
- Skills): read, search and write files with the file tools in bundled skills ([`56ddecf4`](https://github.com/NousResearch/hermes-agent/commit/56ddecf469418f4914f4cd04fa3fe10b978425a8))
- Agents): point AGENTS.md lookups at search_files instead of grep/rg ([`5710d64a`](https://github.com/NousResearch/hermes-agent/commit/5710d64a722c67968ead4f14d345ee1593dd1927))

## 🧪 Tests

- Gateway): pin that the process record is built before the control listener opens ([`fe8b920c`](https://github.com/NousResearch/hermes-agent/commit/fe8b920cae0980cef854f478236f525aaf2b93ce))
- Windows): reap the pipe server when the readiness wait itself fails ([`055f3918`](https://github.com/NousResearch/hermes-agent/commit/055f391822c45fd4ecc75695e8580975178052f8))
- Windows): two live tests stop failing at random under load ([`49f87e3f`](https://github.com/NousResearch/hermes-agent/commit/49f87e3fa8c65e3d7b2630354c13e7d651f1d6f9))
- Gateway): trim the receipt restore tests to their invariants ([`35c059ac`](https://github.com/NousResearch/hermes-agent/commit/35c059acba3a76f01585854a567ab90f6da9dbdc))

## 🏗️ Infrastructure

- Docker): only pull-request builds use the Blacksmith layer cache ([`8a938f60`](https://github.com/NousResearch/hermes-agent/commit/8a938f60b4b9c998aa09bab64ae30db00cc2ce77)) — @c2h5oh

## 📦 Other Changes

- Remedigenius: re-pin to CE main b35dac3 (0.9.3) — marketplace review fixes ([`63ff0a5c`](https://github.com/NousResearch/hermes-agent/commit/63ff0a5c11373314e8478099ecb50a2c7d81f05b)) — @RajaRenga
- Re-pin-entry-to-main-commit-27e980a ([`3341917c`](https://github.com/NousResearch/hermes-agent/commit/3341917c26eee2d20dc32fb62d16a2011b4ae0b6)) — @RajaRenga

## 👥 Contributors

Thank you to everyone who contributed to this release!

- @BearHuddleston (8 commits)
- @kshitijk4poor (7 commits)
- @unsupportedpastels (5 commits)
- @RajaRenga (3 commits)
- @100yenadmin (1 commit)
- @c2h5oh (1 commit)

**Full Changelog**: [v0.23.2+canary.20261118T064620Z...v0.23.2+canary.20261119T064637Z](https://github.com/NousResearch/hermes-agent/compare/v0.23.2+canary.20261118T064620Z...v0.23.2+canary.20261119T064637Z)</content>
    <ore:provenance>
      <ore:sourceId>hermes-agent-releases</ore:sourceId>
      <ore:sourceName>Hermes Agent GitHub Releases</ore:sourceName>
      <ore:sourceType>github_releases</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://github.com/NousResearch/hermes-agent/releases</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://api.github.com/repos/NousResearch/hermes-agent/releases</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://github.com/NousResearch/hermes-agent/releases/tag/v0.23.2%2Bcanary.20261119T064637Z</ore:originalUrl>
      <ore:upstreamId>RE_kwDOPRF1G84a4Uwc</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hatena-bookmark-technology:57000d7fde9b25d4d68d0873046335c9</id>
    <title>正しいUIデザインと、意図のあるUIデザイン</title>
    <updated>2026-11-19T06:50:26Z</updated>
    <published>2026-11-19T06:50:26Z</published>
    <link rel="alternate" href="https://zenn.dev/praha/articles/08568310684aa3" />
    <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    <category scheme="urn:ore-news:sources" term="hatena-bookmark-technology" label="Hatena Bookmark Technology" />
    <author>
      <name>Hatena Bookmark Technology</name>
    </author>
    <source>
      <id>urn:ore-news:source:hatena-bookmark-technology</id>
      <title>Hatena Bookmark Technology</title>
      <link rel="alternate" href="https://b.hatena.ne.jp/hotentry/it" />
      <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hatena-bookmark-technology</ore:sourceId>
      <ore:sourceName>Hatena Bookmark Technology</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://b.hatena.ne.jp/hotentry/it</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://b.hatena.ne.jp/hotentry/it.rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://zenn.dev/praha/articles/08568310684aa3</ore:originalUrl>
      <ore:upstreamId>https://zenn.dev/praha/articles/08568310684aa3</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hacker-news:967ab65e33d0be33dc761a644e0d8aa7</id>
    <title>Fewer slides, more dragons</title>
    <updated>2026-11-19T05:46:36Z</updated>
    <published>2026-11-19T05:46:36Z</published>
    <link rel="alternate" href="https://www.breakingchange.blog/p/fewer-slides-more-dragons" />
    <link rel="via" href="https://news.ycombinator.com/rss" />
    <category scheme="urn:ore-news:sources" term="hacker-news" label="Hacker News" />
    <author>
      <name>Hacker News</name>
    </author>
    <source>
      <id>urn:ore-news:source:hacker-news</id>
      <title>Hacker News</title>
      <link rel="alternate" href="https://news.ycombinator.com/" />
      <link rel="via" href="https://news.ycombinator.com/rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hacker-news</ore:sourceId>
      <ore:sourceName>Hacker News</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://news.ycombinator.com/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://news.ycombinator.com/rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://www.breakingchange.blog/p/fewer-slides-more-dragons</ore:originalUrl>
      <ore:upstreamId>https://www.breakingchange.blog/p/fewer-slides-more-dragons</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hatena-bookmark-technology:7773cd0da02fd9d5b332043c0028f21d</id>
    <title>Welcome! You are invited to join a webinar: 【26/11/26開催】「脱WordPress」に取り組みたい方へ。セキュリティ懸念・運用負担を解消するSaaS型CMS移行. After registering, you will receive a confirmation email about joining the webinar.</title>
    <updated>2026-11-19T02:00:08Z</updated>
    <published>2026-11-19T02:00:08Z</published>
    <link rel="alternate" href="https://hatena.zoom.us/webinar/register/2217624929911/WN_UyuXGu7hRfSejKa5G_lUGg" />
    <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    <category scheme="urn:ore-news:sources" term="hatena-bookmark-technology" label="Hatena Bookmark Technology" />
    <author>
      <name>Hatena Bookmark Technology</name>
    </author>
    <source>
      <id>urn:ore-news:source:hatena-bookmark-technology</id>
      <title>Hatena Bookmark Technology</title>
      <link rel="alternate" href="https://b.hatena.ne.jp/hotentry/it" />
      <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hatena-bookmark-technology</ore:sourceId>
      <ore:sourceName>Hatena Bookmark Technology</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://b.hatena.ne.jp/hotentry/it</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://b.hatena.ne.jp/hotentry/it.rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://hatena.zoom.us/webinar/register/2217624929911/WN_UyuXGu7hRfSejKa5G_lUGg</ore:originalUrl>
      <ore:upstreamId>https://hatena.zoom.us/webinar/register/2217624929911/WN_UyuXGu7hRfSejKa5G_lUGg</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:tailscale-changelog:bd4c9cf813beb93ccbb9a1784074c731</id>
    <title>Log streaming integration with CrowdStrike Falcon Next-Gen SIEM</title>
    <updated>2026-11-19T00:00:00Z</updated>
    <published>2026-11-19T00:00:00Z</published>
    <link rel="alternate" href="https://tailscale.com/changelog/#2026-11-19-service" />
    <link rel="via" href="https://tailscale.com/changelog/index.xml" />
    <category scheme="urn:ore-news:sources" term="tailscale-changelog" label="Tailscale Changelog" />
    <author>
      <name>Tailscale Changelog</name>
    </author>
    <source>
      <id>urn:ore-news:source:tailscale-changelog</id>
      <title>Tailscale Changelog</title>
      <link rel="alternate" href="https://tailscale.com/changelog" />
      <link rel="via" href="https://tailscale.com/changelog/index.xml" />
    </source>
    <content type="html">&lt;ul&gt;
&lt;li&gt;New: Tailscale &lt;a href="/docs/features/logging/log-streaming#network-log-streaming"&gt;network flow logs&lt;/a&gt; and &lt;a href="/docs/features/logging/log-streaming#configuration-log-streaming"&gt;configuration audit logs&lt;/a&gt; can be streamed to &lt;a href="https://www.crowdstrike.com/en-us/platform/next-gen-siem/"&gt;CrowdStrike Falcon Next-Gen SIEM&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;</content>
    <ore:provenance>
      <ore:sourceId>tailscale-changelog</ore:sourceId>
      <ore:sourceName>Tailscale Changelog</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://tailscale.com/changelog</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://tailscale.com/changelog/index.xml</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://tailscale.com/changelog/#2026-11-19-service</ore:originalUrl>
      <ore:upstreamId>changelog:2026-11-19-crowdstrike-ng-siem-logstreaming</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:cloudflare-blog:0b8e794075c1c25545bdfe23eb9173b3</id>
    <title>An updated Clairic and Clairic-flash are now open-weight, from the new Workers AI Superintelligence team</title>
    <updated>2026-11-18T22:00:00Z</updated>
    <published>2026-11-18T22:00:00Z</published>
    <link rel="alternate" href="https://blog.cloudflare.com/open-clairic/" />
    <link rel="via" href="https://blog.cloudflare.com/rss/" />
    <category scheme="urn:ore-news:sources" term="cloudflare-blog" label="Cloudflare Blog" />
    <author>
      <name>Cloudflare Blog</name>
    </author>
    <source>
      <id>urn:ore-news:source:cloudflare-blog</id>
      <title>Cloudflare Blog</title>
      <link rel="alternate" href="https://blog.cloudflare.com/" />
      <link rel="via" href="https://blog.cloudflare.com/rss/" />
    </source>
    <content type="html">&lt;p&gt;Cloudflare has become a neolab. We’re building our own frontier AI models for our customers and the open-source community.&lt;/p&gt;&lt;p&gt;Today, we’re announcing two open-weight model releases:&lt;/p&gt;&lt;ul&gt;&lt;li&gt;We’re introducing an updated version of &lt;a href="https://developers.cloudflare.com/workers-ai/models/clairic"&gt;&lt;strong&gt;&lt;span style="text-decoration:underline"&gt;Clairic&lt;/span&gt;&lt;/strong&gt;&lt;/a&gt;. Since the preview, we’ve improved extraction from complex documents including images and PDFs (new!), with more reliable handling of tables, lists, and dates, and better grounding of answers in the source material.&lt;/li&gt;&lt;li&gt;We’re introducing &lt;a href="https://developers.cloudflare.com/workers-ai/models/clairic-flash"&gt;&lt;strong&gt;&lt;span style="text-decoration:underline"&gt;Clairic-flash&lt;/span&gt;&lt;/strong&gt;&lt;/a&gt;, a lighter, faster version of Clairic that delivers strong extraction and prediction performance in a compact, 9-billion-parameter model.&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;Both extraction models are hosted on Workers AI and full open weights are &lt;a href="https://huggingface.co/Cloudflare"&gt;&lt;span style="text-decoration:underline"&gt;available on Hugging Face&lt;/span&gt;&lt;/a&gt;.&lt;/p&gt;&lt;p&gt;We’re also excited to re-introduce ourselves as the Workers AI superintelligence team, the frontier AI research team behind &lt;a href="https://blog.cloudflare.com/clef-decision-models/"&gt;&lt;span style="text-decoration:underline"&gt;Clef&lt;/span&gt;&lt;/a&gt;, Clairic, and lots more in the works. This team is working quickly to push the AI frontier and build useful models for Cloudflare’s customers and the open source community.&lt;/p&gt;&lt;h2&gt;A new version of Clairic: redesigned after the preview release&lt;/h2&gt;&lt;p&gt;Since &lt;a href="https://blog.cloudflare.com/clairic-extraction-model"&gt;&lt;span style="text-decoration:underline"&gt;announcing Clairic&lt;/span&gt;&lt;/a&gt; in preview, we have received a ton of use cases and helpful feedback on how customers wanted to use an extraction model. We heard about use cases ranging from extracting data from images like receipts to reading values from support tickets. We knew that we wanted extraction to be the clear focus for the model, so it had to excel at reading from unstructured data.&lt;/p&gt;&lt;p&gt;We decided to go back to the drawing board with Clairic and redesigned our architecture, differentiating this new version of Clairic from our preview release. For ordinary text and number extraction fields, we now use &lt;strong&gt;parallel slot autoregressive generation&lt;/strong&gt; instead of a single forward pass. Each field uses the tokens it has already written to choose its next token, then stops at its own end marker. All the fields advance together in the serving batch, still giving lightning-fast latency per request. This boosted our accuracy in extraction for both text and images, and the trade-off in accuracy offsets the small latency cost. For computation, estimation, and extraction use cases, we trained special heads that can handle estimates, forecasts, durations, calculated dates, and explicit arithmetic.&lt;/p&gt;&lt;p&gt;Although the model architecture evolved, we kept the parts of the typed API interface that make the answers useful: confidence scores, character spans, and probabilities are still intact with every request. The model is still incredibly fast and cheap. From the evals below, you can see how our newer versions of Clairic have greatly improved on extraction across text, images, PDFs, and more.&lt;/p&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;Eval&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;Clairic-preview&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;Clairic&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;Clairic-flash&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;D1.2 + OCR&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;ScaleDown&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;Fresh text fields, 96 requests&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;295/336&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;335/336&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;328/336&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;304/336&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;259/336&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;Internal eval (mchen) - mixed-input fields, 36 requests&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;207/226&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;221/226&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;213/226&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;116/226&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;156/226&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;Tracked customer assertions, 139 request shapes&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;1,033/1,263&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;1,263/1,263&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;1,263/1,263&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;973/1,263&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;653/1,263&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;Synthetic receipt fields in text and images&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;369/576&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;576/576&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;576/576&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;397/576&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;280/576&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;There are no public extraction benchmarks yet, but we ran our internal evals for other emerging extraction models on the market, such as &lt;a href="https://openrouter.ai/liquid/d1.2"&gt;Liquid AI’s D1.2&lt;/a&gt; (pipelined with Apple Vision for optical character recognition) and &lt;a href="https://openrouter.ai/scaledown/extract"&gt;&lt;span style="text-decoration:underline"&gt;Scaledown’s Extract&lt;/span&gt;&lt;/a&gt;. Our Clairic models excel across extraction use cases, but take these evals as directional guidance since they are self-reported. We wanted to show an illustrative picture of how Clairic is performing across generalized extraction use cases and celebrate the fact that other companies are releasing extraction models as well — confirming our original hypothesis that extraction was a pain point for LLM users because of the cost, latency, and accuracy.&lt;/p&gt;&lt;h3&gt;But is it fast?&lt;/h3&gt;&lt;p&gt;We ran latency tests for Clairic and Clairic-flash, measuring complete HTTP response from a self-hosted server, including all fields in the request. Even with the redesigned architecture, you can expect responses in under one second — much faster than typical LLM responses for similar workloads.&lt;/p&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;Eval set&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;Requests per model&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;Clairic p50 / p95&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;Clairic-flash p50 / p95&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;Fresh text fields&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;96&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;358 / 736 ms&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;155 / 328 ms&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;Fresh image fields&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;48&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;453 / 976 ms&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;305 / 605 ms&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;Commercial leases&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;180&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;691 / 803 ms&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;379 / 519 ms&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;Loan pricing&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;600&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;395 / 407 ms&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;188 / 192 ms&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;Traffic forecasting&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;114&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;532 / 585 ms&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;243 / 261 ms&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;Expense audit, development&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;60&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;632 / 742 ms&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;393 / 512 ms&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;h3&gt;Better extraction for images and PDFs&lt;/h3&gt;&lt;p&gt;In our &lt;a href="https://blog.cloudflare.com/clairic-extraction-model"&gt;&lt;span style="text-decoration:underline"&gt;preview blog post&lt;/span&gt;&lt;/a&gt;, Clairic read a photo of a receipt. Now the Clairic family of models can read PDFs too, so you can ask for the supplier, line items, and total in one request, even when they appear on different pages. You can include up to four images or PDF pages in total, and line items can come back as rows that keep each description, quantity, and price together. Due to Clairic’s new architecture, image reading accuracy has improved from 207 errors to 0 on our internal benchmarks, explicitly covering text and images.&lt;/p&gt;&lt;!-- unsupported block: image --&gt;&lt;h3&gt;Promotional pricing on Clairic for a limited time&lt;/h3&gt;&lt;p&gt;When we first launched our preview endpoint of Clairic at &lt;code&gt;@cf/cloudflare/clairic&lt;/code&gt;, we hosted the 9B variant as it was faster and easier to train, at the preview price of $0.10 per M input tokens. We’re now moving the 9B model to the &lt;code&gt;@cf/cloudflare/clairic-flash&lt;/code&gt; endpoint and the 27B model will live at &lt;code&gt;@cf/cloudflare/clairic&lt;/code&gt;.&lt;/p&gt;&lt;p&gt;The 27B Clairic model will be priced at $0.24 per M input tokens, while the 9B Clairic-flash model will be priced at $0.10 per M input tokens. Although the model does technically generate output tokens, we decided to keep the &lt;a href="https://blog.cloudflare.com/clairic-extraction-model"&gt;&lt;span style="text-decoration:underline"&gt;System One&lt;/span&gt;&lt;/a&gt; pricing principles and are only charging on input tokens: we eat the cost of the output token generation.&lt;/p&gt;&lt;p&gt;In order to make this a seamless swap, we’re offering a promotional discount on Clairic — until December 1, 2026, both Clairic and Clairic-flash will cost $0.10 per M input tokens. This means you get to try out the higher quality variant of Clairic at the same price. If your applications are hooked up to the Clairic endpoint that we released in preview, you will automatically benefit from the better extraction capabilities of our new model, which we’re rolling out in place.&lt;/p&gt;&lt;p&gt;If you’d like to move more cost-sensitive workloads to the cheaper 9B Clairic-flash variant, we encourage you to do so. On December 1, we’ll be ending the promotional discount for Clairic and pricing will resume at $0.24 per M input tokens instead of the discounted $0.10 per M input tokens.&lt;/p&gt;&lt;h3&gt;Clairic and Clairic-flash (new) are open-weight&lt;/h3&gt;&lt;p&gt;Both Clairic models are now &lt;a href="https://huggingface.co/Cloudflare/"&gt;&lt;span style="text-decoration:underline"&gt;open-weight on Hugging Face&lt;/span&gt;&lt;/a&gt; as well. We have seen an outpouring of experiments and tuned models from our release of Clef, and we’re happy to continue supporting teams and research with our open-weight release of Clairic.&lt;/p&gt;&lt;p&gt;Our mission with these System One models is to help people augment their expensive LLM usage with smaller, faster, cheaper models that are purpose-built for a specific task. We hope that releasing these models open-weight encourages others to experiment and build on our ideas as well.&lt;/p&gt;&lt;h2&gt;Try them out&lt;/h2&gt;&lt;p&gt;Clairic and Clairic-flash are available on Workers AI as &lt;code&gt;@cf/cloudflare/clairic&lt;/code&gt; and &lt;code&gt;@cf/cloudflare/clairic-flash&lt;/code&gt;. The &lt;a href="https://developers.cloudflare.com/workers-ai/models/clairic"&gt;&lt;span style="text-decoration:underline"&gt;developer documentation&lt;/span&gt;&lt;/a&gt; has the full API schemas, which remain unchanged from our preview endpoint. We’re also publishing the open-weight releases for &lt;a href="https://huggingface.co/Cloudflare/clairic"&gt;&lt;span style="text-decoration:underline"&gt;Clairic&lt;/span&gt;&lt;/a&gt; and &lt;a href="https://huggingface.co/Cloudflare/clairic-flash"&gt;&lt;span style="text-decoration:underline"&gt;Clairic-flash&lt;/span&gt;&lt;/a&gt; on Hugging Face. &lt;/p&gt;&lt;p&gt;The team behind these models — the Workers AI superintelligence team — is just getting started, and growing fast to push frontier AI research at Cloudflare. &lt;a href="https://boards.greenhouse.io/cloudflare/jobs/8043974?gh_jid=8043974"&gt;&lt;span style="text-decoration:underline"&gt;Join us early&lt;/span&gt;&lt;/a&gt; and help shape what the superintelligence team becomes.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>cloudflare-blog</ore:sourceId>
      <ore:sourceName>Cloudflare Blog</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://blog.cloudflare.com/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://blog.cloudflare.com/rss/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://blog.cloudflare.com/open-clairic/</ore:originalUrl>
      <ore:upstreamId>01M7R89D5X67THE8N5T2YSWARZ</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:cloudflare-blog:c132d4de17ba97fbd460312c3e33b873</id>
    <title>How Cloudflare WAF helps protect against Java4Shell (CVE-2026-114938)</title>
    <updated>2026-11-18T14:52:10Z</updated>
    <published>2026-11-18T14:52:10Z</published>
    <link rel="alternate" href="https://blog.cloudflare.com/java4shell-waf-protection/" />
    <link rel="via" href="https://blog.cloudflare.com/rss/" />
    <category scheme="urn:ore-news:sources" term="cloudflare-blog" label="Cloudflare Blog" />
    <author>
      <name>Cloudflare Blog</name>
    </author>
    <source>
      <id>urn:ore-news:source:cloudflare-blog</id>
      <title>Cloudflare Blog</title>
      <link rel="alternate" href="https://blog.cloudflare.com/" />
      <link rel="via" href="https://blog.cloudflare.com/rss/" />
    </source>
    <content type="html">&lt;p&gt;On November 17, 2026, the security research company Calif disclosed &lt;a href="https://calif.io/java4shell/"&gt;&lt;span style="text-decoration:underline"&gt;Java4Shell (CVE-2026-114938)&lt;/span&gt;&lt;/a&gt;, a memory-corruption vulnerability in the Base64 decoder of OpenJDK, the most widely used Java runtime. Under the Common Vulnerability Scoring System (CVSS) 4.0, it scores 9.2 out of 10 (Critical). The flaw affects Java. OpenJDK published a &lt;a href="https://openjdk.org/groups/vulnerability/advisories/2026-11-17"&gt;&lt;span style="text-decoration:underline"&gt;security advisory&lt;/span&gt;&lt;/a&gt; and Oracle released patched builds in its &lt;a href="https://www.oracle.com/security-alerts/cspunov2026.html"&gt;&lt;span style="text-decoration:underline"&gt;November 2026 Critical Patch Update&lt;/span&gt;&lt;/a&gt; the same day, at 21:00 UTC.&lt;/p&gt;&lt;p&gt;The vulnerability lets a remote attacker with no credentials send malformed Base64 data to a Java application and overwrite memory next to the decoded output. Calif turned that overwrite into a leak of heap memory, similar to &lt;a href="https://www.heartbleed.com/"&gt;&lt;span style="text-decoration:underline"&gt;Heartbleed&lt;/span&gt;&lt;/a&gt;, and into remote code execution. Calif demonstrated pre-authentication remote code execution against Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins and PingFederate in their default configurations, and post-authentication remote code execution against Apache Kafka, Apache Solr, Elasticsearch, Gerrit, and Spinnaker.&lt;/p&gt;&lt;p&gt;Cloudflare has released a new set of rules in the Cloudflare Managed Ruleset designed to detect malformed Base64 input patterns associated with this vulnerability. The rules are available on Pro, Business and Enterprise plans and are enabled by default with the Log action because malformed input and some benign application-specific token formats can resemble exploitation attempts. Blocking by default could therefore disrupt legitimate traffic. Customers can review matching requests in Security Events now and change the rules action to Block once they confirm it does not affect legitimate traffic. &lt;/p&gt;&lt;p&gt;The WAF is an additional layer of defense, not a replacement for the patch. Java4Shell can be reached through paths a WAF does not see, like outbound TLS responses, and the only complete fix is to update the Java runtime. Our analysts continue to monitor attack activity and will update the rules as new techniques and variations appear. You can track rule changes in the &lt;a href="https://developers.cloudflare.com/waf/change-log/changelog/"&gt;&lt;span style="text-decoration:underline"&gt;WAF changelog&lt;/span&gt;&lt;/a&gt; and get more information on how the vulnerability develops on the dedicated &lt;a href="https://radar.cloudflare.com/zero-wire/java4shell"&gt;&lt;span style="text-decoration:underline"&gt;Cloudflare Zero Wire briefing&lt;/span&gt;&lt;/a&gt;.&lt;/p&gt;&lt;p&gt;We have seen no indication so far that Java4Shell was exploited on Cloudflare infrastructure.&lt;/p&gt;&lt;h2&gt;What we know about the vulnerability&lt;/h2&gt;&lt;p&gt;Base64 is a common way to represent binary data as text. Java applications decode Base64 when they process authentication headers, tokens, file uploads and many network messages. To decode it faster, OpenJDK replaces frequently used code with specialized machine code, called intrinsics. On supported x86-64 processors, the Base64 intrinsic uses AVX-512 instructions to process 64 bytes at a time.&lt;/p&gt;&lt;p&gt;The bug sits in the handwritten assembly that handles the final characters of the input. When the tail of the input contains padding characters (=) in a position where valid Base64 never places them, the routine calculates a negative output length. That invalid length turns into a full 64-byte write. For a 65-character input, made of 64 characters followed by a single =, OpenJDK allocates a 50-byte output array and then writes 62 bytes past its end.&lt;/p&gt;&lt;p&gt;Java eventually rejects the input as invalid and throws an exception. By then, the neighboring memory has already been overwritten. An application&amp;#x27;s own input validation does not help, because the corruption happens inside the decoder before the application can reject the data.&lt;/p&gt;&lt;p&gt;The simplest trigger is 64 A characters followed by =. On OpenJDK 17, the trigger needs 128 characters followed by =, because the threshold for the fast code path is higher.&lt;/p&gt;&lt;p&gt;Exploitation is not point-and-shoot. The overwritten bytes are mostly fixed values, and the attacker controls only where the write lands. To build a working exploit, Calif arranged the Java heap so that the overflow enlarged neighboring arrays, which gave them first a way to read heap memory and then a way to write chosen bytes. Each target application requires its own exploit chain. Calif reported developing its first working local exploit in about three hours with the help of AI agents, so we expect other attackers to build exploit chains quickly.&lt;/p&gt;&lt;h3&gt;Who is affected&lt;/h3&gt;&lt;p&gt;Java4Shell affects a system only when all the following conditions are true:&lt;/p&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;Condition&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;Details&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;Java runtime&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;OpenJDK 17.0.6 or newer, including distributions built from OpenJDK: Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu, BellSoft Liberica, SAP SapMachine, Red Hat OpenJDK, Oracle OpenJDK, Oracle Java SE and Oracle GraalVM for JDK. &lt;br/&gt;&lt;br/&gt;Check &lt;a href="https://www.oracle.com/security-alerts/cspunov2026.html"&gt;&lt;span style="text-decoration:underline"&gt;Oracle&amp;#x27;s advisory&lt;/span&gt;&lt;/a&gt; for the exact list of affected Oracle builds.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;Processor&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;x86-64 with AVX-512 VBMI support, such as Intel Xeon Ice Lake, Sapphire Rapids, Emerald Rapids and Granite Rapids, or AMD EPYC and Ryzen Zen 4 or newer. ARM64 processors are not affected.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;Input&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;The application decodes attacker-controlled Base64 data with the standard Java decoder.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;Many applications bundle their own Java runtime, and container images ship with a fixed Java Development Kit (JDK). Upgrading the system Java package does not update those copies, and it does not replace a Java virtual machine (JVM) that is already running. Every updated service needs a restart.&lt;/p&gt;&lt;h2&gt;Mitigate if you cannot patch right away&lt;/h2&gt;&lt;p&gt;If you cannot update immediately, Calif documents two JVM startup flags that remove the vulnerable code path:&lt;/p&gt;&lt;ul&gt;&lt;li&gt;&lt;code&gt;-XX:-UseBASE64Intrinsics&lt;/code&gt; disables hardware-accelerated Base64 encoding and decoding.&lt;/li&gt;&lt;li&gt;&lt;code&gt;-XX:UseAVX=2&lt;/code&gt; disables AVX-512. Apply this flag only on x86-64 hosts. OpenJDK on ARM does not recognize it and will fail to start.&lt;br/&gt;&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;Both flags require a restart and may reduce performance for workloads that decode large amounts of Base64. They buy time while you patch. They do not replace the update.&lt;/p&gt;&lt;h2&gt;Protect your infrastructure while you patch&lt;/h2&gt;&lt;p&gt;Patching every Java runtime takes time, especially when JDKs are bundled inside applications and container images. Cloudflare WAF can reduce your exposure while you patch. A new managed rule, available on paid plans and enabled in Log mode by default, detects the malformed Base64 input that triggers Java4Shell. For Business and Enterprise customers, &lt;a href="https://developers.cloudflare.com/waf/detections/attack-score/"&gt;&lt;span style="text-decoration:underline"&gt;WAF attack score&lt;/span&gt;&lt;/a&gt; adds a machine learning layer that scores each request for remote code execution payloads, which helps catch variations and bypass attempts that signature-based rules can miss.&lt;/p&gt;&lt;h3&gt;New managed rules&lt;/h3&gt;&lt;p&gt;Protection for paid plans has been released as part of the Cloudflare Managed Ruleset (Ruleset ID efb7b8c949ac4650a09736fc376e9aee). The rule is enabled by default with the Log action, because blocking by default could cause false positives on legitimate Base64 traffic. To review its matches, go to Security &amp;gt; Security Analytics &amp;gt; Events and filter by the rule ID. If the matches are not legitimate traffic, change the rule action to Block: go to Security &amp;gt; Settings, edit the Cloudflare Managed Ruleset, search for CVE-2026-114938 and set the rule action to Block. Alternatively, you can follow the link to &lt;a href="https://radar.cloudflare.com/zero-wire/java4shell#cloudflare-coverage"&gt;&lt;span style="text-decoration:underline"&gt;review your configuration on the Zero Wire&lt;/span&gt;&lt;/a&gt; briefing.&lt;/p&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;Rule description&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;Rule ID&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;Java4Shell - Malformed Base64 Header - CVE-2026-114938&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;5de9b20a45ea45d3841919ab4d718bf4&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;Java4Shell - Malformed Base64 Query Value - CVE-2026-114938&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;46bb4172813e471ea62d31c02337b51d&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;Java4Shell - Malformed Base64 Body Value - CVE-2026-114938&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;d4dc3f71f1bc44a0811ae570e5e5836c&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;Java4Shell - Malformed Base64 Path Segment - CVE-2026-114938&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;0dceaf0684b54fd0b085fcfb6fd6f152&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;Java4Shell - Malformed Base64url JWT Component - CVE-2026-114938&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;0ddd0eb664a040779f2f19065a25d991&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;Java4Shell - Malformed Base64 WebAuthn Value - CVE-2026-114938&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;4fce1ea79a614c07a27348d167d74ebb&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;We are working on a rule for the Cloudflare Free Managed Ruleset and will update this post when it is available.&lt;/p&gt;&lt;p&gt;A WAF can block the exploit when the malformed Base64 arrives in an HTTP request that passes through Cloudflare. It cannot block every path to the vulnerable decoder, including:&lt;/p&gt;&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Encoded or nested data.&lt;/strong&gt; The Base64 value may be wrapped inside another encoding or compressed format that the application unpacks before decoding.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Non-HTTP protocols.&lt;/strong&gt; Some affected products, such as the Apache Kafka broker, accept traffic over their own protocols.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Outbound connections.&lt;/strong&gt; Calif also shared a client-side exploit: a Java program that opens a TLS connection to a malicious server can be compromised, even if it exposes no service of its own.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Traffic that bypasses Cloudflare.&lt;/strong&gt; This includes internal traffic between services.&lt;/li&gt;&lt;/ul&gt;&lt;h3&gt;Adding defense-in-depth with WAF attack score&lt;/h3&gt;&lt;p&gt;While the managed rule is the primary way to block malformed Base64 triggers at the edge, &lt;a href="https://developers.cloudflare.com/waf/detections/attack-score/"&gt;&lt;span style="text-decoration:underline"&gt;Cloudflare WAF Attack Score&lt;/span&gt;&lt;/a&gt; (and specifically its remote code execution sub-score cf.waf.score.rce available on Enterprise plans) can offer an additional, complementary layer of protection.&lt;/p&gt;&lt;p&gt;Because CVE-2026-114938 (Java4Shell) is a binary heap-corruption vulnerability, an attacker rarely achieves full, reliable remote code execution with a single 65-byte (or 129-byte) trigger string alone. On the wire, that initial trigger looks like an opaque, malformed Base64 string containing heap-corruption bytes rather than traditional web-layer injection syntax. As a result, machine learning models trained on application-layer injection patterns will not flag the raw Base64 trigger in isolation.&lt;/p&gt;&lt;p&gt;Instead, turning a bounded JVM heap overflow into remote code execution over HTTP almost always requires a multi-stage or multi-parameter exploit chain, which creates more fingerprints that WAF Attack Score can inspect and flag, including:&lt;/p&gt;&lt;ul&gt;&lt;li&gt;Heap Grooming and Triggering: To corrupt a predictable adjacent object on the JVM heap (such as a String or byte[] length header), attackers often send repetitive parameters or headers alongside the malformed Base64 payload to shape memory layout before triggering the out-of-bounds write.&lt;/li&gt;&lt;li&gt;Second-Stage Payloads: Once heap corruption gives the attacker control over execution flow or object references, the exploit still needs commands, scripts, or Java gadgets to run. If an exploit chain pairs the initial heap-corruption trigger with a second-stage payload such as shell execution primitives (/bin/sh -c, cmd.exe, reverse-shell strings) or Java class-loading gadgets (java.lang.Runtime, ProcessBuilder, serialized object streams) tucked into another header, query parameter, or request body, cf.waf.score.rce can detect and score that secondary payload as malicious.&lt;/li&gt;&lt;li&gt;Post-Exploitation Activity: Even if an initial heap-read or corruption request slips past edge filters, subsequent HTTP requests attempting to interact with an in-memory webshell or pass OS commands to the compromised JVM remain directly visible to WAF Attack Score.&lt;/li&gt;&lt;/ul&gt;&lt;h2&gt;Deploy protections and patch&lt;/h2&gt;&lt;p&gt;Because sophisticated in-memory exploits can still execute raw shellcode or manipulate bytecode without ever sending plaintext shell commands over HTTP, WAF Attack Score should be used alongside explicit Base64 rules and JVM patching.&lt;/p&gt;&lt;p&gt;You can find more information on how to deploy Managed rules and attack score in &lt;a href="https://developers.cloudflare.com/waf/get-started/"&gt;&lt;span style="text-decoration:underline"&gt;our WAF guide&lt;/span&gt;&lt;/a&gt;, but in a nutshell:&lt;/p&gt;&lt;p&gt;1. Set the CVE-2026-114938 rule in the Cloudflare Managed Ruleset (Pro plan and above) to Block. It is enabled in Log mode by default, so review its matches in Security Events first. Use the links on the Cloudflare Zero Wire page to review your rules status.&lt;/p&gt;&lt;p&gt;2. Layer &lt;a href="https://developers.cloudflare.com/waf/get-started/#2-create-custom-rule-based-on-waf-attack-score"&gt;&lt;span style="text-decoration:underline"&gt;Attack Score&lt;/span&gt;&lt;/a&gt; to get ML-based remote code execution (RCE) detection: create a custom rule blocking or challenging requests with a low RCE attack score (for example, cf.waf.score.rce le 20 on Enterprise plans, or cf.waf.score.class eq &amp;quot;attack&amp;quot; on Business plans) to catch multi-stage exploit chains and post-exploitation command traffic.&lt;/p&gt;&lt;p&gt;3. Remediate at runtime: Upgrade to patched OpenJDK builds (or set -XX:+UnlockDiagnosticVMOptions -XX:-UseBASE64Intrinsics as a temporary workaround) to eliminate the vulnerable AVX-512 code path entirely. Follow the &lt;a href="https://openjdk.org/groups/vulnerability/advisories/2026-11-17"&gt;&lt;span style="text-decoration:underline"&gt;OpenJDK advisory&lt;/span&gt;&lt;/a&gt; and &lt;a href="https://www.oracle.com/security-alerts/cspunov2026.html"&gt;&lt;span style="text-decoration:underline"&gt;Oracle&amp;#x27;s Critical Patch Update&lt;/span&gt;&lt;/a&gt; and install your Java vendor&amp;#x27;s fixed release as soon as possible. For a prompt you can give an AI agent to inventory your Java runtimes, see the &lt;a href="https://radar.cloudflare.com/zero-wire/java4shell"&gt;&lt;span style="text-decoration:underline"&gt;Java4Shell page on Cloudflare Zero Wire&lt;/span&gt;&lt;/a&gt;. &lt;/p&gt;&lt;h2&gt;Impact on Cloudflare infrastructure&lt;/h2&gt;&lt;p&gt;Cloudflare also runs Java, so when &lt;a href="https://calif.io/java4shell/"&gt;&lt;span style="text-decoration:underline"&gt;Java4Shell&lt;/span&gt;&lt;/a&gt; was disclosed we checked our own systems. The vulnerability can only be triggered in specific hardware configurations, namely a x86-64 processor that supports AVX-512 VBMI, so a system is exposed only when both are true. Our investigation found that the majority of our Java workloads are not scheduled on vulnerable systems; we took immediate action to protect the remainder.&lt;/p&gt;&lt;p&gt;About an hour after the patches were published, we began rolling out a JVM startup option that turns off the accelerated Base64 routine containing the bug on all Java workloads, so decoding falls back to the standard implementation. To be safe, we are rolling out our patched configuration to all machines, regardless of hardware as a precaution. We have seen no indication so far that Java4Shell was exploited on Cloudflare infrastructure.&lt;/p&gt;&lt;h2&gt;Update every Java runtime now&lt;/h2&gt;&lt;p&gt;Java4Shell turns a performance optimization in the Java runtime into a path to remote code execution, and with technical details now public, we expect exploit attempts to follow quickly. The fix is to update every Java runtime and restart the services that use it. While you patch, review the new managed rule&amp;#x27;s matches and switch it to Block if you are on a paid plan and use attack score to catch remote code execution payloads that signatures may miss. &lt;/p&gt;&lt;p&gt;Our WAF analysts will continue to update protections as new techniques emerge. Follow the &lt;a href="https://developers.cloudflare.com/waf/change-log/changelog/"&gt;&lt;span style="text-decoration:underline"&gt;WAF changelog&lt;/span&gt;&lt;/a&gt; for rule updates and the &lt;a href="https://radar.cloudflare.com/zero-wire/java4shell"&gt;&lt;span style="text-decoration:underline"&gt;Java4Shell page on Cloudflare Zero Wire&lt;/span&gt;&lt;/a&gt; for the latest on this vulnerability.&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>cloudflare-blog</ore:sourceId>
      <ore:sourceName>Cloudflare Blog</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://blog.cloudflare.com/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://blog.cloudflare.com/rss/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://blog.cloudflare.com/java4shell-waf-protection/</ore:originalUrl>
      <ore:upstreamId>01M7QERD06VJ8ESJENBCYJESX5</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hermes-agent-releases:6e161f9aa49fba374353f5fe534772d6</id>
    <title>Hermes Agent canary v0.23.2+canary.20261118T064620Z</title>
    <updated>2026-11-18T07:55:35Z</updated>
    <published>2026-11-18T07:55:35Z</published>
    <link rel="alternate" href="https://github.com/NousResearch/hermes-agent/releases/tag/v0.23.2%2Bcanary.20261118T064620Z" />
    <link rel="via" href="https://api.github.com/repos/NousResearch/hermes-agent/releases" />
    <category scheme="urn:ore-news:sources" term="hermes-agent-releases" label="Hermes Agent GitHub Releases" />
    <author>
      <name>Hermes Agent GitHub Releases</name>
    </author>
    <source>
      <id>urn:ore-news:source:hermes-agent-releases</id>
      <title>Hermes Agent GitHub Releases</title>
      <link rel="alternate" href="https://github.com/NousResearch/hermes-agent/releases" />
      <link rel="via" href="https://api.github.com/repos/NousResearch/hermes-agent/releases" />
    </source>
    <content type="text"># Hermes Agent v0.23.2+canary.20261118T064620Z (v0.23.2+canary.20261118T064620Z)

**Release Date:** November 18, 2026

&lt;!-- HERMES_BUILDS_TABLE --&gt;
## Downloads

### Hermes Desktop

| OS | Architecture | Download |
|---|---|---|
| macOS | Apple Silicon (M-series) | [DMG](https://hermes-assets.nousresearch.com/releases/tag/v0.23.2%2Bcanary.20261118T064620Z/HermesBundled-0.23.2%2Bcanary.20261118T064620Z-mac-arm64.dmg) |
| Windows | x86 (64-bit) | [MSIX](https://hermes-assets.nousresearch.com/releases/tag/v0.23.2%2Bcanary.20261118T064620Z/HermesBundled-0.23.2%2Bcanary.20261118T064620Z-win-x64.msix) |
| Windows | ARM (arm64 / aarch64) | [MSIX](https://hermes-assets.nousresearch.com/releases/tag/v0.23.2%2Bcanary.20261118T064620Z/HermesBundled-0.23.2%2Bcanary.20261118T064620Z-win-arm64.msix) |

### Native install/chat smoke

Download availability is independent of smoke status. Each result covers all native legs in that format group. Linux bundles are disabled; unsigned Store envelopes are not install-smoked. No-upload dry tags have no download handoff and are not smoke-qualified.

| Packages | Smoke status |
|---|---|
| macOS DMG + ZIP (arm64) | Passed |
| Windows MSIX (arm64) | Passed |
| Windows MSIX (x64) | Passed |
&lt;!-- /HERMES_BUILDS_TABLE --&gt;

## ✨ Features

- Models): support GPT-6.2 Astra and Sol ([`786314ce`](https://github.com/NousResearch/hermes-agent/commit/786314cef191e1cda1b5842fd1973e45697655ff)) — @vortexopenclaw
- Image_gen): GPT Image 2.6 Flare and Sunburst join the FAL catalog ([`8f2c6064`](https://github.com/NousResearch/hermes-agent/commit/8f2c6064fa80f3b9b0bc4965ae6f409da4415a21))
- Plugin-catalog: add barrier-shield, chaos-takens, eigen ([`4841eebc`](https://github.com/NousResearch/hermes-agent/commit/4841eebcb15dbd599bb5522410d31a675678bda0)) — @arjunbagga-xyz
- Plugin-catalog: add axiom (Neural-Symbolic Conservation-Law Verifier &amp; SMT Ce) ([`2bff853a`](https://github.com/NousResearch/hermes-agent/commit/2bff853ac794dfbfd862472a8d0480478bfe0639)) — @arjunbagga-xyz
- Hermes-safeguard plugin configuration ([`781cc939`](https://github.com/NousResearch/hermes-agent/commit/781cc93941ed220a8c362c23fef080dfd2f9ef19)) — @robberdom
- Catalog: add safari plugin ([`1addeb7b`](https://github.com/NousResearch/hermes-agent/commit/1addeb7b5167d1980072055235dc5cb461b520dd)) — @Thorballer
- Plugin-catalog): add relatedb-memory ([`7a324936`](https://github.com/NousResearch/hermes-agent/commit/7a324936fa404c918d4d9e9b703dd763d76919bc)) — @loheander
- Catalog): add Ukrainian language pack for Hermes Agent ([`593f35c6`](https://github.com/NousResearch/hermes-agent/commit/593f35c6e62f564b41820b6574dc1cba3dbddb44)) — @angusvka-spec
- Plugin-catalog): add scansift ([`97b95eea`](https://github.com/NousResearch/hermes-agent/commit/97b95eeaa12366f9cbbc5d5bfb56b916217999f7)) — @rodricksz4h5
- Plugin-catalog): add covsift ([`73b0fc6e`](https://github.com/NousResearch/hermes-agent/commit/73b0fc6e9981f6edc3d3d5c13a9916b1402545d6)) — @rodricksz4h5
- Session_rules): pure session rules shared by callers and backends ([`5bf76580`](https://github.com/NousResearch/hermes-agent/commit/5bf7658044cb48e2cf966694483f389a0b7978ac)) — @yoniebans
- Persistence): housekeeping and maintenance operations ([`84035b4c`](https://github.com/NousResearch/hermes-agent/commit/84035b4c0913999df99311c4a572c9fbc82b2cee)) — @yoniebans
- Persistence): worker execution and delegation ledger operations ([`d333146d`](https://github.com/NousResearch/hermes-agent/commit/d333146d3f3de3f92f1682f8ac8932f293a6adf0)) — @yoniebans
- Persistence): gateway routing and delivery operations ([`db2296e1`](https://github.com/NousResearch/hermes-agent/commit/db2296e189ebd79efb49f279808b9e89ba9c6a9e)) — @yoniebans
- Persistence): session authority and binding operations ([`516f3c31`](https://github.com/NousResearch/hermes-agent/commit/516f3c3185a2849a7bdba7b236baf2aa7a94d3aa)) — @yoniebans
- Persistence): conversation storage operations ([`f1fd5674`](https://github.com/NousResearch/hermes-agent/commit/f1fd567463e63c64810c93248833770e8ea496bb)) — @yoniebans
- Persistence): the storage interface: core records, errors, profile scope and awaitable view ([`4a66e4b1`](https://github.com/NousResearch/hermes-agent/commit/4a66e4b1cdc624e2c2a9a1b44a504ac7ea9f5f24)) — @yoniebans
- Plugin-catalog): add sound-cut ([`ac071094`](https://github.com/NousResearch/hermes-agent/commit/ac071094451a448471b6412a8985422805e84b65)) — @TakeshiTGAL
- Plugin-catalog): add lazybird ([`5d1a1f2b`](https://github.com/NousResearch/hermes-agent/commit/5d1a1f2b0c4b6686ee7351b5f121a6a13abe28b2)) — @elyssiaamani
- Plugin-catalog): bump policy-backtester to 0.5.3 (c2a15a2) ([`d30b0a2f`](https://github.com/NousResearch/hermes-agent/commit/d30b0a2feb0cb9f71e9e9d0eb45e3913e6c5fc22)) — @noviceadam666
- Plugin-catalog: add hermes-voice-gateway ([`b8702d10`](https://github.com/NousResearch/hermes-agent/commit/b8702d109be9fae0b7ade80487db04739c34bde0)) — @SRai22
- Plugin-catalog): elm 0.4.0-preview (auto mode, /elm private) ([`8e02eb48`](https://github.com/NousResearch/hermes-agent/commit/8e02eb48318ddc7c2fe7d3a0530cef4b32120cb9)) — @Miawd3
- Plugin-catalog: add hermes-axiom-coach 0.1.0 ([`98ff066e`](https://github.com/NousResearch/hermes-agent/commit/98ff066ecebe813efb6623eb75d24366b78fa66e)) — @percyhendrux123-prog
- Plugin-catalog): update worktable plugin to 0.1.4 ([`6e0877da`](https://github.com/NousResearch/hermes-agent/commit/6e0877dab0afe793e638a51e36b0cd9e8816d122)) — @obkaro
- Plugin-catalog): add sleek ([`262b063e`](https://github.com/NousResearch/hermes-agent/commit/262b063e58eb005d03da71007022dbb860ca1a4c)) — @stefanofa
- Plugin-catalog): add music-listener (community) ([`09bc3b02`](https://github.com/NousResearch/hermes-agent/commit/09bc3b020e8182864f3bc65c4641bfcbeaac7f70)) — @JPeetz
- Plugin-catalog): add proactive-continuity plugin ([`1bb1f4ed`](https://github.com/NousResearch/hermes-agent/commit/1bb1f4edbb8158322f13fc841e68d1c0bb0ffb4e)) — @iknowterry
- Hermes-baikal to the plugin catalog ([`b0ba2b52`](https://github.com/NousResearch/hermes-agent/commit/b0ba2b52a56fe3fdaf75d3e8fd301d2cc6855a21)) — @tedlefter
- Hermes-regress plugin catalog entry ([`87b55995`](https://github.com/NousResearch/hermes-agent/commit/87b55995474b5ac5a91d6411d2a47234ee02451b)) — @harishkotra
- Plugin-catalog: re-pin glide to 5421c70a (CI-built dist with review fixes); mark gateway-method features inactive; add /fleet and /intel ([`3ee103f8`](https://github.com/NousResearch/hermes-agent/commit/3ee103f8a4c60ecb3491b4b14c9d49ee56280f60)) — @kvnloo
- Plugin-catalog): pin glide 4bc0b5f (fresh-install e2e green on GitHub runners) ([`ae7704a4`](https://github.com/NousResearch/hermes-agent/commit/ae7704a4f67341ce87b224ec4150945ce998358c)) — @kvnloo
- Plugin-catalog): pin glide d486f0c (documents live helper lanes; code identical to 68d9675) ([`978eb4bb`](https://github.com/NousResearch/hermes-agent/commit/978eb4bb50d624a77d316e49919020616a5b4352)) — @kvnloo
- Plugin-catalog): pin glide 68d9675 (live helper lanes, rebuilt bundle) ([`e8019229`](https://github.com/NousResearch/hermes-agent/commit/e8019229fdc55405f67bc6dbfc99910cf0d0f849)) — @kvnloo
- Plugin-catalog): pin glide ccfcd91 and describe /glide focus ([`92eaa1e6`](https://github.com/NousResearch/hermes-agent/commit/92eaa1e6bd88b406ec126fe86c56ad5a9f137a48)) — @kvnloo
- Plugin-catalog): describe glide fully and pin dc2b19a ([`b9ff1ba1`](https://github.com/NousResearch/hermes-agent/commit/b9ff1ba1a689a7846b03910cab0fef024b59379d)) — @kvnloo
- Plugin-catalog): add glide (Tern UI + /glide in one install) ([`c592a441`](https://github.com/NousResearch/hermes-agent/commit/c592a44137d13ace6633f5aa16b844ed84db7d2a)) — @kvnloo
- Plugin-catalog): bump reset-rescue to 0.2.0 ([`f65041a9`](https://github.com/NousResearch/hermes-agent/commit/f65041a9db949a55227db4e5042a041646d13316)) — @bwoliveira
- Plugin-catalog: add barrier-shield (Continuous Control-Barrier Function (CBF) Quadrati) ([`f28259a8`](https://github.com/NousResearch/hermes-agent/commit/f28259a8dc818cd15c7bf56cd058c334dad16998)) — @arjunbagga-xyz
- Plugin-catalog: add transducer (Ultrasonic FMCW Sonar &amp; Vibrometer) ([`d5a08e01`](https://github.com/NousResearch/hermes-agent/commit/d5a08e01bcecf8c395942e9da554571a65eae11d)) — @arjunbagga-xyz
- Plugin-catalog: add system-one 0.3.2 ([`6e023dd5`](https://github.com/NousResearch/hermes-agent/commit/6e023dd56571e1e1e38de1bb3ebe6d270af45234)) — @salismt
- Catalog): update Apparent to 0.4.0 with recording handoff ([`6c1410b2`](https://github.com/NousResearch/hermes-agent/commit/6c1410b2d1d8ac28666f0e563001343d0953bf03)) — @simonvanlaak
- Catalog): refresh live-video with a title, images and 1.3.8 ([`0119f900`](https://github.com/NousResearch/hermes-agent/commit/0119f900cbc1936bcc8bc4c61a374254cd7eab4a)) — @dacheah
- Plugin-catalog): add alphagrowth plugin ([`7a05fc61`](https://github.com/NousResearch/hermes-agent/commit/7a05fc6105c26156168b3934327728726df7479a)) — @ardey26
- Plugin-catalog: add 2pr (2pr.io LinkedIn MCP connector) ([`9d8d504e`](https://github.com/NousResearch/hermes-agent/commit/9d8d504e0739dcdd2f4fb8191057ed0824d38e22)) — @midovislam
- Panoptes to the plugin catalog ([`b91f0563`](https://github.com/NousResearch/hermes-agent/commit/b91f0563f6ad6c99db2a8d4350566a37ba1610cd)) — @huwhitememes
- Plugin-catalog: add token-stats ([`7454a90a`](https://github.com/NousResearch/hermes-agent/commit/7454a90a6ee27327ac4ad08847d20e537d19e47a)) — @amitamit10
- Plugin-catalog): add marcora ([`beacfd43`](https://github.com/NousResearch/hermes-agent/commit/beacfd43d1389ef0c2ef1b9cf4b921a902354a11)) — @ccromp
- Plugin-catalog): add aigrow model provider ([`6580089b`](https://github.com/NousResearch/hermes-agent/commit/6580089b43e9e01d7639f0ffa2d5336997a18765)) — @guglielmo-io
- Plugin-catalog): add twinpost ([`044a6baf`](https://github.com/NousResearch/hermes-agent/commit/044a6bafd18c07e72fa844ab06346824a97a9dd8)) — @MelMayssonOwen
- Catalog: add aipg-community (AI Power Grid model provider) ([`3295ec33`](https://github.com/NousResearch/hermes-agent/commit/3295ec338815fd992d035d84b2aeec20764992bb)) — @speteai
- Catalog: add hermes-guests 0.1.0 ([`4a8d97e8`](https://github.com/NousResearch/hermes-agent/commit/4a8d97e84b1e99cd07403310833d0d1f48386189)) — @d8joseph
- Catalog): add azure-mai-image ([`600f276d`](https://github.com/NousResearch/hermes-agent/commit/600f276d5c53ff1a07ddd6f199472656615b05fa)) — @joescars
- Catalog: add hermes-compute-priority 0.3.2 ([`6c4126d7`](https://github.com/NousResearch/hermes-agent/commit/6c4126d7f753da872ae09d075126476af8c0898c)) — @atostivint
- Plugins): bump rh-preflight to 0.5.8 ([`adfaeedc`](https://github.com/NousResearch/hermes-agent/commit/adfaeedcea6feac2c40ce89130394b6e312b9517)) — @quotumorg
- Plugins): bump rh-preflight to 0.5.7 ([`f8aa9c83`](https://github.com/NousResearch/hermes-agent/commit/f8aa9c83b4df19252835f7e3d606843973df23b2)) — @quotumorg
- Plugins): bump rh-preflight to 0.5.6 ([`d9dd75ed`](https://github.com/NousResearch/hermes-agent/commit/d9dd75ed3d58ed65f4dd092972007b73701cc7df)) — @quotumorg
- Plugin-catalog: add pepbank-peptide-research ([`f03cd671`](https://github.com/NousResearch/hermes-agent/commit/f03cd6712f433dd76be3e0c9f4256c5cf20c34b6)) — @BadTechBandit
- Plugin-catalog: add chime-scheduler (Chime Scheduler, LinkedIn post scheduler) ([`b088b612`](https://github.com/NousResearch/hermes-agent/commit/b088b612cb5409f9b093b65cd0f2fd8d3d87ddb4)) — @aliHafizji
- Plugin-catalog): add shiwake-ai ([`5c3fb04b`](https://github.com/NousResearch/hermes-agent/commit/5c3fb04bf109204e144677945396baec2b69ab7f)) — @zchking
- Plugin-catalog): add paperlesson plugin ([`02103366`](https://github.com/NousResearch/hermes-agent/commit/0210336663c50e32e0d9e1043306087af78de6cf)) — @AbigailDavised
- Eventmem memory provider ([`b5fa89dc`](https://github.com/NousResearch/hermes-agent/commit/b5fa89dc55db23794d01c31c669900812e738e07)) — @wackyju2-beep
- Plugin-catalog: add chereda — obligation loops in the desktop app ([`c74934f0`](https://github.com/NousResearch/hermes-agent/commit/c74934f0ead0152ca53a9d679d4abdb96f03fc07)) — @kostyk348
- Catalog: add hermes-cinema ([`272c2084`](https://github.com/NousResearch/hermes-agent/commit/272c2084a57340de8bea689a5c79b3bd8c4faf04)) — @Tormen28
- Plugin-catalog: add omnisight (Multi-Surface Spatial Vision &amp; AST Linking) ([`a33317cd`](https://github.com/NousResearch/hermes-agent/commit/a33317cd8c84c7aef97fe7113c7acf67437217db)) — @arjunbagga-xyz
- Catalog: add rubal-oracle community plugin ([`d6e860fc`](https://github.com/NousResearch/hermes-agent/commit/d6e860fc8a6b74fcec093622b5bea5b5278ea8be)) — @X0EF
- Plugin-catalog: add clotho ([`619ad767`](https://github.com/NousResearch/hermes-agent/commit/619ad767af19d288575b1d8213da93fb8f4e4aac)) — @NicWeinbrecht
- Plugin-catalog): add paintcolormatcher plugin ([`748e6e59`](https://github.com/NousResearch/hermes-agent/commit/748e6e591a42b5f921d1c2a0ed5830f668a1502c)) — @AbigailDavised
- Plugin-catalog): add checkchinatransit plugin ([`df0a7386`](https://github.com/NousResearch/hermes-agent/commit/df0a7386c8696c950d40257ea888d8ca224553a1)) — @AbigailDavised
- Plugin-catalog): listeningkit-log re-pinned to 06178006 ([`a962fa1a`](https://github.com/NousResearch/hermes-agent/commit/a962fa1a5054f62567b25c5cd6e1ce5e8646c2ac)) — @matthewdonsemail-lab
- Plugin-catalog): listeningkit-log re-pinned to fe8bd3c9 after review ([`f7cb81cc`](https://github.com/NousResearch/hermes-agent/commit/f7cb81ccc85a2bcfd1feabe9b8fdac1ae4c5627a)) — @matthewdonsemail-lab
- Plugin-catalog): listeningkit-log moves to matthewdonsemail-lab/log (hermesPlugin/) ([`854d5d9c`](https://github.com/NousResearch/hermes-agent/commit/854d5d9c5c77f0ee3a007d19c70c83d00a93aa21)) — @matthewdonsemail-lab
- Plugin-catalog): add dafeiyu-companion plugin ([`55173e02`](https://github.com/NousResearch/hermes-agent/commit/55173e0240c0b5c89b66a48a0533295b9d7a3232)) — @rayyichen310
- Catalog: update Finix to verified public-SDK backup implementation ([`664c41f1`](https://github.com/NousResearch/hermes-agent/commit/664c41f1d58f1d4bc0f7caa321c907d12ffc435d)) — @web3blind
- Plugin-catalog: add ghostbox (Speculative Shadow Sandbox) ([`9455c756`](https://github.com/NousResearch/hermes-agent/commit/9455c75639eb34677c1a7c670e041e56709a3707)) — @arjunbagga-xyz
- Catalog: add rule-injector ([`46cf0e89`](https://github.com/NousResearch/hermes-agent/commit/46cf0e8906842bc8f0bd6c90a8b216bf5ce38045)) — @klautimus
- Theta-edge-node plugin catalog entry ([`a2429a9a`](https://github.com/NousResearch/hermes-agent/commit/a2429a9a0d4a2661495255f18a90fad41259ed85)) — @bonesnasty
- Plugin-catalog): add timetopost ([`da056981`](https://github.com/NousResearch/hermes-agent/commit/da05698152e978a6e7ec784a1c37d84467889803)) — @MelMayssonOwen
- Catalog): add laya-oneshot ([`d4aab172`](https://github.com/NousResearch/hermes-agent/commit/d4aab172f222b96b42e227e360426edfeab57056)) — @gergeisabo
- Plugin-catalog): withdraw 1guy (author request) ([`4f33931f`](https://github.com/NousResearch/hermes-agent/commit/4f33931f5f414d51da554a9800fa5f6c8982a686)) — @jrezmo

## 🔧 Improvements

- Clean: the append case pins that a live compression lock never fences an append ([`b636d6e6`](https://github.com/NousResearch/hermes-agent/commit/b636d6e6ed4f8d45962c76fceb119303967caa67)) — @yoniebans
- Plugins: update Subnano to 0.3.65 ([`8ac9ac96`](https://github.com/NousResearch/hermes-agent/commit/8ac9ac96fbd650b86ebea85d79d1c4f347f2c05a)) — @madsb
- Catalog(nexus): update pin to 0.22.53 and disclose the session-end and withdraw changes ([`d9c7133f`](https://github.com/NousResearch/hermes-agent/commit/d9c7133f070ff1f1442a74ed2b6a91b6a7c9b009)) — @Neboy72
- Catalog(nexus): update pin to 0.22.52 and disclose the four releases since 0.22.48 ([`c5e32dd3`](https://github.com/NousResearch/hermes-agent/commit/c5e32dd39444ea52104f04ad227e65bfae0ea384)) — @Neboy72
- SHA for hermes-safeguard plugin ([`b8d837f1`](https://github.com/NousResearch/hermes-agent/commit/b8d837f139d701f3a35e71931995d5a957428828)) — @robberdom
- Persistence): running is the only in-flight delegation state ([`d2cbdfa3`](https://github.com/NousResearch/hermes-agent/commit/d2cbdfa3ad1ec97eaa3f47e8e0dd888bb272bbd5)) — @yoniebans
- Pantheon catalogue to 1.0.14 ([`6d2946e3`](https://github.com/NousResearch/hermes-agent/commit/6d2946e30f05e243c621bc15ff212481189267b3)) — @mrdavey
- Hermes-regress: pin to README update sha ([`c1c14fc5`](https://github.com/NousResearch/hermes-agent/commit/c1c14fc5b49f3759fc219e2d681d361230ff16c2)) — @harishkotra
- Catalog: update barrier-shield sha to 88c903a ([`4e7fd50b`](https://github.com/NousResearch/hermes-agent/commit/4e7fd50b4695c13c29fb0074a0b286e37dc5ea82)) — @arjunbagga-xyz
- Catalog: update transducer sha to 44b3d48 ([`12823592`](https://github.com/NousResearch/hermes-agent/commit/1282359279828c671942d85637fd1878c35e6541)) — @arjunbagga-xyz
- Plugins: update Subnano to 0.3.64 ([`17a87f84`](https://github.com/NousResearch/hermes-agent/commit/17a87f84f08e757b81f528466cddcfae97dd7204)) — @madsb
- Kumpay-aeo pin to EUR-priced package ([`bd72cb0c`](https://github.com/NousResearch/hermes-agent/commit/bd72cb0c95c0f3bcfb16edfa6cd7d908043fb272)) — @kumpayinteractive-sudo
- Pin OwnMachine catalog update to v1.1.1 release ([`644a35d9`](https://github.com/NousResearch/hermes-agent/commit/644a35d9eeea5305d9ca66605d8005d8378e54a3)) — @rbur0425
- OwnMachine to v1.1.0 with Windows KVM support ([`26efb221`](https://github.com/NousResearch/hermes-agent/commit/26efb22189011528f38456565b60291b410eb445)) — @rbur0425
- Catalog: update Living Spaces to 0.1.2 ([`aa19bd46`](https://github.com/NousResearch/hermes-agent/commit/aa19bd466898196641ca830a210e5c2061e467b5)) — @akinduroifedayo
- Catalog: update omnisight sha to 2254dcb ([`8cb6e2f9`](https://github.com/NousResearch/hermes-agent/commit/8cb6e2f9ae34a751157a97c7ea63ef2d3faba67f)) — @arjunbagga-xyz
- Catalog: update ghostbox sha to 1515748 ([`ddb366b6`](https://github.com/NousResearch/hermes-agent/commit/ddb366b646d1ddd6fbd6f888102a6c0709e59f0d)) — @arjunbagga-xyz
- Plugin-catalog(opensop): re-pin 7fe934a and update disclosure ([`2b54584b`](https://github.com/NousResearch/hermes-agent/commit/2b54584ba7f4fbef7503b414efd21410ce10cb13)) — @Chosen9115

## 🐛 Bug Fixes

- Models): keep undiscovered Codex choices out of Desktop and ACP ([`864fd57c`](https://github.com/NousResearch/hermes-agent/commit/864fd57c5989e97a503b7c92aa622d581f9e6796)) — @vortexopenclaw
- Models): require verified Codex discovery for GPT-6.2 choices ([`444a6b86`](https://github.com/NousResearch/hermes-agent/commit/444a6b8644c1926d23beb41bc0147a328070f157)) — @vortexopenclaw
- Models): honor GPT-6.2 Fast rates and Codex eligibility ([`1a831506`](https://github.com/NousResearch/hermes-agent/commit/1a8315068220eb9ebf79f5332f3b666fb9d94cef)) — @vortexopenclaw
- Models): keep the Codex fallback available on free plans ([`a312aea1`](https://github.com/NousResearch/hermes-agent/commit/a312aea1ceadd00ea756b380ed20cf6a9ef4c91d)) — @vortexopenclaw
- Models): keep implicit OpenAI defaults cost-safe ([`e3a4eb8b`](https://github.com/NousResearch/hermes-agent/commit/e3a4eb8becf33e1f565535b66b8f35256e402f46)) — @vortexopenclaw
- Plugin-catalog): pin scope-recall 4.0.4 from its new repository ([`67e4d22d`](https://github.com/NousResearch/hermes-agent/commit/67e4d22d83b242ecfb2807ed39e9696ba1b1b0d5)) — @c410979729-bit
- Plugin-catalog): move scope-recall to its new repository ([`b803c323`](https://github.com/NousResearch/hermes-agent/commit/b803c32352e3bbfa3299ac89c5d04b7f2ae8024d)) — @c410979729-bit
- Deps): bump tornado 6.6 -&gt; 6.6.1 (low, GHSA-5cjw-f85j-cv6r) ([`7d54092e`](https://github.com/NousResearch/hermes-agent/commit/7d54092e781ac6c2432021ee2c999106e2cadb2f)) — @c2h5oh
- Codex): allow profile opt-out from zstd Responses requests ([`d6f73ca9`](https://github.com/NousResearch/hermes-agent/commit/d6f73ca99a72ba7c12c8ef8a2aae4bc0f1c832c9)) — @kvnloo
- Curator): fsync a skills snapshot before pruning older ones ([`57e7b050`](https://github.com/NousResearch/hermes-agent/commit/57e7b050cfccd3af301bd3f0082683f7b0ee512c)) — @c2h5oh
- Gateway): /resume proves ownership from the whole stored row, chat_type included ([`00dabb5f`](https://github.com/NousResearch/hermes-agent/commit/00dabb5fe5800d26544067c01a480d28bc30de45)) — @yoniebans
- File-safety): casefold project .env basenames in the read deny ([`7d7a9705`](https://github.com/NousResearch/hermes-agent/commit/7d7a9705bfde2b7543d238398ad8a6e96baebd3a)) — @unsupportedpastels
- Desktop): regenerate the i18n key list after dropping the hub picker strings ([`56b02860`](https://github.com/NousResearch/hermes-agent/commit/56b028603e140d28ab9802e08500ad4ffb7560b7)) — @austinpickett
- Desktop): skills catalog docs button opens the skills guide, not the legacy catalog ([`f461c64a`](https://github.com/NousResearch/hermes-agent/commit/f461c64a29a3b48a9518ea5fad399ec054aa29c2)) — @austinpickett
- Web): send plugin help to documentation instead of the legacy catalog ([`b36ffe9c`](https://github.com/NousResearch/hermes-agent/commit/b36ffe9c68d09ff8dff83f02326e9a5eab63a721)) — @austinpickett
- Catalog: re-pin axiom, chaos-takens, eigen to updated review fix SHAs ([`f6a7ba71`](https://github.com/NousResearch/hermes-agent/commit/f6a7ba718270117987c0aaeefd255828ae54108f)) — @arjunbagga-xyz
- Catalog): repin voice gateway after caller isolation review ([`0d066c9e`](https://github.com/NousResearch/hermes-agent/commit/0d066c9ef66a0fee75a6709f6bcc7ee44f1d3967)) — @SRai22
- Catalog): re-pin sha to 8430658 (public-API-only imports, review fixes) ([`415dae5d`](https://github.com/NousResearch/hermes-agent/commit/415dae5d6a165bfbbe9ffd28b460bd0d3fe003a2)) — @Tranquil-Flow
- Catalog): point repo at hermes-incognito-private-mode, pin final main tip ([`de78892a`](https://github.com/NousResearch/hermes-agent/commit/de78892a08c20c7d19c37c51f03436cc760d3352)) — @Tranquil-Flow
- Plugin-catalog: breadcrumbs 0.5.0 -&gt; bundle 6c1e20d (one dispatch skill with lanes per model family; settings panel) ([`10a9a4cc`](https://github.com/NousResearch/hermes-agent/commit/10a9a4cca1ad10f596ac46da8b73b5ff0354e8fa)) — @jnorthrup
- Plugin-catalog): pin proactive-continuity to 09aae57 (Telegram menu) ([`57880e94`](https://github.com/NousResearch/hermes-agent/commit/57880e941b3dc29fb7f1477679e808e0b92c030b)) — @iknowterry
- Plugin-catalog): pin proactive-continuity to 58590f0 (Linux setup fix) ([`eff23fba`](https://github.com/NousResearch/hermes-agent/commit/eff23fba88cf84df80f797850a7ee9c589167bd7)) — @iknowterry
- Catalog: re-pin barrier-shield to updated review fix SHA ([`540e1941`](https://github.com/NousResearch/hermes-agent/commit/540e1941f810aec94d138a8007f222326c0264c5)) — @arjunbagga-xyz
- Catalog: re-pin transducer to updated review fix SHA ([`72cebd7f`](https://github.com/NousResearch/hermes-agent/commit/72cebd7fa841dfacb5c43fe8e49ee6f833764b0d)) — @arjunbagga-xyz
- Re-pin to 13e8e41 (station diagram fix in README) ([`ae46419a`](https://github.com/NousResearch/hermes-agent/commit/ae46419a007a349a5fa87a030c9eefe0fdf95634)) — @huwhitememes
- Plugin-catalog): re-pin twzrd-intel to the reviewed fixes (0.2.0) ([`54099300`](https://github.com/NousResearch/hermes-agent/commit/54099300d3a9eb396b1abc970004d38bf293ac0e)) — @twzrd-sol
- Catalog: re-pin omnisight to updated review fix SHA ([`ad1b7c03`](https://github.com/NousResearch/hermes-agent/commit/ad1b7c032ec61f8362f11ee12e58b2112b4d353e)) — @arjunbagga-xyz
- Scenemux: re-pin to review-fixed plugin tree (8492640) ([`f31d3f86`](https://github.com/NousResearch/hermes-agent/commit/f31d3f864538d8c0ba14b4dc8787798566789b98)) — @ep150de
- Catalog: re-pin ghostbox to updated review fix SHA ([`f6ab58bc`](https://github.com/NousResearch/hermes-agent/commit/f6ab58bc34d7754e0a96d93332f7f2da0c03d707)) — @arjunbagga-xyz
- Catalog: say what happens when it cannot fix it (hands the job to the agent) ([`c5119771`](https://github.com/NousResearch/hermes-agent/commit/c5119771fce4aeedf9eaa7149624933d21e7663b)) — @33hodl
- Video_gen): downscale inlined images only for providers with a body cap ([`5c4db986`](https://github.com/NousResearch/hermes-agent/commit/5c4db986bbda1a0d4c6137b654e5dd3eb6c6d07f))
- Keep the fallback notice on messaging chats and mask the failed route's key ([`3e9d42b8`](https://github.com/NousResearch/hermes-agent/commit/3e9d42b876081b0aa58010862fc4c0a16c57e60d))

## 📚 Documentation

- Ci): list windows-latest with the other GitHub-hosted runners ([`da9c2bd6`](https://github.com/NousResearch/hermes-agent/commit/da9c2bd62fa567ed0006866de022939ac14582cf)) — @BearHuddleston
- Remove the legacy /docs/skills and /docs/plugins hub pages ([`82e1b455`](https://github.com/NousResearch/hermes-agent/commit/82e1b4553dc6255e6ed399917878b5a6265ea112)) — @austinpickett
- Link the navbar and sidebar to the Hermes Marketplace ([`2e4d2366`](https://github.com/NousResearch/hermes-agent/commit/2e4d2366c56025ab190ab25116c4aeb983b6795a)) — @austinpickett
- Plugin-catalog): stop describing per-entry /docs/plugins pages in field comments ([`37b4f9a0`](https://github.com/NousResearch/hermes-agent/commit/37b4f9a07ac1fd075c4b9e1ba5fe80b84a7ab75b)) — @austinpickett
- Stop advertising legacy web catalogs during Marketplace work ([`c3952057`](https://github.com/NousResearch/hermes-agent/commit/c39520573fd1f1cfe2adb97197b363f082984468)) — @austinpickett
- Catalog): add incognito-private-mode v0.3.0 plugin entry ([`95aa598b`](https://github.com/NousResearch/hermes-agent/commit/95aa598be3ac29e42f386dcacedbc04bf9ef077e)) — @Tranquil-Flow
- Catalog): hermes-ui 1.8.1 — tilted eyes of the avatar fixed ([`c0aa9c97`](https://github.com/NousResearch/hermes-agent/commit/c0aa9c97c0e26a572f7b7c031b1e96974efe43ed)) — @Ilyassbm
- Catalog): hermes-ui 1.8.0 — pin on the docs commit with the 1.8 screenshots ([`0c03bd2b`](https://github.com/NousResearch/hermes-agent/commit/0c03bd2b51d3acbf1b273b76c524688550132c1a)) — @Ilyassbm
- Catalog): hermes-ui 1.8.0 — queued messages, one working line instead of tool rows, a look of its own ([`0ebd5786`](https://github.com/NousResearch/hermes-agent/commit/0ebd5786daba1f85f7a09494e387f0d537c04579)) — @Ilyassbm
- Catalog): hermes-ui 1.6.4 — agent questions, per-bot model picker, pictures ([`18f83033`](https://github.com/NousResearch/hermes-agent/commit/18f8303315c9bee6e3b432b89af77d03d3d0b25d)) — @Ilyassbm
- Catalog): hermes-ui 1.6.3 — the gateway's model guards reach the person ([`51c7f17f`](https://github.com/NousResearch/hermes-agent/commit/51c7f17f4221a8215f03ce998cb7768511a44d52)) — @Ilyassbm
- Catalog): hermes-ui 1.6.2 — page aligned on the validated design, model switch fixed ([`63e7a1c1`](https://github.com/NousResearch/hermes-agent/commit/63e7a1c1888ff10b4ead613e9fb30cd3741e8ff0)) — @Ilyassbm

## 🧪 Tests

- Tui): verify approval withdrawal without a wall clock ([`73466ca3`](https://github.com/NousResearch/hermes-agent/commit/73466ca3a79c85d58a0391cb9b2b891546851c2c)) — @vortexopenclaw
- Gateway): the primary-auth route case stubs the adapter's store open by its interface name ([`f54017b7`](https://github.com/NousResearch/hermes-agent/commit/f54017b7a9e5ff82a15ca389216852ba272aafe4)) — @yoniebans
- Gateway): the id-less Telegram send case reaches the ledger through its scope and holder ([`d4c1495f`](https://github.com/NousResearch/hermes-agent/commit/d4c1495f6e8865f9552d291c4b69063611d3a9fc)) — @yoniebans
- The newer tests seed and read through the storage interface instead of the legacy session store ([`d7ba9254`](https://github.com/NousResearch/hermes-agent/commit/d7ba9254866116ecdc2cd926fd5921d528d1a3f4)) — @yoniebans
- Gateway): move four more authority tests onto the persistence interface ([`3d858e6b`](https://github.com/NousResearch/hermes-agent/commit/3d858e6b92b849c731c125507afc3e863c11d4fd)) — @yoniebans
- Gateway): gateway cases over the persistence interface, part 1 of 6 ([`b7f590ed`](https://github.com/NousResearch/hermes-agent/commit/b7f590ed5678323fff732e197d874c66e6f5522e)) — @yoniebans
- Contracts): contract cases for conversation, authority, gateway and worker storage ([`7247bd02`](https://github.com/NousResearch/hermes-agent/commit/7247bd02f9a92c0caefa5ed9ba20d41902621a7c)) — @yoniebans
- Contracts): core contract cases ([`5def99d9`](https://github.com/NousResearch/hermes-agent/commit/5def99d9d6c3d1166800396162ca551bb42ad3a2)) — @yoniebans
- Contracts): reference backend and contract suite harness ([`b67b5dd7`](https://github.com/NousResearch/hermes-agent/commit/b67b5dd7a26b01c54a432dcbc6a6a6ef8607961a)) — @yoniebans

## 🏗️ Infrastructure

- Ci): run the Windows install/update legs on the standard runner ([`796a4121`](https://github.com/NousResearch/hermes-agent/commit/796a412157211b4ddc186e921ce33541c8d1a8df)) — @BearHuddleston
- Plugin-catalog): bump game-lab to 0.4.0 ([`2aa0b037`](https://github.com/NousResearch/hermes-agent/commit/2aa0b037c78d58aa73d1966cd90f62619ac65c65)) — @flabanabba8
- Catalog): re-pin nexus to the v0.22.56 release commit ([`68a2b0cf`](https://github.com/NousResearch/hermes-agent/commit/68a2b0cf8a05561522285f7b65ad257d8b5d25f8))
- Catalog): chaos-takens and eigen use the catalog schema (repo, maintainer, title, tier) ([`0d0bf5c9`](https://github.com/NousResearch/hermes-agent/commit/0d0bf5c9e7f9019d48ab1e47613fd2f7cda3cbd2))
- Catalog): review disclosure for hermes-safeguard ([`8dc3b9a2`](https://github.com/NousResearch/hermes-agent/commit/8dc3b9a24023adc4a54a90996e6dcaed86346b84))
- Catalog): review disclosure for grounder ([`40188a89`](https://github.com/NousResearch/hermes-agent/commit/40188a890f791f8ee8f4842f65c0be1ebbc35bf7))
- Plugin-catalog): bump grounder to 0.7.7 ([`a940efde`](https://github.com/NousResearch/hermes-agent/commit/a940efde32bff9820818ce1277ee358aa3681dba)) — @hdiggity
- Catalog): bump hermes-guide to 0.9.8 ([`2e6970eb`](https://github.com/NousResearch/hermes-agent/commit/2e6970ebacdf70143ed85d08655ba33ceadde77d)) — @iap
- Map contributor email for Thorballer ([`49bafb61`](https://github.com/NousResearch/hermes-agent/commit/49bafb61547582c6aedc5d0d96f49e96f94e4acc))
- Catalog): review disclosure for safari ([`0a64edbc`](https://github.com/NousResearch/hermes-agent/commit/0a64edbcea34251f5015a3fd2c6923d123d1a9ed))
- Catalog): review disclosure for relatedb-memory ([`3aad52e6`](https://github.com/NousResearch/hermes-agent/commit/3aad52e6548bf2e82e6e56e842054664d9fed3ce))
- Plugin-catalog): bump pilot to 0.3.3 ([`0f6ba9ac`](https://github.com/NousResearch/hermes-agent/commit/0f6ba9ac78e1018b4bee5a90ec2b8fac318bfdd2)) — @LangerSword
- Plugin-catalog): bump stoa to 0.24.1 ([`a381bd50`](https://github.com/NousResearch/hermes-agent/commit/a381bd50bfc05362482aa91e1628c42344a92f69)) — @jarrett-del
- Map contributor email for angusvka-spec ([`e10394b4`](https://github.com/NousResearch/hermes-agent/commit/e10394b4f3c48203af6ee1c6157297c46909a47b))
- Catalog): review disclosure for hermes-lang-uk ([`deb100f8`](https://github.com/NousResearch/hermes-agent/commit/deb100f8a1102bf4660da0b140f68c2274a41185))
- Catalog): review disclosure for credential-pool-switcher (#152944) ([#152944](https://github.com/NousResearch/hermes-agent/pull/152944))
- Plugin-catalog): update detonator to v0.3.1 ([`25e71e0f`](https://github.com/NousResearch/hermes-agent/commit/25e71e0f79107bbe59f67e5b2068bdfd930678ca)) — @shreyasudupi
- Catalog): bump caduceus to v0.3.2 ([`a39349ce`](https://github.com/NousResearch/hermes-agent/commit/a39349ce79dc62c2d899dca22d8299d68f0fd56b)) — @100yenadmin
- Map contributor email for elyssiaamani ([`9dd9421f`](https://github.com/NousResearch/hermes-agent/commit/9dd9421f1dd7be7b629873da7a42fb213d595a54))
- Catalog): merge chores for the maintainer-copied entries ([`969a0264`](https://github.com/NousResearch/hermes-agent/commit/969a0264d9d3e65fe33231ab0ac1192dd2356cb0))
- Map contributor email for SRai22 ([`9762c2f6`](https://github.com/NousResearch/hermes-agent/commit/9762c2f6507fe346d6ed5e15ea198de96ddf8b2f))
- Catalog): review disclosure for hermes-voice-gateway ([`cea72054`](https://github.com/NousResearch/hermes-agent/commit/cea72054b53af12745e7188098653d7d49f5c70e))
- Catalog): review disclosure for incognito-private-mode ([`3994649c`](https://github.com/NousResearch/hermes-agent/commit/3994649c1b36f7fe8185bbcd13616973828b144d))
- Map contributor email for mrdavey ([`54670caa`](https://github.com/NousResearch/hermes-agent/commit/54670caa57240a98c6155b4982b3911dd0b1b2bb))
- Catalog): review disclosure for pantheon ([`0ccdced9`](https://github.com/NousResearch/hermes-agent/commit/0ccdced9fbd9af63a8c4bc917dea533d14a7cfba))
- Catalog): bump hermes-adaptive-effort to 0.6.0 ([`585d8295`](https://github.com/NousResearch/hermes-agent/commit/585d82954a072cc4d4f5f770e4d7f394fe8dbd4a)) — @atostivint
- Plugin-catalog): memorybank 1.5.0 (plugin at repository top, works on Windows and macOS) ([`7de7621e`](https://github.com/NousResearch/hermes-agent/commit/7de7621ed0cac2bc4de30a740f98172232dd58e8)) — @nicholaslaldigital
- Catalog): update genealogy recipes to v1.20.0 ([`b7878beb`](https://github.com/NousResearch/hermes-agent/commit/b7878beb792bf45fb189b4765c45c83591eb15c1)) — @lazyants
- Map contributor email for JPeetz ([`8fa6b305`](https://github.com/NousResearch/hermes-agent/commit/8fa6b30563f7cda57cb34e70e75e18029f32307e))
- Catalog): review disclosure for music-listener ([`54672ab5`](https://github.com/NousResearch/hermes-agent/commit/54672ab5a8bdc4480b86431fd8488bb03ab7f2bd))
- Plugin-catalog): bump adaptlypost to 1.22.0 ([`3b23241f`](https://github.com/NousResearch/hermes-agent/commit/3b23241feb213d95b96abdd2fe7847cc463aca28)) — @TarasShyn
- Plugin-catalog): bump redreplier to 1.6.0 ([`c5bfb94d`](https://github.com/NousResearch/hermes-agent/commit/c5bfb94de4ee0dc2eafb31bd85c13b5836814e1e)) — @TarasShyn
- Catalog): review disclosure for breadcrumbs ([`52fc0956`](https://github.com/NousResearch/hermes-agent/commit/52fc09563f684e0f81d997aa5b2e4e561792ecd4))
- Catalog): review disclosure for proactive-continuity ([`9c27b53d`](https://github.com/NousResearch/hermes-agent/commit/9c27b53d2713f387790659d1b24adf4ea8a7773b))
- Map contributor email for tedlefter ([`f329af70`](https://github.com/NousResearch/hermes-agent/commit/f329af70de071cca1630c3295fbc705f553ff2b4))
- Map contributor email for harishkotra ([`691eca18`](https://github.com/NousResearch/hermes-agent/commit/691eca18f524ef4cb2595b94e54e87c7dea03acc))
- Catalog): review disclosure for hermes-regress ([`c67b0153`](https://github.com/NousResearch/hermes-agent/commit/c67b015327bee8c90e75e544b3542ae305c4302c))
- Catalog): review disclosure for glide ([`a057a719`](https://github.com/NousResearch/hermes-agent/commit/a057a7191d247959b40151b2615192c5e6706e44))
- Plugin-catalog): pin glide to 82be62d (current main) ([`d993736a`](https://github.com/NousResearch/hermes-agent/commit/d993736a68f1a87c3117a6eaf2d2ebb844398c0d)) — @kvnloo
- Map contributor email for bwoliveira ([`23fbfbfb`](https://github.com/NousResearch/hermes-agent/commit/23fbfbfbac99b1d8467347ca7d8f18f6f3e945c0))
- Catalog): bump jev-curator to v0.1.1 ([`cb224ae2`](https://github.com/NousResearch/hermes-agent/commit/cb224ae2ffcd2b91f041fa1cf6333e05a2176261)) — @anpicasso
- Catalog): review disclosure for barrier-shield ([`5587cbc5`](https://github.com/NousResearch/hermes-agent/commit/5587cbc5aa420963ac7467ed6c035098e2ab951b))
- Catalog): review disclosure for transducer ([`92b3e0d4`](https://github.com/NousResearch/hermes-agent/commit/92b3e0d4d5c7649bdcda263bb5af89e13714533d))
- Optional-mcps): drop Bitquery MCP entry, keep the plugin entry ([`f7b1cf10`](https://github.com/NousResearch/hermes-agent/commit/f7b1cf106ad0be42602ced205cdd0fe5ff5a464e)) — @divyasshree-BQ
- Catalog): bump modal plugin to 6458057 ([`5683773b`](https://github.com/NousResearch/hermes-agent/commit/5683773b6681b0d941aa880913d06d42c3c7b867)) — @andrewhinh
- Catalog): review disclosure for hermes-next-steps ([`bdb1b3f6`](https://github.com/NousResearch/hermes-agent/commit/bdb1b3f62748fc5be7407a5bca8ac2aa2ee50920))
- Catalog): pin hermes-next-steps 1.1.1 ([`bd9b1741`](https://github.com/NousResearch/hermes-agent/commit/bd9b1741ac7b05906a8871f40a5b02d39c8fe120)) — @apoapostolov
- Catalog): update hermes-egm to v0.3.0 ([`c50d91a8`](https://github.com/NousResearch/hermes-agent/commit/c50d91a8e0b718bc0c529cd474122904b7822aa0)) — @willbohn
- Catalog): review disclosure for session-flow ([`859ee4b1`](https://github.com/NousResearch/hermes-agent/commit/859ee4b10748bd350d31f03222fac901bcc5d070))
- Catalog): update Fortytwo provider to 1.1.0 ([`376b0cd6`](https://github.com/NousResearch/hermes-agent/commit/376b0cd651045d17b95eaeb229c1fb428b6e2a7f)) — @AIvashov
- Map contributor email for jacobhausler ([`16a25948`](https://github.com/NousResearch/hermes-agent/commit/16a259483e964cc51aa723715265316e25d3dddc))
- Catalog): review disclosure for hermes-workflows ([`87fa3810`](https://github.com/NousResearch/hermes-agent/commit/87fa38105130be21b9bce7dfd522f71eb28bb46b))
- Catalog): repin hermes-workflows v1.4.10 (sha aa2f4438) ([`69e25294`](https://github.com/NousResearch/hermes-agent/commit/69e252946d7731ada2683356854fec47b6f49ba2)) — @jacobhausler
- Map contributor email for kumpayinteractive-sudo ([`600cf104`](https://github.com/NousResearch/hermes-agent/commit/600cf10413cbd6767ff8f5d79be334314ef4684e))
- Catalog): review disclosure for cognee ([`d050c5dd`](https://github.com/NousResearch/hermes-agent/commit/d050c5dd3f4f1ad2b51065c2ed974f70a317c656))
- Plugin-catalog): move cognee entry to topoteretes/cognee ([`5b19b51b`](https://github.com/NousResearch/hermes-agent/commit/5b19b51b428073b6bb25bb38825d89c2d48b4356)) — @ArmagedonFlamer
- Catalog): review disclosure for apparent ([`21b396f3`](https://github.com/NousResearch/hermes-agent/commit/21b396f310a99c60383a2d1f3e750e116068e34a))
- Map contributor email for linxichen ([`8139988b`](https://github.com/NousResearch/hermes-agent/commit/8139988b1eb6d1ed330cce4d85f523ab186091f8))
- Catalog): pin live-video to the commit that shows its screenshots ([`9544a314`](https://github.com/NousResearch/hermes-agent/commit/9544a314a8487e18c0f7d524b41edbf6d9cfb282)) — @dacheah
- Plugin-catalog): skilluminati pins 9c8babd (0.2.1) ([`fd475abc`](https://github.com/NousResearch/hermes-agent/commit/fd475abc8da25e9ab9ead7ea3185cf60b63f1905)) — @yxssxn
- Catalog): update Unraid to 0.3.0 ([`51267908`](https://github.com/NousResearch/hermes-agent/commit/51267908e7bbae7c4697c84ecc70449ed4962357)) — @Anunnaki-Astronaut
- Catalog): review disclosure for ownmachine ([`67542222`](https://github.com/NousResearch/hermes-agent/commit/67542222ff55ec2b1a981a00f8f36e447c29b842))
- Plugin-catalog): update x-dashboard to v0.2.0 ([`803ee63e`](https://github.com/NousResearch/hermes-agent/commit/803ee63eb829ad15da4b2dd46d44721441b51aec)) — @omxhub
- Catalog): review disclosure for 2pr ([`fac76086`](https://github.com/NousResearch/hermes-agent/commit/fac7608640613c0bf86deec8ba9f3212058211a4))
- Plugin-catalog): bump flowsery to 1.5.0 ([`480d4999`](https://github.com/NousResearch/hermes-agent/commit/480d4999e5f96f6c7c5c4207f0650a9c8249f3df)) — @TarasShyn
- Catalog): review disclosure for deepseek-web-tools ([`c1b128c7`](https://github.com/NousResearch/hermes-agent/commit/c1b128c77de9100c292299318790205b4ac6ddf9))
- Catalog): review disclosure for aigrow ([`29768b6b`](https://github.com/NousResearch/hermes-agent/commit/29768b6bfaca1d221fbc810292011445892be43d))
- Catalog): review disclosure for twinpost ([`41805af3`](https://github.com/NousResearch/hermes-agent/commit/41805af35c95f22fe1fbd7537ab9f4bb6e83b254))
- Catalog): review disclosure for aipg-community ([`792e6355`](https://github.com/NousResearch/hermes-agent/commit/792e63554506d2c720a66872779ae90246376ac7))
- Map contributor email for joescars ([`07781311`](https://github.com/NousResearch/hermes-agent/commit/07781311e416da5cc21111ea688f58e1f29fa8c1))
- Catalog): review disclosure for azure-mai-image ([`55ee8ec4`](https://github.com/NousResearch/hermes-agent/commit/55ee8ec4e702af0024b1a2323e9aa6f66a7b0c2e))
- Plugin-catalog): bump cliproxyapi to 0.8.4 ([`35f126d6`](https://github.com/NousResearch/hermes-agent/commit/35f126d6e322184756107dc2d1e0cbf835727aa8)) — @duu261
- Catalog): review disclosure for pepbank-peptide-research ([`8d70fcc4`](https://github.com/NousResearch/hermes-agent/commit/8d70fcc4517c3912abfd2dbd6f2ddc46be5d4622))
- Catalog): review disclosure for hermes-mini ([`64037ea8`](https://github.com/NousResearch/hermes-agent/commit/64037ea86602aa3bbc6da797db409261a6f84ec6))
- Map contributor email for aliHafizji ([`68987782`](https://github.com/NousResearch/hermes-agent/commit/68987782bf50377d91400c598060f66de55e898b))
- Plugin-catalog): bump local-scout to 1.8.0 (5f95fb9) ([`f1b2a284`](https://github.com/NousResearch/hermes-agent/commit/f1b2a284d0140a502715c2c36c835aefb1977158)) — @Angerosteles
- Catalog): review disclosure for living-spaces ([`e39fb2a8`](https://github.com/NousResearch/hermes-agent/commit/e39fb2a8aaae5c40b32c8ec526d6236e4c2668ab))
- Catalog): update Living Spaces to 0.1.1 ([`ae268ddc`](https://github.com/NousResearch/hermes-agent/commit/ae268ddca62a91562466af9ab5e3e9fad79b0702)) — @akinduroifedayo
- Plugin-catalog): bump werracle-evm-guard to 1.0.2 ([`517eb6bf`](https://github.com/NousResearch/hermes-agent/commit/517eb6bf0afe4a0c216510627bd1f0397cfc7a5a)) — @pCwOrM
- Plugin-catalog): bump verifiable-math-kernel to 1.0.6 ([`924a9b05`](https://github.com/NousResearch/hermes-agent/commit/924a9b05c878d0d581c77cce83475cc437acc6dd)) — @pCwOrM
- Catalog): review disclosure for webgraft ([`6541a26e`](https://github.com/NousResearch/hermes-agent/commit/6541a26e2f6916a78bbf56647fc253ebbaa46e95))
- Catalog): review disclosure for disciplined-vibe-coding ([`a24b68e4`](https://github.com/NousResearch/hermes-agent/commit/a24b68e415e1706e0138d2903aea035994022a49))
- Catalog): bump jev-approvals to v0.4.0 ([`27ed6530`](https://github.com/NousResearch/hermes-agent/commit/27ed653035c6aa2a3517adeb727cc61b4ff7eef3)) — @anpicasso
- Map contributor email for wackyju2-beep ([`08bd2d65`](https://github.com/NousResearch/hermes-agent/commit/08bd2d650fc5bde623f82d840c4e8d975eb89293))
- Catalog): review disclosure for twzrd-intel ([`54d02b92`](https://github.com/NousResearch/hermes-agent/commit/54d02b9216414ec270c2b67aae68b3ce67d87c8e))
- Catalog): review disclosure for chereda ([`2e0965fc`](https://github.com/NousResearch/hermes-agent/commit/2e0965fc1c0bd53dbeb408d780a826c6a53b1a4c))
- Catalog): review disclosure for hermes-cinema ([`ff3fc694`](https://github.com/NousResearch/hermes-agent/commit/ff3fc69483af82cfbbc3f2a124251f29e620e6c7))
- Catalog): review disclosure for omnisight ([`9e1aaa51`](https://github.com/NousResearch/hermes-agent/commit/9e1aaa518bb9ee51f1ce916db0b899efb894c036))
- Catalog): review disclosure for clotho ([`99330454`](https://github.com/NousResearch/hermes-agent/commit/993304543340d8e3bcb45cb0d015b2dfed319a75))
- Catalog): review disclosure for memory-shaper ([`e088297b`](https://github.com/NousResearch/hermes-agent/commit/e088297b93bdbafaaf189845d31cef256f4ec6b1))
- Plugin-catalog): re-pin ctx_checkpoint to 0.14.0 ([`845a9b75`](https://github.com/NousResearch/hermes-agent/commit/845a9b75b54663dddfbacbb77873c5f7900eaa56)) — @GottZ
- Map contributor email for Gaijin-01 ([`d93a1f90`](https://github.com/NousResearch/hermes-agent/commit/d93a1f908963bbd64ce6a55d0418988be8adb4e0))
- Catalog): review disclosure for prompt-firewall ([`49ca70df`](https://github.com/NousResearch/hermes-agent/commit/49ca70df285095d335030bc2fc8de39b953b5e1f))
- Catalog): bump aphrodite to 2.3.2 (binary 1.8.1) ([`ca2c5056`](https://github.com/NousResearch/hermes-agent/commit/ca2c5056edb8e922c15bfca4465915222ddc1d47)) — @NikolaRHristov
- Catalog): review disclosure for listeningkit-log ([`f6c015bd`](https://github.com/NousResearch/hermes-agent/commit/f6c015bdc0617871d6c346269f8fc0dfe516a93d))
- Map contributor email for rayyichen310 ([`8d8f0e09`](https://github.com/NousResearch/hermes-agent/commit/8d8f0e0988252bdd29c40e3f0b148db64796ef20))
- Map contributor email for ep150de ([`6f094128`](https://github.com/NousResearch/hermes-agent/commit/6f09412840ffc1700f3655fd4f1a2b812d26bcf7))
- Catalog): review disclosure for scenemux ([`f0bf8d1b`](https://github.com/NousResearch/hermes-agent/commit/f0bf8d1bae4c8973fe3e5974d4fb7a9984c24df2))
- Map contributor email for arjunbagga-xyz ([`68a2eab0`](https://github.com/NousResearch/hermes-agent/commit/68a2eab0f81f91dc2ea0117df1df5c3a23126eb6))
- Catalog): review disclosure for ghostbox ([`c225851d`](https://github.com/NousResearch/hermes-agent/commit/c225851db0ce8362a67152be30f5234c720c84fc))
- Map contributor email for Chosen9115 ([`eda9ab59`](https://github.com/NousResearch/hermes-agent/commit/eda9ab59bdbb6311d2fc7e38423f837e8644cdba))
- Map contributor email for klautimus ([`3756bc53`](https://github.com/NousResearch/hermes-agent/commit/3756bc53d81e822e7496f002c999d68eedb11ad8))
- Catalog): review disclosure for rule-injector ([`3439b695`](https://github.com/NousResearch/hermes-agent/commit/3439b695af2e6cb5571d77c54574ee4d2543f850))
- Catalog): review disclosure for theta-edge-node ([`40dac10e`](https://github.com/NousResearch/hermes-agent/commit/40dac10ea5505519fed7fb89ad86bc7d8226e80d))
- Catalog): review disclosure for timetopost ([`99fa894d`](https://github.com/NousResearch/hermes-agent/commit/99fa894dd8a29200dba2bd89d6ccb88f96b6a678))
- Catalog): review disclosure for hermes-watchdog ([`a98efde8`](https://github.com/NousResearch/hermes-agent/commit/a98efde8d9d07203eb10d5e9af55797461bf5761))
- Plugin-catalog): v0.5.1 — chip only signals problems ([`605f334d`](https://github.com/NousResearch/hermes-agent/commit/605f334d059ff611a791c5d834eaa4de8440b6c1)) — @33hodl
- Plugin-catalog): v0.5.0, disclosure states what it writes ([`278b5e09`](https://github.com/NousResearch/hermes-agent/commit/278b5e0914bdaeffd6c2dd2dec6f9645a46e7499)) — @33hodl
- Plugin-catalog): v0.4.2 ([`b286c654`](https://github.com/NousResearch/hermes-agent/commit/b286c65462892525375ee709724be4e3f7c5fc80)) — @33hodl
- Plugin-catalog): v0.4.1 ([`8f24896e`](https://github.com/NousResearch/hermes-agent/commit/8f24896ebad02f7965c7934d6d6f9742b657ebc4)) — @33hodl
- Plugin-catalog): v0.4.0 ([`5f016e48`](https://github.com/NousResearch/hermes-agent/commit/5f016e485c8cd5ac5de215930a4fc3b149f8db21)) — @33hodl
- Plugin-catalog): v0.3.2 ([`ce426661`](https://github.com/NousResearch/hermes-agent/commit/ce4266610f05e2deb5cd90f70b216301f1195000)) — @33hodl
- Plugin-catalog): v0.3.1 ([`dcb2595c`](https://github.com/NousResearch/hermes-agent/commit/dcb2595c66d986d745f71cb230a82a24c3cb59fd)) — @33hodl
- Plugin-catalog): v0.3.0 — numbered how-it-works ([`366fb8c9`](https://github.com/NousResearch/hermes-agent/commit/366fb8c906b3e5926e700b3096002d63750f40b7)) — @33hodl
- Plugin-catalog): v0.2.1 — ledger tuple fix ([`3362cc48`](https://github.com/NousResearch/hermes-agent/commit/3362cc48e6215c221cfd3f68931ab6aa891d9786)) — @33hodl
- Plugin-catalog): v0.2.0 — plain language + auto-close ([`75889632`](https://github.com/NousResearch/hermes-agent/commit/758896328983aee9f9503c9c220ba27e27423d46)) — @33hodl
- Plugin-catalog): v0.1.8 ([`ef5fc978`](https://github.com/NousResearch/hermes-agent/commit/ef5fc97832f06ebce6f46378d963d33287b34c9d)) — @33hodl
- Plugin-catalog): pin 4a565dd (v0.1.7 + release) ([`9fe88c91`](https://github.com/NousResearch/hermes-agent/commit/9fe88c91c7f77a9083e2ad3d26da93c21978cbf8)) — @33hodl
- Plugin-catalog): v0.1.7 — orphaned incidents close themselves ([`6fd1645a`](https://github.com/NousResearch/hermes-agent/commit/6fd1645ab05848d5d60fb9020921a4c1e7e5a106)) — @33hodl
- Plugin-catalog): v0.1.6 — Ack explains refusals ([`0f6db11d`](https://github.com/NousResearch/hermes-agent/commit/0f6db11debc957ab14146eb3f6192af9ee231065)) — @33hodl
- Plugin-catalog): v0.1.5 — Ack always available ([`1ae4453d`](https://github.com/NousResearch/hermes-agent/commit/1ae4453d409a861ca6fdfb612034e6afb3b60d38)) — @33hodl
- Plugin-catalog): v0.1.4 — ack closes a hand-off ([`0281872b`](https://github.com/NousResearch/hermes-agent/commit/0281872bad9db449994c9691aa4971378dabeb05)) — @33hodl
- Plugin-catalog): v0.1.3 — budget skips hand off ([`7bbe3469`](https://github.com/NousResearch/hermes-agent/commit/7bbe34698743ed590373a6a0bb4eec775a4f30f5)) — @33hodl
- Plugin-catalog): pin dd3d3e8 ([`d83c25ef`](https://github.com/NousResearch/hermes-agent/commit/d83c25ef9cc4f938fe6caa69f99adedcdfb3957d)) — @33hodl
- Plugin-catalog): v0.1.2 — escalation is a handoff, accurate toasts + re-pin 69992a0 ([`daff6c57`](https://github.com/NousResearch/hermes-agent/commit/daff6c577d7010ff55890fe1577f1f59e34b31e5)) — @33hodl
- Plugin-catalog): pin repo head 3c4f67c ([`f501ad48`](https://github.com/NousResearch/hermes-agent/commit/f501ad48b85bf81d6ced65f24a88f5c5162eff60)) — @33hodl
- Plugin-catalog): re-pin 49d10df (proof script; PR body screenshot) ([`4f4359cb`](https://github.com/NousResearch/hermes-agent/commit/4f4359cb12a4f391193dca0d5e7601ccb7fd75c3)) — @33hodl
- Plugin-catalog): Watchdog page screenshot + re-pin 02c846d ([`3e807cb9`](https://github.com/NousResearch/hermes-agent/commit/3e807cb9f12b272d79b0f49b539a94b321c0ca14)) — @33hodl
- Plugin-catalog): re-pin 9c8783a (clickable status chip) ([`ae35e900`](https://github.com/NousResearch/hermes-agent/commit/ae35e900ab22442ba335c5d53535aa08f3f02c9e)) — @33hodl
- Plugin-catalog): v0.1.1 sidebar page + re-pin e25e1e3 ([`9b78e13f`](https://github.com/NousResearch/hermes-agent/commit/9b78e13f1f292978ac80b98df749e0973b4b5fd1)) — @33hodl
- Plugin-catalog): Desktop screenshot + re-pin fad79ef ([`d23512c5`](https://github.com/NousResearch/hermes-agent/commit/d23512c547e88d44c02897fbc574feae398b0b37)) — @33hodl
- Plugin-catalog): re-pin hermes-watchdog to 4354e8d ([`cc2c567c`](https://github.com/NousResearch/hermes-agent/commit/cc2c567c7c92fc852f9b9067f0d373cfb210683c)) — @33hodl
- Plugin-catalog): re-pin hermes-watchdog to c76edf1 (example playbooks) ([`ffa6f8e8`](https://github.com/NousResearch/hermes-agent/commit/ffa6f8e8278bcee802ebbab7e8c22bc9c76f9360)) — @33hodl
- Plugin-catalog): Hermes Watchdog name, simple description, banner, re-pin 85a3237 ([`5dbf50d9`](https://github.com/NousResearch/hermes-agent/commit/5dbf50d91ed1390880d818f9a91098114b8113b0)) — @33hodl
- Plugin-catalog): re-pin hermes-watchdog to 1094084 ([`63f0d9a8`](https://github.com/NousResearch/hermes-agent/commit/63f0d9a8a97c116d18c2001000fa5bd389f9e112)) — @33hodl
- Keep the PR description out of the branch ([`30ca239e`](https://github.com/NousResearch/hermes-agent/commit/30ca239e757afe7bcc5145e04aa710a1bb33bb37)) — @33hodl
- Plugin-catalog): re-pin hermes-watchdog to 0bcc7ff ([`ee0d47a3`](https://github.com/NousResearch/hermes-agent/commit/ee0d47a30fdb94f1e91300e2576b2a39b49ab18a)) — @33hodl
- Plugin-catalog): re-pin hermes-watchdog to d64d015 ([`066ed4d4`](https://github.com/NousResearch/hermes-agent/commit/066ed4d40d74188fa0b0bfaa781443e0b0cc750a)) — @33hodl
- Plugin-catalog): add hermes-watchdog ([`a6332323`](https://github.com/NousResearch/hermes-agent/commit/a63323232aba36fcae010c1fd229cc2e77cb6a00)) — @33hodl
- Map contributor email for gergeisabo ([`ecf04102`](https://github.com/NousResearch/hermes-agent/commit/ecf0410243ff7251509d968dfa5b82ca8d5c0a85))
- Catalog): review disclosure for laya-oneshot ([`892314e0`](https://github.com/NousResearch/hermes-agent/commit/892314e0ecf860e04d2539b528755c8b4993308f))
- Catalog): pin laya-oneshot to 0.2.0 (7b76de4) ([`07edb75f`](https://github.com/NousResearch/hermes-agent/commit/07edb75f9761b6aabd41e85b9c5b247d41ef1d66)) — @gergeisabo

## 📦 Other Changes

- Plugin-catalog: bump nvidia-switchyard to 0.1.1 (NVIDIA Switchyard) ([`f7e2898a`](https://github.com/NousResearch/hermes-agent/commit/f7e2898aaefc8f967dbf7345e3999a65672fe60e)) — @DevArtech
- Plugin-catalog: bump memtomem to v0.7.8 ([`ef932c31`](https://github.com/NousResearch/hermes-agent/commit/ef932c3147891f0556fcb994cc5e208c7e699a88)) — @memtomem
- F20: session_rules comments describe behaviour, not its history ([`d923fc1d`](https://github.com/NousResearch/hermes-agent/commit/d923fc1dc4277cb01041aff3dffa8e667b8f146c)) — @yoniebans
- Catalog(nexus): pin 0.22.56 and disclose the tier-change ([`0c73bfe0`](https://github.com/NousResearch/hermes-agent/commit/0c73bfe04191c6b45817fbf0969a2a4703606100)) — @Neboy72
- Catalog(nexus): pin 0.22.55 and disclose the coverage rule ([`cc9abbf3`](https://github.com/NousResearch/hermes-agent/commit/cc9abbf362f403c62069480ebeef99b850cceeb9)) — @Neboy72
- Catalog(nexus): pin 0.22.54 and disclose the candidate-pool floor ([`d19b52d9`](https://github.com/NousResearch/hermes-agent/commit/d19b52d97532c4bc8313588e95d03c26db00aa64)) — @Neboy72
- Change SHA in hermes-safeguard.yaml ([`38886aef`](https://github.com/NousResearch/hermes-agent/commit/38886aef1c964bd0316c065a3221cd1b78632005)) — @robberdom
- Plugin-catalog: hermes-kame-provider 1.9.0.2 ([`ad93f0a2`](https://github.com/NousResearch/hermes-agent/commit/ad93f0a2883d7152309bcea19fba4826f7e8f9e2)) — @Kame696
- Plugin-catalog: hermes-kame-api-rotation 1.9.0.2 ([`1b3abd04`](https://github.com/NousResearch/hermes-agent/commit/1b3abd0414827fbf51b4da21f1173facfd1227ef)) — @Kame696
- F1: the stored route names its model, and resume_route pairs them ([`cecd813a`](https://github.com/NousResearch/hermes-agent/commit/cecd813a36bc49f247b6210284b3a5d68a64d8b0)) — @yoniebans
- Plugin-catalog: bump stoa to 0.26.3 ([`ec1e4358`](https://github.com/NousResearch/hermes-agent/commit/ec1e43589d8ed924366691757b0e1f6d594707f5)) — @jarrett-del
- Plugin-catalog: bump stoa to 0.26.2 ([`a1ea3915`](https://github.com/NousResearch/hermes-agent/commit/a1ea3915d1d1a24ad877ab0bf7433dabb4c0f5ed)) — @jarrett-del
- Plugin-catalog: bump stoa to 0.26.1 ([`d204d5a3`](https://github.com/NousResearch/hermes-agent/commit/d204d5a327e832817b14ad733dc85e262bfc0d50)) — @jarrett-del
- Plugin-catalog: bump stoa to 0.26.0 ([`ddb105ba`](https://github.com/NousResearch/hermes-agent/commit/ddb105ba7a264aad9555a102b4c763435204b70f)) — @jarrett-del
- Plugin-catalog: bump stoa to 0.25.1 ([`3559854d`](https://github.com/NousResearch/hermes-agent/commit/3559854d327a19e67c38d071cf075372dcc401bd)) — @jarrett-del
- Plugin-catalog: bump stoa to 0.25.0 ([`840cc281`](https://github.com/NousResearch/hermes-agent/commit/840cc281ef9acaf2c394ca5e21bff8cf0aa658c2)) — @jarrett-del
- Plugin-catalog: bump stoa to 0.24.2 ([`c54d3451`](https://github.com/NousResearch/hermes-agent/commit/c54d3451735c0ed6b3c391e59e97bc5c91e8769f)) — @jarrett-del
- Plugin-catalog: bump stoa to 0.23.0 ([`ec7b8bda`](https://github.com/NousResearch/hermes-agent/commit/ec7b8bda36f3865e61cb8e66bc20e0ae6fde8236)) — @jarrett-del
- Plugin-catalog: bump stoa to 0.22.1 ([`06748acc`](https://github.com/NousResearch/hermes-agent/commit/06748acc0fa557f02b9d853adc4479f3702e4c55)) — @jarrett-del
- Plugin-catalog: bump stoa to 0.22.0 ([`d6dd3a54`](https://github.com/NousResearch/hermes-agent/commit/d6dd3a54e8b4456e4eee1a78b10ac4e5086d7dd7)) — @jarrett-del
- Plugin-catalog: credential-pool-switcher (#152944) ([#152944](https://github.com/NousResearch/hermes-agent/pull/152944)) — @hendkai
- Plugin-catalog: chartquery (#156840) ([#156840](https://github.com/NousResearch/hermes-agent/pull/156840)) — @josselinlbe
- Plugin-catalog: huntapi (#156839) ([#156839](https://github.com/NousResearch/hermes-agent/pull/156839)) — @josselinlbe
- Plugin-catalog: air-agent-kya (#153579) ([#153579](https://github.com/NousResearch/hermes-agent/pull/153579)) — @armanmamyan
- Plugin-catalog: fotor (#156761) ([#156761](https://github.com/NousResearch/hermes-agent/pull/156761)) — @jovijovi
- Plugin-catalog: 0xarchive (#155154) ([#155154](https://github.com/NousResearch/hermes-agent/pull/155154)) — @nuttykenzo
- Plugin-catalog: aimlapi (#155147) ([#155147](https://github.com/NousResearch/hermes-agent/pull/155147)) — @hugoaimlapi
- Plugin-catalog: fleet-control (#153881) ([#153881](https://github.com/NousResearch/hermes-agent/pull/153881)) — @driptothebone
- Plugin-catalog(xscapes): 0.2.2, README images render on the marketplace ([`cb6e2811`](https://github.com/NousResearch/hermes-agent/commit/cb6e2811917b02f7a472f7eb6a1a09f5c751b64e)) — @donlucasx
- Plugin-catalog: pin timecapsule 0.1.1 (sha 7d4ef02) ([`1c35efdd`](https://github.com/NousResearch/hermes-agent/commit/1c35efdd3de0ccf4a6dc34c2aae5db809a43601f)) — @brayedan
- Zambo-receipts: re-pin to f771dcd (canon free-tier wording, AER-1 draft credit) + description punctuation ([`0133939e`](https://github.com/NousResearch/hermes-agent/commit/0133939ec517cdde4d9d39a2d782e5d191e1613e)) — @zambodotdev
- Catalog: antemuse 0.11.21 (five states, restored and specified) ([`21af19f9`](https://github.com/NousResearch/hermes-agent/commit/21af19f98f429dba588582a3b8943ce882f4c2a5)) — @roosiq
- Catalog: antemuse 0.11.20 (interchangeable walk graphs) ([`d16fe817`](https://github.com/NousResearch/hermes-agent/commit/d16fe817e66256f1ba925b2d7bf9a28297235483)) — @roosiq
- Catalog: antemuse 0.11.19 (touch cockpit, 4 screenshots) ([`dadc410a`](https://github.com/NousResearch/hermes-agent/commit/dadc410a7d59c8ea92d222bf416d75c74f839b65)) — @roosiq
- Catalog: antemuse 0.10.44 → 0.11.18 (generated entry; credential reader removed, description corrected) ([`7086dddb`](https://github.com/NousResearch/hermes-agent/commit/7086dddb15be0d3e4af9e27f0f2e6845e8b16705)) — @roosiq
- Plugin-catalog: holographic 0.29.2 ([`87d3668e`](https://github.com/NousResearch/hermes-agent/commit/87d3668efb7ddb8cba04caa7f006a15a9e34f903)) — @itpartypattaya
- Plugin-catalog: bump browser-viewer to 0.3.4 ([`7f9b6bab`](https://github.com/NousResearch/hermes-agent/commit/7f9b6bab5c2088a4254440ce62923218373e84d3)) — @vittoriocompagno
- Plugin-catalog: bump browser-viewer to 0.3.1 ([`ba8389c4`](https://github.com/NousResearch/hermes-agent/commit/ba8389c4a7f238c4b00cc33aed80960df221a13e)) — @vittoriocompagno
- Plugin-catalog: shipframe 1.2.0 ([`bdedec09`](https://github.com/NousResearch/hermes-agent/commit/bdedec090f8ff7ed6c7e774f1c858bbd98b248c8)) — @juanitourquiza
- Hermes-regress: pin to fbd570b, disclose task-id scope and serialised claims ([`89a7034f`](https://github.com/NousResearch/hermes-agent/commit/89a7034fc74e430bdc4597b2e0ff3545fd24ac5a)) — @harishkotra
- Hermes-regress: pin to ddc0a2b, scope disclosure to the claimed session ([`f6f1ba64`](https://github.com/NousResearch/hermes-agent/commit/f6f1ba640d6b2c7108380ed1deebedc20603d60d)) — @harishkotra
- Hermes-regress: pin to a6f1960, scope disclosure to the real store path ([`51c325d9`](https://github.com/NousResearch/hermes-agent/commit/51c325d9169f5d52080611e291efa6d9abf0b02a)) — @harishkotra
- Plugin-catalog: re-pin glide to 3db11c66 (5421c70a + e2e harness moved under tests/ for the install scanner) ([`40dea8e8`](https://github.com/NousResearch/hermes-agent/commit/40dea8e81ff15fb14a780f07882746a087489c08)) — @kvnloo
- Plugin-catalog: re-pin glide to 0b03b5e (review fixes: rename, SSRF guard, minimal child env, http(s)-only links, opt-in loopback lane token) ([`084baa08`](https://github.com/NousResearch/hermes-agent/commit/084baa08c2328f2114e1885dc57f80543420792e)) — @kvnloo
- Catalog(glide): pin cbcb012760f692bff136b0c75d6c09c47ede72aa (rich AODL contract card #263, contrast #264) ([#263](https://github.com/NousResearch/hermes-agent/pull/263)) — @kvnloo
- Plugin-catalog: system-one 0.4.1 (ollama provider: Laya, Tev1) ([`7abd4a22`](https://github.com/NousResearch/hermes-agent/commit/7abd4a227e6eacbf34977e3ed4c56bea895ce1cc)) — @salismt
- Plugin-catalog: system-one 0.4.0 (upstage, azure, self-hosted providers) ([`8a7ef924`](https://github.com/NousResearch/hermes-agent/commit/8a7ef924833dd11bd23a83965eefb42ca07f1820)) — @salismt
- Plugin-catalog: bump session-flow to v1.30.0 (pin 26fa4c6) ([`9e601ef0`](https://github.com/NousResearch/hermes-agent/commit/9e601ef0554ba9c24264bd7f516501baee7937af)) — @Agantila
- Plugin-catalog: bump acrylic to 1.2.0 (pin ae5b8b4) ([`78b5080a`](https://github.com/NousResearch/hermes-agent/commit/78b5080a70e2b22a4608b29277ff72fb6f8b4e9b)) — @Saderius
- Catalog: repin proof-run to 0.3.2 ([`c3412732`](https://github.com/NousResearch/hermes-agent/commit/c3412732504f7dccc9bfaebf1e5a9bff8cb908bf)) — @raffieeey
- Catalog: repin proof-run to 0.3.1 ([`9196d6bb`](https://github.com/NousResearch/hermes-agent/commit/9196d6bb2aaeb37c23a32e7b4a51e4bfb23792db)) — @raffieeey
- Catalog: offpeak-bekci 0.1.10 pini (2828b50) ([`7045d8b9`](https://github.com/NousResearch/hermes-agent/commit/7045d8b92fc91051b1b975083c30dc2b9e99a707)) — @onkanat
- Plugin-catalog: relist volcengine-voice at 2.0.0 (public provider APIs) ([`2dafbb06`](https://github.com/NousResearch/hermes-agent/commit/2dafbb061fcf12d71a2360fbacc74a7f7767aa72)) — @linxichen
- Plugin-catalog: bump model-kombat to 0.7.3 ([`e9ed8aa5`](https://github.com/NousResearch/hermes-agent/commit/e9ed8aa5ca7ed761728aecdd3987f42b6baec936)) — @DarkeTech
- Plugin-catalog: clarify approval disclosure for 2pr ([`11255d69`](https://github.com/NousResearch/hermes-agent/commit/11255d692e3178733cccbb71d071ab215b6ebab4)) — @midovislam
- Plugin-catalog: re-pin argos to f0a9a09 (Nous-style cover) ([`2fe1010b`](https://github.com/NousResearch/hermes-agent/commit/2fe1010b61989034e46a247f2051c04434d0c123)) — @Tormen28
- Plugin-catalog: token-stats screenshots, pin cef5577 ([`f70f7c36`](https://github.com/NousResearch/hermes-agent/commit/f70f7c36044f47643e3206bb304d7eb03f03acd2)) — @amitamit10
- Catalog: deepseek-web-tools 1.0.6 (floor 0.22.2) ([`e96a0bf7`](https://github.com/NousResearch/hermes-agent/commit/e96a0bf758fa2798b2913b0cc612989859013770)) — @fedebyes
- Catalog: deepseek-web-tools 1.0.5 - file input, honest disclosure, floor 0.23.0 ([`6eb13e69`](https://github.com/NousResearch/hermes-agent/commit/6eb13e69f3df1e57ba8822e34108c08b6704a66a)) — @fedebyes
- Plugin-catalog: pin hermes-handle-it to 30e669b (0.3.0) ([`6ae8f405`](https://github.com/NousResearch/hermes-agent/commit/6ae8f405f109e63a063f30eb0cb72c39bdfd4e4d)) — @casualsav
- Catalog: hermes-rich-ui v0.1.11 @ 7524087 ([`d197285b`](https://github.com/NousResearch/hermes-agent/commit/d197285b32eb4acb2f547c8eb9acdbfe55407403)) — @jacobhausler
- Plugin-catalog: hermes-mini 0.2.1 ([`e3b521d3`](https://github.com/NousResearch/hermes-agent/commit/e3b521d31cf53dfa3460ee4e443ad3fe5c5fce11)) — @ieatcode4breakfast
- Plugin-catalog: tenure 1.0.0 → 1.1.0 ([`2735b7ab`](https://github.com/NousResearch/hermes-agent/commit/2735b7ab3c126713182df0e66962f2d8d856a1c6)) — @otsoa-dubief
- Plugin-catalog: bump memtomem-memory to 0.2.1 ([`3cc1548f`](https://github.com/NousResearch/hermes-agent/commit/3cc1548f51448fc7444eddf6651d018509fba59d)) — @memtomem
- Webgraft: re-pin to 0748d7f (0.3.0) ([`3437e5c3`](https://github.com/NousResearch/hermes-agent/commit/3437e5c3a69366f7897087e2c44727e9d7f2efaa)) — @ElSerda
- Plugin-catalog: bump disciplined-vibe-coding to 0.3.3 (502e655) ([`0d747ee7`](https://github.com/NousResearch/hermes-agent/commit/0d747ee71981c339a593dcbf203353ccdea7d56e)) — @bmtrnavsky
- Plugin-catalog: bump plan-mode to 1.5.3 ([`5d321eaa`](https://github.com/NousResearch/hermes-agent/commit/5d321eaab9b481a7653790444ca39cd7c37d7efb)) — @100yenadmin
- Pin the catalog entry to the tree that reads settings through hermes_yaml ([`bc9cdf16`](https://github.com/NousResearch/hermes-agent/commit/bc9cdf1622862a5738a7356958a35eff4bb51094)) — @wackyju2-beep
- Pin the catalog entry to the tree that documents the Origin guard ([`c51c8b27`](https://github.com/NousResearch/hermes-agent/commit/c51c8b27a2a1b9ba01fbf89e6d3554d6754873fc)) — @wackyju2-beep
- Pin the catalog entry to the scrubbed tree ([`23c33033`](https://github.com/NousResearch/hermes-agent/commit/23c330339630552de1e68d3cf9982197ed68608d)) — @wackyju2-beep
- Pin the catalog entry to the commit that fixes the English security note ([`8b5e36ab`](https://github.com/NousResearch/hermes-agent/commit/8b5e36aba1995b648e84a180ed876b6d7b3fbe53)) — @wackyju2-beep
- Plugin-catalog: перевести chereda на f1c1bbf (префикс разрешений, путь к бинарю, английский README) ([`6a261e42`](https://github.com/NousResearch/hermes-agent/commit/6a261e42897c0f762b6f4206a9346330fdff3e1a)) — @kostyk348
- Plugin-catalog: pin chereda e7c1dcc (CI workflow for the 32 tests) ([`9a3f874e`](https://github.com/NousResearch/hermes-agent/commit/9a3f874e933ec0fa81bb2c20857e4db65b48afb4)) — @kostyk348
- Plugin-catalog: chereda 0.1.1 — approval gate for model-written proofs, sha bump ([`21613702`](https://github.com/NousResearch/hermes-agent/commit/216137020ff22f60519e07e2dfa5d3e98566f7c6)) — @kostyk348
- Plugin-catalog: chereda — category desktop (accepted shelf), pin f4b5b82 ([`c4b51645`](https://github.com/NousResearch/hermes-agent/commit/c4b5164527d536f16830290a792e3582e6271a9b)) — @kostyk348
- Plugin-catalog: bump chereda pin to f4b5b82 (i18n en/ru, verb glossary) ([`3d816b57`](https://github.com/NousResearch/hermes-agent/commit/3d816b57ed5d00d1e2ca6b36ed467f87535169cc)) — @kostyk348
- Plugin-catalog: bump chereda pin to ab65d96 (i18n en/ru, verb glossary) ([`71f3e707`](https://github.com/NousResearch/hermes-agent/commit/71f3e707e7daa84be7e7102ded829076ef679d1e)) — @kostyk348
- Plugin-catalog: bump chereda pin to 7e14b09 (description editing, free verb list) ([`e45d3268`](https://github.com/NousResearch/hermes-agent/commit/e45d326897ffbae983fd701ea5f39154301f4f51)) — @kostyk348
- Tormen catalog: re-pin hermes-cinema to 68555cb (0.3.7) ([`c34ec9e7`](https://github.com/NousResearch/hermes-agent/commit/c34ec9e7b32fa063aa417df069d90fe364d30ed8)) — @Tormen28
- Catalog: re-pin hermes-cinema a 8dbd0e1 (0.3.6) ([`b15d07fe`](https://github.com/NousResearch/hermes-agent/commit/b15d07fe9f3605ba4336d466c4d87923486448f9)) — @Tormen28
- Catalog: re-pin hermes-cinema to fd75227 (agent half, English default) ([`77de30ee`](https://github.com/NousResearch/hermes-agent/commit/77de30ee2510dfa025c5d5fde036ae7b66ffda5e)) — @Tormen28
- Catalog: re-pin rubal-oracle at 0f7cf67 (calendar compliance) ([`aa1e0ba7`](https://github.com/NousResearch/hermes-agent/commit/aa1e0ba76d13b4eca6235239086f90430799f0d7)) — @X0EF
- Plugin-catalog: clotho re-pins to 9c47c5a for the review fixes ([`92b45297`](https://github.com/NousResearch/hermes-agent/commit/92b452979159b0713ae45fb5b6a1bf05f65b710e)) — @NicWeinbrecht
- Plugin-catalog: clotho pins the commit without runtime overrides of Hermes core ([`cb55b25b`](https://github.com/NousResearch/hermes-agent/commit/cb55b25b7ff7d1841adfb9bff52abf440be4d173)) — @NicWeinbrecht
- Plugin-catalog: bump memory-shaper to 1.12.1 (memcheck opt-in, hold_stream, bounded samples) ([`5bf7dc0b`](https://github.com/NousResearch/hermes-agent/commit/5bf7dc0bec7e338340ca8a789d5680c4688322b6)) — @ockentap
- Kaggle-competitions: bump sha c5f2dad -&gt; d51f8c9 (leaderboard CLI flag fix) ([`75ba7070`](https://github.com/NousResearch/hermes-agent/commit/75ba70704071ab82bb4447b305e4dd2a5f8032c1)) — @landenjackson
- Plugin-catalog: heartbeat2 0.4.9 ([`8c5b5e96`](https://github.com/NousResearch/hermes-agent/commit/8c5b5e96cf0a582a1d455729fc99e3c5a13ff667)) — @100yenadmin
- Catalog(prompt-firewall): re-pin 1.1.5 to the installable commit ([`b1de8e45`](https://github.com/NousResearch/hermes-agent/commit/b1de8e4593f2e259ce3c884baa5398ef40a36bdc)) — @Gaijin-01
- Catalog: correct xAI token disclosure and re-pin 0.10.6 ([`5174610a`](https://github.com/NousResearch/hermes-agent/commit/5174610a8696299a66bdbfb964fa57441e2f3b3c)) — @jerrygooch
- Catalog: bump jg-provider-usage to 0.10.6 ([`34a8ec81`](https://github.com/NousResearch/hermes-agent/commit/34a8ec818d9059b14c88c70c387bc6bf3d35c518)) — @jerrygooch
- Catalog: pin 1.7.2 (vault login + transport hardening) ([`db9e4328`](https://github.com/NousResearch/hermes-agent/commit/db9e4328828b50f2659ee9906bc8f607b1cb6d16)) — @Goitonthefloor
- Catalog: pin secret-drop 1.7.1 (vault session survives batch stores) ([`4b5c3b2c`](https://github.com/NousResearch/hermes-agent/commit/4b5c3b2c7990c37acbbd218adad2a1c70d5c3b38)) — @Goitonthefloor
- Catalog: move the 1.7.0 pin to the config-read warning fix ([`901833a4`](https://github.com/NousResearch/hermes-agent/commit/901833a4e189fdd2e3bd7c5a09b58396be38a565)) — @Goitonthefloor
- Catalog: pin secret-drop 1.7.0 (optional Vaultwarden backend) ([`d40221d6`](https://github.com/NousResearch/hermes-agent/commit/d40221d69b0f0460a3f42cfdc07768a2fb3df450)) — @Goitonthefloor
- Plugin-catalog: re-pin dafeiyu-companion to d0e44679 (review fixes) ([`9e64cb63`](https://github.com/NousResearch/hermes-agent/commit/9e64cb63f0f2ef67c876966e9e58b5fddd97c978)) — @rayyichen310
- Re-pin scenemux to ca6ef43 (v0.5.1): home_agent_url from setting only, tighten _is_trusted_host ([`1e4da5d6`](https://github.com/NousResearch/hermes-agent/commit/1e4da5d69fd3695fde4420c07561a9dc13248b62)) — @ep150de
- Catalog: re-pin rule-injector to 1.1.0 (review fixes) ([`bff1dcf7`](https://github.com/NousResearch/hermes-agent/commit/bff1dcf72930f5568f38c431220f7b210fab1555)) — @klautimus
- Catalog: re-pin rule-injector to the dashboard build ([`4c4a7702`](https://github.com/NousResearch/hermes-agent/commit/4c4a7702027e3943dd776565a574103c9db55033)) — @klautimus
- Pin theta-edge-node to 3634cd8 (review fixes) ([`b81b5d79`](https://github.com/NousResearch/hermes-agent/commit/b81b5d79dba7a4f580ef0157d5f0500d2a82e61e)) — @bonesnasty
- Pin theta-edge-node to 2f1e976 ([`dc681d08`](https://github.com/NousResearch/hermes-agent/commit/dc681d080cede3606db94859b7070bce2c3af9a4)) — @bonesnasty
- Plugin-catalog: re-pin timetopost to 8e91a08 ([`6caaf578`](https://github.com/NousResearch/hermes-agent/commit/6caaf5788388a7f4805c2d8ad186d4af3ded4a33)) — @MelMayssonOwen
- Catalog: re-pin hermes-watchdog to c2d6774 (docs: current screenshot; same 0.10.1 code) ([`670fdcbd`](https://github.com/NousResearch/hermes-agent/commit/670fdcbdd44f23a9d6138545ae03ab87f5a974fb)) — @33hodl
- Catalog: re-pin hermes-watchdog to v0.10.1 (b1a2bc7) ([`a8eb58de`](https://github.com/NousResearch/hermes-agent/commit/a8eb58de91d4cb5ea6c6c3eaa2f8036925863f25)) — @33hodl
- Catalog: re-pin hermes-watchdog to v0.10.0 (1044530) ([`9196dac4`](https://github.com/NousResearch/hermes-agent/commit/9196dac485902980d4550749547f552531626aea)) — @33hodl
- Catalog: re-pin hermes-watchdog to v0.9.6 (cf8e3ff) — manifest version corrected ([`6d18fedc`](https://github.com/NousResearch/hermes-agent/commit/6d18fedc0ef22dca40175ce2d07aef62672ecd02)) — @33hodl
- Catalog: re-pin hermes-watchdog to v0.9.5 (2f12497) ([`7822dfc3`](https://github.com/NousResearch/hermes-agent/commit/7822dfc3ff730038b78cedce2c1b37c2088b3709)) — @33hodl
- Catalog: re-pin hermes-watchdog to v0.9.4 (383a158) ([`00f03820`](https://github.com/NousResearch/hermes-agent/commit/00f03820d9a61b041724db68a82580bb50007579)) — @33hodl
- Catalog: re-pin hermes-watchdog to v0.9.3 (2ae125e) ([`417cd327`](https://github.com/NousResearch/hermes-agent/commit/417cd327450272ded22d26b53453ae0611938af5)) — @33hodl
- Catalog: re-pin hermes-watchdog to v0.9.2 (996d7f8) ([`488bb74b`](https://github.com/NousResearch/hermes-agent/commit/488bb74b83117ede6f18cd59c73fcc8a9dbbd4ed)) — @33hodl
- Catalog: re-pin hermes-watchdog to v0.9.1 (9606742) ([`08c9b650`](https://github.com/NousResearch/hermes-agent/commit/08c9b650f9e544de8157eee230d543b1700d8c2c)) — @33hodl
- Catalog: re-pin hermes-watchdog to v0.9.0 (9b4bd98) ([`dc90fe22`](https://github.com/NousResearch/hermes-agent/commit/dc90fe22d41e206adedafca467ed20a41986bf77)) — @33hodl
- Catalog: re-pin hermes-watchdog to v0.8.0 (36b7448) ([`4111ca92`](https://github.com/NousResearch/hermes-agent/commit/4111ca924c1e84b4fec444455222d273fef84d06)) — @33hodl
- Catalog: re-pin hermes-watchdog to v0.7.1 (81d3deb) ([`8f4a11be`](https://github.com/NousResearch/hermes-agent/commit/8f4a11beee76d0bed4a059f6e7b5347ad39196bb)) — @33hodl
- Catalog: re-pin hermes-watchdog to v0.7.0 (9c668d9) ([`d7401ddd`](https://github.com/NousResearch/hermes-agent/commit/d7401ddd0898ea1aa89fd72a4c219e638b836e77)) — @33hodl
- Catalog: re-pin hermes-watchdog to v0.6.2 (c6fdd32) — self-explaining incidents ([`6040cc06`](https://github.com/NousResearch/hermes-agent/commit/6040cc0659713e482da45fa8561c25467239b068)) — @33hodl
- Catalog: re-pin hermes-watchdog to v0.6.0 (77a7cfe) — incidents explain themselves ([`a8743172`](https://github.com/NousResearch/hermes-agent/commit/a87431723e0b066c0011ef311e9098df0c5a4144)) — @33hodl
- Catalog: re-pin hermes-watchdog to v0.5.5 head (feea208) ([`2493ae39`](https://github.com/NousResearch/hermes-agent/commit/2493ae39dd6b1c749c8829374948cb7b4cd2f0b8)) — @33hodl
- Catalog(hermes-watchdog): re-pin to v0.5.3 (pin, docs and install line agree) ([`2718ba4e`](https://github.com/NousResearch/hermes-agent/commit/2718ba4e3382f380b6fb418c8f0e5c20817bc27a)) — @33hodl
- Catalog(hermes-watchdog): re-pin to v0.5.2 (CI green; ledger works without host storage) ([`73d6e572`](https://github.com/NousResearch/hermes-agent/commit/73d6e5726d02427e24988dbeaafd71685bd0f659)) — @33hodl
- Pin laya-oneshot catalog entry to 0.3.0 review fixes ([`d85255d2`](https://github.com/NousResearch/hermes-agent/commit/d85255d24c9ea0890c49bbb8a0849efe9806389b)) — @gergeisabo

## 👥 Contributors

Thank you to everyone who contributed to this release!

- @33hodl (52 commits)
- @yoniebans (20 commits)
- @arjunbagga-xyz (15 commits)
- @kvnloo (13 commits)
- @jarrett-del (11 commits)
- @kostyk348 (8 commits)
- @vortexopenclaw (7 commits)
- @austinpickett (7 commits)
- @Ilyassbm (6 commits)
- @Neboy72 (5 commits)
- @harishkotra (5 commits)
- @Tormen28 (5 commits)
- @wackyju2-beep (5 commits)
- @roosiq (4 commits)
- @Goitonthefloor (4 commits)
- @BearHuddleston (3 commits)
- @robberdom (3 commits)
- @100yenadmin (3 commits)
- @Tranquil-Flow (3 commits)
- @TarasShyn (3 commits)
- @iknowterry (3 commits)
- @salismt (3 commits)
- @MelMayssonOwen (3 commits)
- @quotumorg (3 commits)
- @AbigailDavised (3 commits)
- @NicWeinbrecht (3 commits)
- @matthewdonsemail-lab (3 commits)
- @klautimus (3 commits)
- @bonesnasty (3 commits)
- @gergeisabo (3 commits)
- @c410979729-bit (2 commits)
- @memtomem (2 commits)
- @c2h5oh (2 commits)
- @madsb (2 commits)
- @Kame696 (2 commits)
- @rodricksz4h5 (2 commits)
- @josselinlbe (2 commits)
- @SRai22 (2 commits)
- @atostivint (2 commits)
- @vittoriocompagno (2 commits)
- @anpicasso (2 commits)
- @raffieeey (2 commits)
- @jacobhausler (2 commits)
- @dacheah (2 commits)
- @rbur0425 (2 commits)
- @midovislam (2 commits)
- @huwhitememes (2 commits)
- @amitamit10 (2 commits)
- @fedebyes (2 commits)
- @akinduroifedayo (2 commits)
- @pCwOrM (2 commits)
- @X0EF (2 commits)
- @jerrygooch (2 commits)
- @rayyichen310 (2 commits)
- @ep150de (2 commits)
- @DevArtech (1 commit)
- @cdempsey1221 (1 commit)
- @unsupportedpastels (1 commit)
- @flabanabba8 (1 commit)
- @hdiggity (1 commit)
- @iap (1 commit)
- @Thorballer (1 commit)
- @loheander (1 commit)
- @LangerSword (1 commit)
- @angusvka-spec (1 commit)
- @hendkai (1 commit)
- @shreyasudupi (1 commit)
- @TakeshiTGAL (1 commit)
- @elyssiaamani (1 commit)
- @noviceadam666 (1 commit)
- @armanmamyan (1 commit)
- @jovijovi (1 commit)
- @nuttykenzo (1 commit)
- @hugoaimlapi (1 commit)
- @driptothebone (1 commit)
- @donlucasx (1 commit)
- @brayedan (1 commit)
- @mrdavey (1 commit)
- @Miawd3 (1 commit)
- @zambodotdev (1 commit)
- @percyhendrux123-prog (1 commit)
- @nicholaslaldigital (1 commit)
- @obkaro (1 commit)
- @itpartypattaya (1 commit)
- @stefanofa (1 commit)
- @lazyants (1 commit)
- @JPeetz (1 commit)
- @jnorthrup (1 commit)
- @tedlefter (1 commit)
- @juanitourquiza (1 commit)
- @bwoliveira (1 commit)
- @divyasshree-BQ (1 commit)
- @andrewhinh (1 commit)
- @apoapostolov (1 commit)
- @willbohn (1 commit)
- @Agantila (1 commit)
- @AIvashov (1 commit)
- @Saderius (1 commit)
- @kumpayinteractive-sudo (1 commit)
- @ArmagedonFlamer (1 commit)
- @simonvanlaak (1 commit)
- @onkanat (1 commit)
- @linxichen (1 commit)
- @yxssxn (1 commit)
- @ardey26 (1 commit)
- @Anunnaki-Astronaut (1 commit)
- @DarkeTech (1 commit)
- @omxhub (1 commit)
- @ccromp (1 commit)
- @guglielmo-io (1 commit)
- @casualsav (1 commit)
- @speteai (1 commit)
- @d8joseph (1 commit)
- @joescars (1 commit)
- @duu261 (1 commit)
- @BadTechBandit (1 commit)
- @ieatcode4breakfast (1 commit)
- @aliHafizji (1 commit)
- @otsoa-dubief (1 commit)
- @zchking (1 commit)
- @Angerosteles (1 commit)
- @ElSerda (1 commit)
- @bmtrnavsky (1 commit)
- @twzrd-sol (1 commit)
- @ockentap (1 commit)
- @GottZ (1 commit)
- @landenjackson (1 commit)
- @Gaijin-01 (1 commit)
- @NikolaRHristov (1 commit)
- @web3blind (1 commit)
- @Chosen9115 (1 commit)
- @elozadaf (1 commit)
- @jrezmo (1 commit)

**Full Changelog**: [v0.23.2+canary.20261117T064624Z...v0.23.2+canary.20261118T064620Z](https://github.com/NousResearch/hermes-agent/compare/v0.23.2+canary.20261117T064624Z...v0.23.2+canary.20261118T064620Z)</content>
    <ore:provenance>
      <ore:sourceId>hermes-agent-releases</ore:sourceId>
      <ore:sourceName>Hermes Agent GitHub Releases</ore:sourceName>
      <ore:sourceType>github_releases</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://github.com/NousResearch/hermes-agent/releases</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://api.github.com/repos/NousResearch/hermes-agent/releases</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://github.com/NousResearch/hermes-agent/releases/tag/v0.23.2%2Bcanary.20261118T064620Z</ore:originalUrl>
      <ore:upstreamId>RE_kwDOPRF1G84azJz6</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hacker-news:27ee7e280728b4726a9ae89955803bae</id>
    <title>Show HN: Tinnitus frequency finder and audio notch tool</title>
    <updated>2026-11-18T03:40:01Z</updated>
    <published>2026-11-18T03:40:01Z</published>
    <link rel="alternate" href="https://trynotched.com/find" />
    <link rel="via" href="https://news.ycombinator.com/rss" />
    <category scheme="urn:ore-news:sources" term="hacker-news" label="Hacker News" />
    <author>
      <name>Hacker News</name>
    </author>
    <source>
      <id>urn:ore-news:source:hacker-news</id>
      <title>Hacker News</title>
      <link rel="alternate" href="https://news.ycombinator.com/" />
      <link rel="via" href="https://news.ycombinator.com/rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hacker-news</ore:sourceId>
      <ore:sourceName>Hacker News</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://news.ycombinator.com/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://news.ycombinator.com/rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://trynotched.com/find</ore:originalUrl>
      <ore:upstreamId>https://trynotched.com/find</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hatena-bookmark-technology:479921088c1d6fe84ccbb3b98d4acffd</id>
    <title>なぜヘンリーのE2Eリポジトリは整理されないまま膨らみ続けたのか。 AIで加速した開発とガードレール - 株式会社ヘンリー エンジニアブログ</title>
    <updated>2026-11-18T03:02:46Z</updated>
    <published>2026-11-18T03:02:46Z</published>
    <link rel="alternate" href="https://dev.henry.jp/entry/e2e-repository" />
    <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    <category scheme="urn:ore-news:sources" term="hatena-bookmark-technology" label="Hatena Bookmark Technology" />
    <author>
      <name>Hatena Bookmark Technology</name>
    </author>
    <source>
      <id>urn:ore-news:source:hatena-bookmark-technology</id>
      <title>Hatena Bookmark Technology</title>
      <link rel="alternate" href="https://b.hatena.ne.jp/hotentry/it" />
      <link rel="via" href="https://b.hatena.ne.jp/hotentry/it.rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hatena-bookmark-technology</ore:sourceId>
      <ore:sourceName>Hatena Bookmark Technology</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://b.hatena.ne.jp/hotentry/it</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://b.hatena.ne.jp/hotentry/it.rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://dev.henry.jp/entry/e2e-repository</ore:originalUrl>
      <ore:upstreamId>https://dev.henry.jp/entry/e2e-repository</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:cloudflare-blog:b1bd1adc90104eb7d7841f3ba243bef3</id>
    <title>Quad9’s withdrawal from France: A canary in the coal mine</title>
    <updated>2026-11-17T20:24:27Z</updated>
    <published>2026-11-17T20:24:27Z</published>
    <link rel="alternate" href="https://blog.cloudflare.com/quad9-withdrawal-from-france/" />
    <link rel="via" href="https://blog.cloudflare.com/rss/" />
    <category scheme="urn:ore-news:sources" term="cloudflare-blog" label="Cloudflare Blog" />
    <author>
      <name>Cloudflare Blog</name>
    </author>
    <source>
      <id>urn:ore-news:source:cloudflare-blog</id>
      <title>Cloudflare Blog</title>
      <link rel="alternate" href="https://blog.cloudflare.com/" />
      <link rel="via" href="https://blog.cloudflare.com/rss/" />
    </source>
    <content type="html">&lt;p&gt;Last month, the Swiss non-profit foundation Quad9 &lt;a href="https://quad9.net/news/blog/au-revoir-france/"&gt;&lt;span style="text-decoration:underline"&gt;announced&lt;/span&gt;&lt;/a&gt; that it will withdraw its free public DNS resolver from France. This difficult decision followed months of litigation and a French court ruling that imposed daily financial penalties on Quad9 for failing to block domains associated with alleged copyright infringement.&lt;/p&gt;&lt;p&gt;Quad9’s departure from France is both disheartening and understandable. The court’s ruling put the organization in the impossible bind of having to choose between crippling litigation and penalties, or fundamentally altering its service in a way that would undermine the privacy and security of its users. Left with no good option, Quad9 is choosing the exit door instead.&lt;/p&gt;&lt;p&gt;The withdrawal of a basic infrastructure service from France fundamentally harms the free and open Internet, and it should serve as a warning of the damage that will result if rightsholders and policymakers continue demanding maximal blocking across every layer of the Internet. It not only deprives French Internet users of a trustworthy and important tool; it creates a real risk of disruption to their daily lives. Quad9’s resolver is used by a wide variety of individuals and organizations in France — including government bodies, educational institutions, hospitals, and utilities — and Quad9 has no way to directly notify those individuals and institutions that their resolver will soon stop working. If the affected parties do not change their resolver before Quad9 removes its service, their Internet will fail with no explanation.&lt;/p&gt;&lt;p&gt;Quad9 is not the first public DNS resolver to withdraw from a country following blocking orders, and it almost certainly won’t be the last. Cisco previously withdrew its OpenDNS resolver from France, Portugal, and Belgium (temporarily) under similar circumstances. And a Belgian court recently issued an &lt;a href="https://lawyerd.net/news/brussels-dns-blocking-dazn-google-cloudflare-opendns/"&gt;&lt;span style="text-decoration:underline"&gt;order&lt;/span&gt;&lt;/a&gt; that would impose substantial penalties if Cloudflare, Google, and Cisco do not begin blocking websites through their public resolvers by early January 2027. That’s something Cloudflare has never done.&lt;/p&gt;&lt;p&gt;Cloudflare has spent years advocating against orders of this kind. We are concerned that rightsholders’ unrelenting demands for blocking by public DNS resolvers will end up causing real harm to the Internet.&lt;/p&gt;&lt;h2&gt;A refresher on DNS, the Domain Name System&lt;/h2&gt;&lt;p&gt;To understand why this is such a problem, it helps to understand how the Internet works under the hood. DNS resolvers are a foundational piece of the Internet’s infrastructure. DNS is the Internet’s address book: when you type a website name such as cloudflare.com, the DNS system translates that domain name into the IP address your device needs to connect to it. A DNS resolver is the service that looks up that address and sends it back to your device, much like an operator finding a phone number in a directory.&lt;/p&gt;&lt;p&gt;DNS resolvers can be operated by anyone, but they are commonly run by Internet service providers (ISPs), mobile networks, businesses, and universities. If you’re reading this blog post at home and have never thought about DNS before, chances are that you’re using your ISP’s default resolver. Because you use your DNS resolver every time that you visit a website, it’s important for it to be reliable and trustworthy.&lt;/p&gt;&lt;p&gt;And because the DNS resolver has access to all of your browsing activity, which resolver you use has real privacy implications.&lt;/p&gt;&lt;p&gt;In addition to DNS resolvers that are provided by your local ISP, there are a variety of public DNS resolvers available. Cloudflare launched our public DNS resolver &lt;a href="https://one.one.one.one/"&gt;&lt;span style="text-decoration:underline"&gt;1.1.1.1&lt;/span&gt;&lt;/a&gt; in April 2018 to give back to the Internet. &lt;a href="https://blog.cloudflare.com/announcing-1111/"&gt;&lt;span style="text-decoration:underline"&gt;Our goal&lt;/span&gt;&lt;/a&gt; was to make a fast, reliable, privacy-first consumer DNS service available for free to everyone. We succeeded. 1.1.1.1 is among the fastest DNS resolvers &lt;a href="https://www.dnsperf.com/#!dns-resolvers"&gt;&lt;span style="text-decoration:underline"&gt;in the world&lt;/span&gt;&lt;/a&gt;, including in Europe. Cloudflare&amp;#x27;s resolver doesn’t collect any user data, let alone sell it to advertisers. 1.1.1.1 has always been one of our favorite examples of Cloudflare fulfilling its mission to help build a better Internet.&lt;/p&gt;&lt;p&gt;1.1.1.1 is one of many public resolvers that anyone can use. In addition to 1.1.1.1 and Quad9’s 9.9.9.9, some of the other best-known public resolvers include Google’s 8.8.8.8 and Cisco’s OpenDNS. Just because these services are offered for free doesn’t mean they’re easy to provide. A well-run global public DNS resolver is an extraordinary engineering feat, built to securely and privately resolve hundreds of billions or even trillions of queries a day across a globally distributed network of hundreds of server locations.&lt;/p&gt;&lt;p&gt;As Quad9 notes, there are many other DNS resolvers available to users, many of them offered by essentially anonymous services whose practices are unknown or undocumented. It’s easy to change your DNS resolver, and people do so for a variety of reasons including performance, reliability, or to access specific security features.&lt;/p&gt;&lt;h2&gt;Why public DNS resolvers should not be required to block&lt;/h2&gt;&lt;p&gt;Rightsholders have a legitimate interest in preventing online piracy. But trying to address online infringement through public DNS resolvers is fundamentally the wrong approach.&lt;/p&gt;&lt;p&gt;Among other things, such blocking is ineffective. Think back to the analogy of an operator finding a phone number in a directory. If a court wants to shut down an illegal business, forcing the directory operator to cross the business&amp;#x27;s name out of the phone book doesn&amp;#x27;t actually close the business. The storefront is still open, the products are still there, and anyone who already knows the address, or uses a different phone book, can walk in.&lt;/p&gt;&lt;p&gt;The same is true for the Internet. DNS resolvers are just one link in the transmission chain. The only way a DNS resolver can “block” content is by declining to return the IP address for a particular website. But a public DNS resolver cannot remove the actual infringing content from the Internet, nor can it take down the servers hosting it.&lt;/p&gt;&lt;p&gt;Because of this, blocking by public DNS resolvers is remarkably easy to bypass. Any Internet user who wants to reach a blocked site can circumvent the block in less than a minute simply by switching to one of the thousands of other DNS resolvers available online. In fact, users don’t even need a resolver at all to reach infringing content if they already know the underlying IP address. Unsurprisingly, while blocking via public resolvers may inject some friction for some users when accessing content, there is no evidence that it actually reduces the total amount of online infringement that occurs.&lt;/p&gt;&lt;p&gt;In addition to being ineffective, as we’ve &lt;a href="https://blog.cloudflare.com/latest-copyright-decision-in-germany-rejects-blocking-through-global-dns-resolvers/"&gt;&lt;span style="text-decoration:underline"&gt;written previously&lt;/span&gt;&lt;/a&gt;, DNS blocking is a blunt instrument that causes collateral damage. Because DNS operates at the domain level, a resolver cannot block a specific infringing video or file; it must block the entire domain. This affects all content on that domain, whether legal or illegal. It is also entirely opaque to the user: when a resolver is forced to block a domain, the website simply fails to load. The user receives no explanation or legal notice, making it impossible to know if the site is down for maintenance, if their network is broken, or if the site was blocked by a court order.&lt;/p&gt;&lt;p&gt;The problem is substantially worse with respect to public DNS resolvers. Because public resolvers operate globally, any blocking will naturally cross borders, meaning that a single country could dictate what content is accessible around the world. For example, while the EU-dedicated DNS resolver DNS4EU operated by Whalebone blocks in response to country-specific orders, it does so across the entire EU. Efforts to reengineer public DNS resolvers to allow for more localized blocking would fundamentally alter the service, harming performance and resilience, undermining user privacy, and fragmenting the open Internet.&lt;/p&gt;&lt;p&gt;For these reasons, Cloudflare, Google, Cisco, and Quad9 have all opposed efforts to mandate blocking by public DNS resolvers, with some success. Several years ago, courts in Germany ruled in favor of &lt;a href="https://blog.cloudflare.com/latest-copyright-decision-in-germany-rejects-blocking-through-global-dns-resolvers/"&gt;&lt;span style="text-decoration:underline"&gt;Cloudflare&lt;/span&gt;&lt;/a&gt; and &lt;a href="https://quad9.net/news/blog/quad9-turns-the-sony-case-around-in-dresden/"&gt;&lt;span style="text-decoration:underline"&gt;Quad9&lt;/span&gt;&lt;/a&gt;, rejecting requests to require DNS blocking. More recently, a French court &lt;a href="https://torrentfreak.com/cloudflare-keeps-1-1-1-1-out-of-piracy-blocking-escapes-penalties-in-france/"&gt;&lt;span style="text-decoration:underline"&gt;rejected&lt;/span&gt;&lt;/a&gt; penalties against Cloudflare for failing to block through 1.1.1.1, finding that other actions we had taken through our CDN and reverse-proxy service were sufficient to comply with the underlying order.&lt;/p&gt;&lt;p&gt;Undeterred, rightsholders have continued to press for blocking by public resolvers with a level of determination that is hard to explain. A recent study &lt;a href="https://labs.ripe.net/author/antonio-prado/live-event-blocking-at-scale-effectiveness-vs-collateral-damage-in-italys-piracy-shield/"&gt;&lt;span style="text-decoration:underline"&gt;found&lt;/span&gt;&lt;/a&gt; that the majority of online piracy in Europe is hosted in Europe. If rightsholders want to genuinely address online infringement, there are far better places to focus their efforts — most notably by requiring the hosting providers who actually store the pirated files to take them down.&lt;/p&gt;&lt;h2&gt;Forcing public DNS resolvers out of markets hurts the Internet&lt;/h2&gt;&lt;p&gt;The French court’s penalty order against Quad9 represents the culmination of these rightsholder efforts. As a small non-profit that only offers a public DNS resolver, Quad9 had no alternative methods for demonstrating compliance with the order. The French court therefore granted rightsholders’ request to issue penalties for non-compliance, forcing Quad9 to undermine its own service or leave the country.&lt;/p&gt;&lt;p&gt;Quad9’s withdrawal from France represents a genuine loss for the Internet. In the short term, removal of Quad9’s resolver is likely to cause immediate and potentially severe disruptions to Internet access. Because of the way their service is set up to preserve privacy, Quad9 has no way to know who exactly is using its resolver, let alone to directly communicate to them about the upcoming withdrawal of services. That means that individuals, hospitals, universities, and government offices all may be caught unaware when the resolver stops working. Again, because of how DNS resolvers work, those users will not receive a detailed error message explaining what happened — their Internet will simply stop working. The problem will be even worse when devices like security systems or thermostats are hardwired to use Quad9’s resolver. Fixing these issues may be slow or even impossible.&lt;/p&gt;&lt;p&gt;More generally, driving Quad9 out of France does absolutely nothing to prevent online infringement, but it does leave everyday Internet users with fewer safe, reliable options, particularly ones like Quad9 that also protect users from phishing and malware. Taking established public DNS resolvers away forces Internet users to fall back on the default resolvers offered by their ISPs (which may monetize their browsing data), try lesser-known resolvers operated by anonymous or less trustworthy organizations, or run their own resolver. The irony is that Quad9 and Cloudflare are being pulled into court precisely because we are transparent, reputable organizations. Penalizing transparent services only pushes users toward less accountable corners of the web.&lt;/p&gt;&lt;h2&gt;The way forward&lt;/h2&gt;&lt;p&gt;If nothing else, we hope that Quad9’s announcement may serve as a wake-up call to rightsholders and policymakers that seeking to block infringement at every layer of the Internet has real costs.&lt;/p&gt;&lt;p&gt;We believe there are far better ways to work together to fight piracy without compromising the integrity of the Internet, and Cloudflare continues to pursue &lt;a href="https://blog.cloudflare.com/h1-2025-transparency-report#innovating-to-address-abuse-and-identify-new-threats"&gt;&lt;span style="text-decoration:underline"&gt;innovative collaborations&lt;/span&gt;&lt;/a&gt; to that end. Our collective efforts in addressing online infringement would be put to better use in seeking to have such content removed at the hosting provider, which would both achieve a more durable solution and avoid collateral damage to the Internet.&lt;/p&gt;&lt;p&gt;In the meantime, we will keep resisting misguided efforts to require blocking by public DNS resolvers. Along with Google and Cisco, we have appealed the Belgian order that would impose penalties on us if we do not start DNS blocking by January 2027. We hope to get a resolution before the end of the year that would avoid another situation like the one Quad9 faces now in France.&lt;/p&gt;&lt;p&gt;We have grave concerns about the disruption that would be caused if additional resolvers are forced to withdraw from markets, and we will continue to advocate against that possible result.&lt;/p&gt;&lt;p&gt;&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>cloudflare-blog</ore:sourceId>
      <ore:sourceName>Cloudflare Blog</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://blog.cloudflare.com/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://blog.cloudflare.com/rss/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://blog.cloudflare.com/quad9-withdrawal-from-france/</ore:originalUrl>
      <ore:upstreamId>01M7NJA4ESQ31MDVBT2RBP1ZHX</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hacker-news:85181d6d286d6d17c87b9c36ffb1aba9</id>
    <title>Valkey kills the skiplist, cuts sorted set overhead by up to 43%</title>
    <updated>2026-11-17T16:58:30Z</updated>
    <published>2026-11-17T16:58:30Z</published>
    <link rel="alternate" href="https://valkey.io/blog/from-skiplist-to-b+tree/" />
    <link rel="via" href="https://news.ycombinator.com/rss" />
    <category scheme="urn:ore-news:sources" term="hacker-news" label="Hacker News" />
    <author>
      <name>Hacker News</name>
    </author>
    <source>
      <id>urn:ore-news:source:hacker-news</id>
      <title>Hacker News</title>
      <link rel="alternate" href="https://news.ycombinator.com/" />
      <link rel="via" href="https://news.ycombinator.com/rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hacker-news</ore:sourceId>
      <ore:sourceName>Hacker News</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://news.ycombinator.com/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://news.ycombinator.com/rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://valkey.io/blog/from-skiplist-to-b+tree/</ore:originalUrl>
      <ore:upstreamId>https://valkey.io/blog/from-skiplist-to-b+tree/</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:simon-willison:e66c77687255a22b84ac086e5f97d58a</id>
    <title>Running the full server-side Datasette Python app in the browser with service workers and Pyodide</title>
    <updated>2026-11-17T16:48:33Z</updated>
    <published>2026-11-17T16:48:33Z</published>
    <link rel="alternate" href="https://simonwillison.net/2026/Nov/17/datasette-lite/" />
    <link rel="via" href="https://simonwillison.net/atom/entries/" />
    <category scheme="urn:ore-news:sources" term="simon-willison" label="Simon Willison's Weblog" />
    <author>
      <name>Simon Willison's Weblog</name>
    </author>
    <source>
      <id>urn:ore-news:source:simon-willison</id>
      <title>Simon Willison's Weblog</title>
      <link rel="alternate" href="https://simonwillison.net/" />
      <link rel="via" href="https://simonwillison.net/atom/entries/" />
    </source>
    <content type="text">&lt;p&gt;&lt;a href="https://lite.datasette.io/"&gt;Datasette Lite&lt;/a&gt; is my port of the &lt;a href="https://datasette.io/"&gt;Datasette&lt;/a&gt; Python application to run directly in the browser using WebAssembly and &lt;a href="https://pyodide.org/"&gt;Pyodide&lt;/a&gt;. I've released a complete rewrite of Datasette Lite using service workers, and it's now almost indistinguishable from the real server-side application.&lt;/p&gt;
&lt;p&gt;You can now do all of the following, using a carefully crafted URL to &lt;strong&gt;lite.datasette.io&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Load client-side Datasette to browse any SQLite database, JSON file, CSV file or SQL script&lt;/li&gt;
&lt;li&gt;Select a released version of Datasette to load from PyPI&lt;/li&gt;
&lt;li&gt;Load a specific commit, tag, or branch name from the Datasette GitHub repository&lt;/li&gt;
&lt;li&gt;Pick from over 100 versions of SQLite to use with Datasette&lt;/li&gt;
&lt;li&gt;Install additional Datasette plugins from PyPI or URLs to wheel files, including JavaScript visualization tools&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The ability to load specific Datasette references, plugins, and SQLite versions makes this a fantastic tool for linking to demos of work-in-progress features or bug reproductions, without needing to spin up a full web server to serve that demo.&lt;/p&gt;
&lt;p&gt;As an example, consider the following URL:&lt;/p&gt;
&lt;p&gt;&lt;a href="https://lite.datasette.io/?install=datasette-maplibre&amp;amp;url=https://gist.githubusercontent.com/simonw/39fa5d399465766039549912e2b3d291/raw/f6dfba99a75cbb8b5d9386223220eb52272767ee/demo.db&amp;amp;metadata=https://gist.githubusercontent.com/simonw/39fa5d399465766039549912e2b3d291/raw/f6dfba99a75cbb8b5d9386223220eb52272767ee/metadata.yml#/demo/capitals_and_countries%23map=0/4.2/180&amp;amp;color=continent"&gt;https://lite.datasette.io/?install=datasette-maplibre&amp;amp;url=https://gist.githubusercontent.com/simonw/39fa5d399465766039549912e2b3d291/raw/f6dfba99a75cbb8b5d9386223220eb52272767ee/demo.db&amp;amp;metadata=https://gist.githubusercontent.com/simonw/39fa5d399465766039549912e2b3d291/raw/f6dfba99a75cbb8b5d9386223220eb52272767ee/metadata.yml#/demo/capitals_and_countries%23map=0/4.2/180&amp;amp;color=continent&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Follow that link and, after a short loading screen, you'll find yourself on a page that looks like this:&lt;/p&gt;
&lt;p&gt;&lt;img src="https://static.simonwillison.net/static/cors-allow/2026/datasette-maplibre.webp" alt="Screenshot of a web map interface. Toolbar: &amp;quot;View&amp;quot; set to &amp;quot;Clusters&amp;quot;, &amp;quot;Colour by&amp;quot; set to &amp;quot;continent&amp;quot;, plus &amp;quot;Filter to this area&amp;quot; and &amp;quot;Download GeoJSON&amp;quot; buttons. A world map shows countries outlined and shaded by continent, with coloured dots and numbered cluster circles. A popup for a point in South America reads: capital Caracas, country Venezuela, continent South America, capital_population 2985000, latitude 10.502944, longitude -66.918983. Legend: Africa (52), Asia (45), Europe (39), North America (16), South America (13), Oceania (6). Text: &amp;quot;All 171 rows are on the map&amp;quot;. Below, a table with columns country, continent, capital_population, latitude, longitude, boundary. First row: Afghanistan, Asia, 3277000, 34.518636, 69.181314, with a small map in the boundary column showing Afghanistan outlined and shaded in blue." style="max-width: 100%;" /&gt;&lt;/p&gt;
&lt;p&gt;That's Datasette running the new &lt;a href="https://github.com/datasette/datasette-maplibre"&gt;datasette-maplibre&lt;/a&gt; plugin, loading up a database of GeoJSON shapes of countries and displaying both a combined map and individual boundary maps in a table.&lt;/p&gt;
&lt;p&gt;Let's break down that URL to see what it's doing:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;https://lite.datasette.io/
  ?install=datasette-maplibre
  &amp;amp;url=https://.../demo.db
  &amp;amp;metadata=https://.../metadata.yml
  #/demo/capitals_and_countries%23map=0/4.2/180&amp;amp;color=continent
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;The &lt;code&gt;?install=datasette-maplibre&lt;/code&gt; installs that additional plugin from PyPI. You can pass &lt;code&gt;&amp;amp;install=...&lt;/code&gt; as many times as you like to load more plugins.&lt;/p&gt;
&lt;p&gt;&lt;code&gt;&amp;amp;url=https://.../demo.db&lt;/code&gt; loads that SQLite database from the provided URL. These URLs need to have &lt;a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CORS"&gt;open CORS headers&lt;/a&gt; - I host files like this in &lt;a href="https://gist.github.com/"&gt;Gists&lt;/a&gt;, because they provide an easy way to get open CORS headers on a web-hosted file.&lt;/p&gt;
&lt;p&gt;&lt;code&gt;&amp;amp;metadata=https://.../metadata.yml&lt;/code&gt; loads &lt;a href="https://gist.githubusercontent.com/simonw/39fa5d399465766039549912e2b3d291/raw/f6dfba99a75cbb8b5d9386223220eb52272767ee/metadata.yml"&gt;this metadata.yml file&lt;/a&gt;. The metadata file adds HTML descriptions to various tables, and to the Datasette homepage. Visit &lt;a href="https://lite.datasette.io/?install=datasette-maplibre&amp;amp;url=https://gist.githubusercontent.com/simonw/39fa5d399465766039549912e2b3d291/raw/f6dfba99a75cbb8b5d9386223220eb52272767ee/demo.db&amp;amp;metadata=https://gist.githubusercontent.com/simonw/39fa5d399465766039549912e2b3d291/raw/f6dfba99a75cbb8b5d9386223220eb52272767ee/metadata.yml#/"&gt;that homepage here&lt;/a&gt; for a guided tour of the other features of that plugin, all defined in the metadata file.&lt;/p&gt;
&lt;p&gt;&lt;code&gt;#/demo/capitals_and_countries%23map=0/4.2/180&amp;amp;color=continent&lt;/code&gt; is a fragment hash that turns into a location within Datasette - here it's loading the &lt;code&gt;/demo/capitals_and_countries&lt;/code&gt; SQL view, then appending &lt;em&gt;another&lt;/em&gt; fragment hash to it (&lt;code&gt;%23&lt;/code&gt; is a URL-encoded &lt;code&gt;#&lt;/code&gt;) which tells the map plugin to zoom to a certain location and to set the color of the shapes on the map based on the &lt;code&gt;continent&lt;/code&gt; column in the data.&lt;/p&gt;
&lt;p&gt;That URL is doing a lot of work! I wrote more about this trick for building URL-addressable software in &lt;a href="https://simonwillison.net/2025/Feb/13/url-addressable-python/"&gt;URL-addressable Pyodide Python environments&lt;/a&gt; last year.&lt;/p&gt;
&lt;p&gt;The full set of supported URL arguments is &lt;a href="https://github.com/simonw/datasette-lite#load-a-different-datasette-version"&gt;described in the Datasette Lite README&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;I've already started using Datasette Lite as part of the Datasette development process. Here's &lt;a href="https://github.com/simonw/datasette/issues/3056#issuecomment-6902484982"&gt;a recent issue&lt;/a&gt; describing a pagination bug - I posted a comment there demonstrating the old, broken behavior and the new fix using links to Datasette Lite:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Demo of the bug: &lt;a href="https://lite.datasette.io/?ref=1.0a42&amp;amp;sql=https://gist.github.com/simonw/75ececf61d50e6e8d50f0c150150ee81#/data/scores?_size=2&amp;amp;_sort=score"&gt;https://lite.datasette.io/?ref=1.0a42&amp;amp;sql=https://gist.github.com/simonw/75ececf61d50e6e8d50f0c150150ee81#/data/scores?_size=2&amp;amp;_sort=score&lt;/a&gt; - click next and the second page is empty.&lt;/p&gt;
&lt;p&gt;Here's that same page with the bug fixed (running on 1.0a43): &lt;a href="https://lite.datasette.io/?ref=1.0a43&amp;amp;sql=https://gist.github.com/simonw/75ececf61d50e6e8d50f0c150150ee81#/data/scores?_size=2&amp;amp;_sort=score"&gt;https://lite.datasette.io/?ref=1.0a43&amp;amp;sql=https://gist.github.com/simonw/75ececf61d50e6e8d50f0c150150ee81#/data/scores?_size=2&amp;amp;_sort=score&lt;/a&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h4 id="how-this-works-using-service-workers"&gt;How this works, using service workers&lt;/h4&gt;
&lt;p&gt;Datasette Lite is not a new project. I launched the first version &lt;a href="https://simonwillison.net/2022/May/4/datasette-lite/"&gt;back in 2022&lt;/a&gt;, originally as a bit of a joke (running server-side apps in the browser is pretty funny) but one that quickly started proving its value.&lt;/p&gt;
&lt;p&gt;The problem with that initial version is that it was a &lt;em&gt;hack&lt;/em&gt;. It worked by running Datasette in a Pyodide web worker, simulating requests through that stack, then injecting the resulting HTML back into the top level page using &lt;code&gt;innerHTML&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;This worked for basic Datasette, but meant that any feature that used JavaScript failed to work, because script tags in &lt;code&gt;innerHTML&lt;/code&gt; don't execute, and the web worker tricks it used failed to load additional JavaScript or CSS files.&lt;/p&gt;
&lt;p&gt;The new version takes a completely different approach based on &lt;a href="https://developer.mozilla.org/en-US/docs/Web/API/Service_Worker_API"&gt;Service Workers&lt;/a&gt;. These allow JavaScript to intercept HTTP requests for new pages and resources and serve them from client-side code instead.&lt;/p&gt;
&lt;p&gt;Datasette Lite registers a service worker for the entire &lt;code&gt;lite.datasette.io&lt;/code&gt; domain. The parent page then creates an iframe that sends requests for Datasette pages to URLs that look like this:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;/app/aa94e6851595/ # the homepage (HTML)
/app/aa94e6851595/data/places # a table page (HTML)
/app/aa94e6851595/-/static/navigation-search.js # (JavaScript)
/app/aa94e6851595/-/static/app.css # (CSS)
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Those are regular Datasette URLs, but with a &lt;code&gt;/app/aa94e6851595/&lt;/code&gt; prefix. What's that about?&lt;/p&gt;
&lt;p&gt;The &lt;code&gt;/app/&amp;lt;session&amp;gt;/&lt;/code&gt; prefix is necessary because of multiple tabs.&lt;/p&gt;
&lt;p&gt;Consider the URL above, which loads the demo instance with the &lt;code&gt;datasette-maplibre&lt;/code&gt; plugin. That URL defines a full, custom Datasette instance. You might have that one running in a tab, then one of my other demo links running in another.&lt;/p&gt;
&lt;p&gt;The service worker for &lt;code&gt;lite.datasette.io&lt;/code&gt; is shared between all of those tabs. If it routed to a single instance of Datasette then every tab would share that underlying instance, no matter what plugins or other settings their URL attempted to configure.&lt;/p&gt;
&lt;p&gt;Instead, the parent page generates a random session ID and uses it as a prefix for all of the subsequent hidden asset and page loads. The service worker can then use that session ID to route those requests back through the parent page to a web worker running a dedicated Datasette instance for that particular session.&lt;/p&gt;
&lt;p&gt;(We still need a web worker because Pyodide in a service worker would not be able to maintain state beyond around 30 seconds, depending on the browser. There are a lot of moving parts here!)&lt;/p&gt;
&lt;p&gt;I had Claude Fable 5.2 &lt;a href="https://gisthost.github.io/?4192a5a24136cad4c8490ccb15e87d83"&gt;generate several SVG diagrams&lt;/a&gt; to help explain this. Here's my favorite of those, now embedded in the Datasette Lite README:&lt;/p&gt;
&lt;p&gt;&lt;img src="https://static.simonwillison.net/static/2026/datasette-lite-diag.webp" alt="Architecture diagram titled &amp;quot;What happens when you click a link in Datasette Lite&amp;quot;, with a legend showing a solid arrow for &amp;quot;request&amp;quot; and a dashed arrow for &amp;quot;response&amp;quot;. A blue box labeled &amp;quot;index.html: the page you opened - Each tab picks a random session and starts one Web Worker.&amp;quot; contains two white boxes: &amp;quot;iframe Datasette pages at /app/session/…&amp;quot; and &amp;quot;shell.js the page's own script: relays&amp;quot;. Below it is a yellow box labeled &amp;quot;sw.js: the service worker - Intercepts requests for /app/session/….&amp;quot; To the right is a green box marked 4 and labeled &amp;quot;webworker.js: a Web Worker - Pyodide: Python in WebAssembly&amp;quot; containing three stacked white boxes: &amp;quot;ASGI bridge + cookie jar&amp;quot;, &amp;quot;Datasette ASGI app&amp;quot; and &amp;quot;SQLite databases&amp;quot;. Numbered arrows connect them: solid arrow 1 from the iframe down to sw.js, solid arrow 2 from sw.js up to shell.js, solid arrow 3 from shell.js across to the Web Worker, dashed arrow 5 from the Web Worker back to shell.js, dashed arrow 6 from shell.js down to sw.js, and dashed arrow 7 from sw.js up to the iframe. A numbered key at the bottom reads: 1 The page requests /app/session/fixtures. 2 sw.js intercepts it and posts it to the owning tab. 3 shell.js forwards it to the Web Worker. 4 Python adds cookies and calls Datasette, which queries SQLite. 5 The status, headers and body return to the page, 6 then to sw.js over a MessagePort, 7 which hands the browser a Response. The iframe renders it." style="max-width: 100%;" /&gt;&lt;/p&gt;
&lt;p&gt;This system started life &lt;a href="https://simonwillison.net/2026/May/30/pyodide-asgi-browser/"&gt;back in May&lt;/a&gt; as an &lt;a href="https://github.com/simonw/research/tree/main/pyodide-asgi-browser#readme"&gt;AI research spike&lt;/a&gt; generated using Claude Opus 4.8. It wasn't until November (and Claude Fable 5.2) that I felt familiar enough with how it all works to confidently ship it to production!&lt;/p&gt;
&lt;h4 id="bonus-feature-pick-your-version-of-sqlite"&gt;Bonus feature: pick your version of SQLite&lt;/h4&gt;
&lt;p&gt;I added this feature &lt;a href="https://github.com/simonw/datasette-lite/commit/de661dbee42a68304811a0035b78e6b683203cd1"&gt;last night&lt;/a&gt; as an off-shoot of investigating &lt;a href="https://simonwillison.net/2026/Nov/16/llm/"&gt;a potential bug in SQLite&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Datasette is meant to work against any released version of SQLite since 3.25 (released in September 2018). There have been 87 further releases since then.&lt;/p&gt;
&lt;p&gt;Being able to fire up Datasette against a specific version of SQLite is really useful for demonstrating new SQLite features and debugging weird issues.&lt;/p&gt;
&lt;p&gt;In the past I've &lt;a href="https://til.simonwillison.net/sqlite/sqlite-version-macos-python"&gt;used various tricks&lt;/a&gt; to get different SQLite versions running with Python on my Mac, but it's not a trivial process.&lt;/p&gt;
&lt;p&gt;WebAssembly is perfect for this. I can load up a custom SQLite build entirely in my browser, test it there, then discard it when I close my tab.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://github.com/datasette/pysqlite3-wasm-wheels"&gt;datasette/pysqlite3-wasm-wheels&lt;/a&gt; is my new repository which contains WebAssembly compiled Python wheels for &lt;a href="https://github.com/coleifer/pysqlite3"&gt;pysqlite3&lt;/a&gt; for 163 different SQLite versions. Each version gets a file with a name like this:&lt;/p&gt;
&lt;p&gt;&lt;code&gt;pysqlite3-0.6.2-3.54.1-cp314-cp314-pyemscripten_2026_0_wasm32.whl&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;That's for SQLite 3.54.1, the most recent version.&lt;/p&gt;
&lt;p&gt;Datasette Lite now takes a special &lt;code&gt;?sqlite=&lt;/code&gt; URL parameter, which will accept a version number like &lt;code&gt;3.54.1&lt;/code&gt;, resolve the path to the corresponding wheel file, then fetch that wheel and install it into the Pyodide environment and configure Datasette to use it.&lt;/p&gt;
&lt;p&gt;Once I'd built the wheels, I decided to have Claude Fable 5.2 build me &lt;a href="https://datasette.github.io/pysqlite3-wasm-wheels/?versions=3.54.1,3.54.0&amp;amp;sql=select+json_object(%27a%27%2C+(select+json_array(1%29%29%29)"&gt;https://datasette.github.io/pysqlite3-wasm-wheels/?versions=3.54.1,3.54.0&amp;amp;sql=select+json_object(%27a%27%2C+(select+json_array(1%29%29%29)"&gt;this bonus tool&lt;/a&gt; for comparing a SQL query across any selected versions of SQLite. Here's an example showing how &lt;code&gt;select json_object('a', (select json_array(1)))&lt;/code&gt; differs between SQLite 3.54.0 and 3.54.1:&lt;/p&gt;
&lt;p&gt;&lt;img src="https://static.simonwillison.net/static/2026/compare-sqlite.webp" alt="Screenshot of a web tool for comparing SQL across SQLite versions. Heading &amp;quot;SQLite versions (163 available)&amp;quot; sits above a filter text input with placeholder &amp;quot;Filter, e.g. 3.4&amp;quot;, a &amp;quot;Clear selection&amp;quot; button and a blue &amp;quot;Start REPL with 2 versions&amp;quot; button. Below is a scrollable grid of pill-shaped checkboxes, one per version, running from 3.54.1 down past 3.30.0, with 3.54.1 and 3.54.0 checked. A &amp;quot;REPL&amp;quot; heading follows, with two green status badges reading &amp;quot;3.54.1 ready&amp;quot; and &amp;quot;3.54.0 ready&amp;quot;, then a textarea containing &amp;quot;select json_object('a', (select json_array(1)))&amp;quot; beside a blue &amp;quot;Run&amp;quot; button, and a row of clickable example queries labeled &amp;quot;Examples:&amp;quot;. The output section shows the prompt &amp;quot;sqlite&amp;gt; select json_object('a', (select json_array(1)))&amp;quot; followed by an orange warning &amp;quot;Versions differ: 2 different results&amp;quot; and two side-by-side yellow result panels, each with the query as its column header. The &amp;quot;SQLite 3.54.1&amp;quot; panel returns a JSON object where key &amp;quot;a&amp;quot; has a string value: the array containing 1, wrapped in double quotes. The &amp;quot;SQLite 3.54.0&amp;quot; panel returns a JSON object where key &amp;quot;a&amp;quot; has an actual array containing 1, with no quotes around it." style="max-width: 100%;" /&gt;&lt;/p&gt;
&lt;h4 id="this-should-work-for-every-other-python-app-too"&gt;This should work for every other Python app, too&lt;/h4&gt;
&lt;p&gt;Nothing about how Datasette Lite works is unique to Datasette. Almost any Python application should be able to pull the same trick - running entirely in the browser using WebAssembly and Pyodide, as a cheap way to provide preview environments, demonstrate features, and recreate bugs.&lt;/p&gt;
&lt;p&gt;C and Rust extensions used to be a blocker for this kind of thing, but any good coding agent can compile those to Pyodide-compatible WebAssembly now. You can &lt;a href="https://github.com/pypi/warehouse/pull/19804"&gt;even publish them to PyPI&lt;/a&gt; as of PEP 783 in April 2026.&lt;/p&gt;
&lt;p&gt;One catch is databases. SQLite is no problem at all, but running PostgreSQL or MySQL in WebAssembly, while possible, is still a path less trodden.&lt;/p&gt;
&lt;p&gt;I'd love to see WebAssembly preview environments like these become a common pattern across the Python ecosystem.&lt;/p&gt;&lt;p&gt;&lt;em&gt;You are only seeing the long-form articles from my blog. Subscribe to &lt;a href="https://simonwillison.net/atom/everything/"&gt;/atom/everything/&lt;/a&gt; to get all of my posts, or take a look at my &lt;a href="https://simonwillison.net/about/#subscribe"&gt;other subscription options&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;</content>
    <ore:provenance>
      <ore:sourceId>simon-willison</ore:sourceId>
      <ore:sourceName>Simon Willison's Weblog</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://simonwillison.net/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://simonwillison.net/atom/entries/</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://simonwillison.net/2026/Nov/17/datasette-lite/</ore:originalUrl>
      <ore:upstreamId>https://simonwillison.net/2026/Nov/17/datasette-lite/</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hermes-agent-releases:87a874edee0d4318605e3b52b31e6ea0</id>
    <title>Hermes Agent canary v0.23.2+canary.20261117T064624Z</title>
    <updated>2026-11-17T07:54:16Z</updated>
    <published>2026-11-17T07:54:16Z</published>
    <link rel="alternate" href="https://github.com/NousResearch/hermes-agent/releases/tag/v0.23.2%2Bcanary.20261117T064624Z" />
    <link rel="via" href="https://api.github.com/repos/NousResearch/hermes-agent/releases" />
    <category scheme="urn:ore-news:sources" term="hermes-agent-releases" label="Hermes Agent GitHub Releases" />
    <author>
      <name>Hermes Agent GitHub Releases</name>
    </author>
    <source>
      <id>urn:ore-news:source:hermes-agent-releases</id>
      <title>Hermes Agent GitHub Releases</title>
      <link rel="alternate" href="https://github.com/NousResearch/hermes-agent/releases" />
      <link rel="via" href="https://api.github.com/repos/NousResearch/hermes-agent/releases" />
    </source>
    <content type="text"># Hermes Agent v0.23.2+canary.20261117T064624Z (v0.23.2+canary.20261117T064624Z)

**Release Date:** November 17, 2026

&lt;!-- HERMES_BUILDS_TABLE --&gt;
## Downloads

### Hermes Desktop

| OS | Architecture | Download |
|---|---|---|
| macOS | Apple Silicon (M-series) | [DMG](https://hermes-assets.nousresearch.com/releases/tag/v0.23.2%2Bcanary.20261117T064624Z/HermesBundled-0.23.2%2Bcanary.20261117T064624Z-mac-arm64.dmg) |
| Windows | x86 (64-bit) | [MSIX](https://hermes-assets.nousresearch.com/releases/tag/v0.23.2%2Bcanary.20261117T064624Z/HermesBundled-0.23.2%2Bcanary.20261117T064624Z-win-x64.msix) |
| Windows | ARM (arm64 / aarch64) | [MSIX](https://hermes-assets.nousresearch.com/releases/tag/v0.23.2%2Bcanary.20261117T064624Z/HermesBundled-0.23.2%2Bcanary.20261117T064624Z-win-arm64.msix) |

### Native install/chat smoke

Download availability is independent of smoke status. Each result covers all native legs in that format group. Linux bundles are disabled; unsigned Store envelopes are not install-smoked. No-upload dry tags have no download handoff and are not smoke-qualified.

| Packages | Smoke status |
|---|---|
| macOS DMG + ZIP (arm64) | Passed |
| Windows MSIX (arm64) | Passed |
| Windows MSIX (x64) | Passed |
&lt;!-- /HERMES_BUILDS_TABLE --&gt;

## ✨ Features

- Plugin-catalog): add opendockit plugin ([`3cf52227`](https://github.com/NousResearch/hermes-agent/commit/3cf522275736592abb9540154b6de50814165144)) — @hyeonsang010716

## 🔧 Improvements

- Teams): move the Microsoft Graph auth and client into the teams_pipeline plugin ([`40d1e95f`](https://github.com/NousResearch/hermes-agent/commit/40d1e95f37e409f9f618f32c170661c66b86a4f4)) — @alt-glitch
- Agent): six checkpoint files move from tools/ to agent/checkpoints/ ([`458a0046`](https://github.com/NousResearch/hermes-agent/commit/458a0046ad6ce75f6f7b2705f592b9c7a749fe14)) — @alt-glitch

## 🐛 Bug Fixes

- Update-check): the passive check's git ls-remote dies with the CLI ([`60503775`](https://github.com/NousResearch/hermes-agent/commit/605037755ad3ffa2ec9d8304447d9cc150db1e73))
- Desktop): an adopted reply drops its late tail by stream offset, in raw form ([`e87a591d`](https://github.com/NousResearch/hermes-agent/commit/e87a591d9b973fa912ef227a7764edb341b978ac))

## 🧪 Tests

- Update-check): fill the child script's SHA with replace, not % (ruff UP031) ([`631e406f`](https://github.com/NousResearch/hermes-agent/commit/631e406f57b2d6fc6a65eb189d8ae0c8afb3f44c))

## 👥 Contributors

Thank you to everyone who contributed to this release!

- @BearHuddleston (8 commits)
- @alt-glitch (2 commits)
- @SHL0MS (2 commits)
- @kvnloo (1 commit)
- @hyeonsang010716 (1 commit)

**Full Changelog**: [v0.23.1+canary.20261116T070005Z...v0.23.2+canary.20261117T064624Z](https://github.com/NousResearch/hermes-agent/compare/v0.23.1+canary.20261116T070005Z...v0.23.2+canary.20261117T064624Z)</content>
    <ore:provenance>
      <ore:sourceId>hermes-agent-releases</ore:sourceId>
      <ore:sourceName>Hermes Agent GitHub Releases</ore:sourceName>
      <ore:sourceType>github_releases</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://github.com/NousResearch/hermes-agent/releases</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://api.github.com/repos/NousResearch/hermes-agent/releases</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://github.com/NousResearch/hermes-agent/releases/tag/v0.23.2%2Bcanary.20261117T064624Z</ore:originalUrl>
      <ore:upstreamId>RE_kwDOPRF1G84at89N</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hacker-news:47888d3de99d553ed9f60b375330c8a2</id>
    <title>Show HN: I made an audio-to-MIDI model 60x more efficient</title>
    <updated>2026-11-17T01:03:05Z</updated>
    <published>2026-11-17T01:03:05Z</published>
    <link rel="alternate" href="https://kobi.music/research/dettato" />
    <link rel="via" href="https://news.ycombinator.com/rss" />
    <category scheme="urn:ore-news:sources" term="hacker-news" label="Hacker News" />
    <author>
      <name>Hacker News</name>
    </author>
    <source>
      <id>urn:ore-news:source:hacker-news</id>
      <title>Hacker News</title>
      <link rel="alternate" href="https://news.ycombinator.com/" />
      <link rel="via" href="https://news.ycombinator.com/rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hacker-news</ore:sourceId>
      <ore:sourceName>Hacker News</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://news.ycombinator.com/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://news.ycombinator.com/rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://kobi.music/research/dettato</ore:originalUrl>
      <ore:upstreamId>https://kobi.music/research/dettato</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hermes-agent-releases:8938dcb3d9b6fb856e5ffb7485f91fc4</id>
    <title>Hermes Agent v0.23.2</title>
    <updated>2026-11-19T15:28:07Z</updated>
    <published>2026-11-16T20:59:18Z</published>
    <link rel="alternate" href="https://github.com/NousResearch/hermes-agent/releases/tag/v0.23.2" />
    <link rel="via" href="https://api.github.com/repos/NousResearch/hermes-agent/releases" />
    <category scheme="urn:ore-news:sources" term="hermes-agent-releases" label="Hermes Agent GitHub Releases" />
    <author>
      <name>Hermes Agent GitHub Releases</name>
    </author>
    <source>
      <id>urn:ore-news:source:hermes-agent-releases</id>
      <title>Hermes Agent GitHub Releases</title>
      <link rel="alternate" href="https://github.com/NousResearch/hermes-agent/releases" />
      <link rel="via" href="https://api.github.com/repos/NousResearch/hermes-agent/releases" />
    </source>
    <content type="text"># Hermes Agent v0.23.2

**Release Date:** November 16, 2026

&gt; Patch release. This tag rolls up the ~1,989 PRs merged since v0.23.1 into a stable release for the GitHub release (CLI and installers), the Microsoft Store app, Docker and Hermes Cloud. Full curated notes for this window ship with v0.24.0.

&lt;!-- HERMES_BUILDS_TABLE --&gt;

## About this release

Measured at commit `ae2a81ccc00`, the window since v0.23.1 contains **7,918 non-merge commits** across **5,211 changed files** (+239,733 / −22,788), **1,989 merged PRs** and **940 closed issues**.

Also in the window, undocumented here on purpose: durable subagents that survive a gateway restart or crash and can be continued on their own conversation, one prompt-cache clock per session, `hermes fallback check` for fallback-chain readiness, `hermes update --force` to stop gateways at once instead of draining, one-time browser_vault codes entered from Telegram and Discord, opt-in shared Telegram DM threads, the Gemini Interactions API by default for Gemini 3 and later plus Gemini 4 Carbon, fast mode for Claude Mythos 5.2, per-job cron options (`wrap_response`, a fresh thread per run), new plugin APIs (`ctx.fork_session`, `ctx.redact_text()`, `ctx.register_idle_task`), compatibility shims so updates work across module moves, a slimmer macOS bundle that installs Chromium on first use, and a large batch of new plugin-catalog entries.

**Full curated release notes for this window ship with v0.24.0**, which will document everything from v0.23.0 onward — highlights, feature areas, and complete contributor credits. Nothing in this window is skipped.

## Fixed in the release candidate

- Desktop chats created by an August build with a bare `custom` provider can send again after updating (#156545).
- A Desktop or TUI reply that streamed beside a todo or memory call now settles instead of leaving the Stop button up (#156553).
- A crash mid-stream on Telegram and other edit-streaming chats no longer shows a duplicate "Recovered reply"; a word holding a key prefix mid-word (`program_id`) is shown on time again (#156546).
- Desktop no longer loses or scrambles what you type while it starts and resumes your last chat (#156615, #156642).
- After a reconnect mid-reply, Desktop shows the reply once and in full, attachments included (#156611).
- In the Webapp, opening Hermes Cloud agents while this install isn't signed in to Nous Portal now tells you to sign in to Nous Portal instead of sending you to the Webapp login (#156652).
- Exiting the CLI while its startup update check is waiting on GitHub no longer leaves `git` running (#156616).

## Security

- Fixes [GHSA-p22p-9ph6-gmrh](https://github.com/NousResearch/hermes-agent/security/advisories/GHSA-p22p-9ph6-gmrh) (`CVE-2026-130164`, High): when Bot Desktop runs inside a `docker` or `ssh` terminal backend, its screen `env` file is now allowlisted and validated, and values from a backend-hosted screen are no longer merged into processes started on the agent machine (#154487).

## Updating

- Microsoft Store app: updates through the Store.
- Desktop app installed from the installer (.exe / .dmg): no change in this release; it updates with the next bundled release.
- CLI: `hermes update`, or re-run the installer one-liner.
- Docker / Hermes Cloud: `nousresearch/hermes-agent:stable` (or `:latest`).

**Full Changelog**: [v0.23.1...v0.23.2](https://github.com/NousResearch/hermes-agent/compare/v0.23.1...v0.23.2)</content>
    <ore:provenance>
      <ore:sourceId>hermes-agent-releases</ore:sourceId>
      <ore:sourceName>Hermes Agent GitHub Releases</ore:sourceName>
      <ore:sourceType>github_releases</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://github.com/NousResearch/hermes-agent/releases</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://api.github.com/repos/NousResearch/hermes-agent/releases</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://github.com/NousResearch/hermes-agent/releases/tag/v0.23.2</ore:originalUrl>
      <ore:upstreamId>RE_kwDOPRF1G84arFmQ</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hacker-news:6ed6674624f3954294fa9cde3fab47de</id>
    <title>I can’t believe it’s 1</title>
    <updated>2026-11-16T19:07:13Z</updated>
    <published>2026-11-16T19:07:13Z</published>
    <link rel="alternate" href="https://aperiodical.com/2026/11/i-cant-believe-its-1/" />
    <link rel="via" href="https://news.ycombinator.com/rss" />
    <category scheme="urn:ore-news:sources" term="hacker-news" label="Hacker News" />
    <author>
      <name>Hacker News</name>
    </author>
    <source>
      <id>urn:ore-news:source:hacker-news</id>
      <title>Hacker News</title>
      <link rel="alternate" href="https://news.ycombinator.com/" />
      <link rel="via" href="https://news.ycombinator.com/rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hacker-news</ore:sourceId>
      <ore:sourceName>Hacker News</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://news.ycombinator.com/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://news.ycombinator.com/rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://aperiodical.com/2026/11/i-cant-believe-its-1/</ore:originalUrl>
      <ore:upstreamId>https://aperiodical.com/2026/11/i-cant-believe-its-1/</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hermes-agent-releases:58d23fee736e6d9416c40fb75774205f</id>
    <title>Hermes Agent canary v0.23.1+canary.20261116T070005Z</title>
    <updated>2026-11-16T07:59:18Z</updated>
    <published>2026-11-16T07:59:18Z</published>
    <link rel="alternate" href="https://github.com/NousResearch/hermes-agent/releases/tag/v0.23.1%2Bcanary.20261116T070005Z" />
    <link rel="via" href="https://api.github.com/repos/NousResearch/hermes-agent/releases" />
    <category scheme="urn:ore-news:sources" term="hermes-agent-releases" label="Hermes Agent GitHub Releases" />
    <author>
      <name>Hermes Agent GitHub Releases</name>
    </author>
    <source>
      <id>urn:ore-news:source:hermes-agent-releases</id>
      <title>Hermes Agent GitHub Releases</title>
      <link rel="alternate" href="https://github.com/NousResearch/hermes-agent/releases" />
      <link rel="via" href="https://api.github.com/repos/NousResearch/hermes-agent/releases" />
    </source>
    <content type="text"># Hermes Agent v0.23.1+canary.20261116T070005Z (v0.23.1+canary.20261116T070005Z)

**Release Date:** November 16, 2026

&lt;!-- HERMES_BUILDS_TABLE --&gt;
## Downloads

### Hermes Desktop

| OS | Architecture | Download |
|---|---|---|
| macOS | Apple Silicon (M-series) | [DMG](https://hermes-assets.nousresearch.com/releases/tag/v0.23.1%2Bcanary.20261116T070005Z/HermesBundled-0.23.1%2Bcanary.20261116T070005Z-mac-arm64.dmg) |
| Windows | x86 (64-bit) | [MSIX](https://hermes-assets.nousresearch.com/releases/tag/v0.23.1%2Bcanary.20261116T070005Z/HermesBundled-0.23.1%2Bcanary.20261116T070005Z-win-x64.msix) |
| Windows | ARM (arm64 / aarch64) | [MSIX](https://hermes-assets.nousresearch.com/releases/tag/v0.23.1%2Bcanary.20261116T070005Z/HermesBundled-0.23.1%2Bcanary.20261116T070005Z-win-arm64.msix) |

### Native install/chat smoke

Download availability is independent of smoke status. Each result covers all native legs in that format group. Linux bundles are disabled; unsigned Store envelopes are not install-smoked. No-upload dry tags have no download handoff and are not smoke-qualified.

| Packages | Smoke status |
|---|---|
| macOS DMG + ZIP (arm64) | Passed |
| Windows MSIX (arm64) | Passed |
| Windows MSIX (x64) | Passed |
&lt;!-- /HERMES_BUILDS_TABLE --&gt;

## 🐛 Bug Fixes

- Code-health): packaged-imports models namespace packages; AGENTS.md names its exceptions ([`aa6d201d`](https://github.com/NousResearch/hermes-agent/commit/aa6d201dfdd530b4bcc4df377181b6e7170e17eb)) — @alt-glitch
- Agent): generic tool deadline no longer clips a tool's own timeout ([`e1ac37eb`](https://github.com/NousResearch/hermes-agent/commit/e1ac37eba1fe4f36bf31d422c2884c895799a02c)) — @huanshan5195
- Redact): mask an .npmrc auth value that only starts with a ${VAR} reference ([`81fd6d89`](https://github.com/NousResearch/hermes-agent/commit/81fd6d89e57998dd8e76042e5e8357a60eed94bb)) — @c2h5oh
- Plugin-catalog): commonly-hermes-plugin re-pinned; its server asks before writes ([`467b8f7d`](https://github.com/NousResearch/hermes-agent/commit/467b8f7d1246536c55872d2318afe0f2b74d6959)) — @lilyshen0722
- Security): mask passwords in DB URL query strings ([`5b3168ea`](https://github.com/NousResearch/hermes-agent/commit/5b3168ea01c0155b474a8778d83e3205339d2a34)) — @thejesh23
- Approval): read git option substitutions nested up to four levels as one word ([`234bd742`](https://github.com/NousResearch/hermes-agent/commit/234bd742d26f5030b51ef87eff41a018e7f969d1)) — @c2h5oh

## 📦 Other Changes

- Review: trim deadline-floor tests to the two runner invariants; slim the registry guard ([`ec931428`](https://github.com/NousResearch/hermes-agent/commit/ec93142876e9c8a9413e7a3dbdcd5cc6caa70079))
- Port from lobehub/lobehub#20735: run in a usable directory when the terminal cwd is gone, and say so ([#20735](https://github.com/NousResearch/hermes-agent/pull/20735))

## 👥 Contributors

Thank you to everyone who contributed to this release!

- @BearHuddleston (81 commits)
- @unsupportedpastels (3 commits)
- @foma-agent (2 commits)
- @c2h5oh (2 commits)
- @alt-glitch (1 commit)
- @liuhao1024 (1 commit)
- @huanshan5195 (1 commit)
- @Sora-bluesky (1 commit)
- @nolanchic (1 commit)
- @Sahilvishnaliya (1 commit)
- @lilyshen0722 (1 commit)
- @thejesh23 (1 commit)
- @kouyichi (1 commit)
- @djagya (1 commit)

**Full Changelog**: [v0.23.1+canary.20261115T064406Z...v0.23.1+canary.20261116T070005Z](https://github.com/NousResearch/hermes-agent/compare/v0.23.1+canary.20261115T064406Z...v0.23.1+canary.20261116T070005Z)</content>
    <ore:provenance>
      <ore:sourceId>hermes-agent-releases</ore:sourceId>
      <ore:sourceName>Hermes Agent GitHub Releases</ore:sourceName>
      <ore:sourceType>github_releases</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://github.com/NousResearch/hermes-agent/releases</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://api.github.com/repos/NousResearch/hermes-agent/releases</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://github.com/NousResearch/hermes-agent/releases/tag/v0.23.1%2Bcanary.20261116T070005Z</ore:originalUrl>
      <ore:upstreamId>RE_kwDOPRF1G84aoBx-</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hermes-agent-releases:8589f00d855791b41b02eb19820e90b1</id>
    <title>Hermes Agent canary v0.23.1+canary.20261115T064406Z</title>
    <updated>2026-11-15T07:52:37Z</updated>
    <published>2026-11-15T07:52:37Z</published>
    <link rel="alternate" href="https://github.com/NousResearch/hermes-agent/releases/tag/v0.23.1%2Bcanary.20261115T064406Z" />
    <link rel="via" href="https://api.github.com/repos/NousResearch/hermes-agent/releases" />
    <category scheme="urn:ore-news:sources" term="hermes-agent-releases" label="Hermes Agent GitHub Releases" />
    <author>
      <name>Hermes Agent GitHub Releases</name>
    </author>
    <source>
      <id>urn:ore-news:source:hermes-agent-releases</id>
      <title>Hermes Agent GitHub Releases</title>
      <link rel="alternate" href="https://github.com/NousResearch/hermes-agent/releases" />
      <link rel="via" href="https://api.github.com/repos/NousResearch/hermes-agent/releases" />
    </source>
    <content type="text"># Hermes Agent v0.23.1+canary.20261115T064406Z (v0.23.1+canary.20261115T064406Z)

**Release Date:** November 15, 2026

&lt;!-- HERMES_BUILDS_TABLE --&gt;
## Downloads

### Hermes Desktop

| OS | Architecture | Download |
|---|---|---|
| macOS | Apple Silicon (M-series) | [DMG](https://hermes-assets.nousresearch.com/releases/tag/v0.23.1%2Bcanary.20261115T064406Z/HermesBundled-0.23.1%2Bcanary.20261115T064406Z-mac-arm64.dmg) |
| Windows | x86 (64-bit) | [MSIX](https://hermes-assets.nousresearch.com/releases/tag/v0.23.1%2Bcanary.20261115T064406Z/HermesBundled-0.23.1%2Bcanary.20261115T064406Z-win-x64.msix) |
| Windows | ARM (arm64 / aarch64) | [MSIX](https://hermes-assets.nousresearch.com/releases/tag/v0.23.1%2Bcanary.20261115T064406Z/HermesBundled-0.23.1%2Bcanary.20261115T064406Z-win-arm64.msix) |

### Native install/chat smoke

Download availability is independent of smoke status. Each result covers all native legs in that format group. Linux bundles are disabled; unsigned Store envelopes are not install-smoked. No-upload dry tags have no download handoff and are not smoke-qualified.

| Packages | Smoke status |
|---|---|
| macOS DMG + ZIP (arm64) | Passed |
| Windows MSIX (arm64) | Passed |
| Windows MSIX (x64) | Passed |
&lt;!-- /HERMES_BUILDS_TABLE --&gt;

## ✨ Features

- Plugin "dosbox-mcp" ([`4c02a304`](https://github.com/NousResearch/hermes-agent/commit/4c02a30498d5f458e2da2276f978e436fb9c51fc)) — @shakeyourbunny
- Hermes-eye-memory to the plugin catalog ([`e71d2da7`](https://github.com/NousResearch/hermes-agent/commit/e71d2da7928fcf976f076715230356f6fa5b13ac)) — @isthatananya
- Plugin-catalog): add permission-tiers (f5f6183) ([`c2779be8`](https://github.com/NousResearch/hermes-agent/commit/c2779be89a3293075a3e892b7f8f2817c1797e02)) — @imperator-clawdius
- Plugin-catalog): add neuralwatt-provider ([`5dcd3b55`](https://github.com/NousResearch/hermes-agent/commit/5dcd3b55983654ccc552a977a2cd20ee50dfddeb)) — @ptaranat
- QMD Workspaces to plugin catalog ([`09adb261`](https://github.com/NousResearch/hermes-agent/commit/09adb261c2fefba343ca922573efe0049d39816e)) — @lad75020
- Catalog): add Asset Curator ([`36890962`](https://github.com/NousResearch/hermes-agent/commit/36890962216343833dd6deef29446de58f59b3d3)) — @dev-willbird1936
- Catalog: add video-xray (video analysis workbench) ([`57c44c75`](https://github.com/NousResearch/hermes-agent/commit/57c44c757472e65d8a4ba7b33fb7661e62ef9e5c)) — @LuuMoss
- Plugin-catalog): bump ascii-worlds to 1.4.0 (pipes and thirteen character habitats) ([`56a81b86`](https://github.com/NousResearch/hermes-agent/commit/56a81b861f7eb57136d2a99b18f1944ae0ca5027)) — @dudicslevente
- Catalog): update vibe-relay to 0.4.0 ([`8f0e84b1`](https://github.com/NousResearch/hermes-agent/commit/8f0e84b1dcb49c8981c54f0d363f1c578b5e668d)) — @trenthalden
- Plugin-catalog): progression 1.2.0 (flag a chat or subagent waiting for input) ([`9f75669b`](https://github.com/NousResearch/hermes-agent/commit/9f75669bb5315ee8c7c418bf9df1d9df0e610dc5)) — @agent-local
- Plugin-catalog): add progression 1.1.0 ([`aa952a4b`](https://github.com/NousResearch/hermes-agent/commit/aa952a4bf7a2199b89b01de34af82795b2cb4309)) — @agent-local
- Plugin-catalog: add munito-provider ([`fe7be3f9`](https://github.com/NousResearch/hermes-agent/commit/fe7be3f923ed71e4880879411d21dbc7115b718b)) — @alexeyeryshev
- Catalog): add datacircle ([`abb7a08b`](https://github.com/NousResearch/hermes-agent/commit/abb7a08bb467bde085549d69678d6891c922bec0)) — @waynehamadi
- Plugin-catalog): update inkly description and pin ([`16d4c88d`](https://github.com/NousResearch/hermes-agent/commit/16d4c88def8055b206b62702e2e7e995f1eea97e)) — @jeevships
- Plugin-catalog): add inkly ([`42158087`](https://github.com/NousResearch/hermes-agent/commit/421580879938128cd5ee90adc1defd97934936f8)) — @jeevships
- Plugin-catalog: add luminary (self-hosted memory provider) ([`1f4a6b50`](https://github.com/NousResearch/hermes-agent/commit/1f4a6b50354fd0d26e534a4f7437ba09c01fbb2e)) — @alertxsto
- Plugin-catalog): add locksift ([`bc7e3a1b`](https://github.com/NousResearch/hermes-agent/commit/bc7e3a1b06fd908dcc73532b6a590a1687e117c1)) — @rodricksz4h5
- Plugin-catalog): add hermes-slots ([`2efda391`](https://github.com/NousResearch/hermes-agent/commit/2efda3919708bdc18bcd4e67f4d8e19cdca78254)) — @tuancookiez-hub
- Plugin-catalog): add plansift ([`93df87ca`](https://github.com/NousResearch/hermes-agent/commit/93df87ca69425fe2a7ef8f8f66e6b246de2a6cb6)) — @rodricksz4h5
- Plugin-catalog): bump valun to 0.6.2 (hermes valun profile: public vouches) ([`6f94da3d`](https://github.com/NousResearch/hermes-agent/commit/6f94da3dd7e0fc8c484d2c534b84bd84ade64aac)) — @fitzss
- Plugin-catalog: add softhalo-usage ([`a90850b7`](https://github.com/NousResearch/hermes-agent/commit/a90850b705f51dc92d6666c008eaf2345c365591)) — @ahujat
- Plugin-catalog): add Apple Health Data adapter ([`5703eed4`](https://github.com/NousResearch/hermes-agent/commit/5703eed4083c970355fa0af61f50aaba9c6cf86e)) — @krumjahn
- Slaide to plugin catalog ([`7ad17bd7`](https://github.com/NousResearch/hermes-agent/commit/7ad17bd71de0e5db23e91c4af89366bea1087ca8)) — @Lugier
- Plugin-catalog): update data to 0.1.8 ([`6b4be069`](https://github.com/NousResearch/hermes-agent/commit/6b4be0692419b96579c88db30b55875811e663a1)) — @Adolanium
- Plugin-catalog): add us-filings ([`66cefccf`](https://github.com/NousResearch/hermes-agent/commit/66cefccf1de57a9c45cb614a9fa12e452a23786a)) — @TakeshiTGAL
- Plugin-catalog): bump modelscout to 0.3.11 ([`61fadb96`](https://github.com/NousResearch/hermes-agent/commit/61fadb967156edbd431c6e501592c465c0a17108)) — @iknowterry
- Hermes-hostd plugin configuration ([`0e62767c`](https://github.com/NousResearch/hermes-agent/commit/0e62767cf88fbdbb16bb00a05d0b89cb237514aa)) — @violetSoftware
- Hive.yaml plugin configuration file ([`a636863f`](https://github.com/NousResearch/hermes-agent/commit/a636863fe989aa7c77e413de0b611e05030309ee)) — @MFaiqKhan
- Plugin-catalog: add own-compute (Plugin Hackathon entry) ([`686949c4`](https://github.com/NousResearch/hermes-agent/commit/686949c4956e7defaeadcba5d07e41d1dd107730)) — @Siioh
- Plugin-catalog: add verifiable-math-kernel (v1.0.2) ([`016a5999`](https://github.com/NousResearch/hermes-agent/commit/016a59990c53bb6a346d906671c115a5d75f1aa7)) — @pCwOrM
- Catalog): add Meridian plugin ([`4e40848e`](https://github.com/NousResearch/hermes-agent/commit/4e40848e5f0971f8af1c1af52e9fdf8f5b8a8125)) — @unifyWeb3
- Plugin-catalog: add code-assurance-engine v0.1.0 (pin 0a502a3) ([`66caf62b`](https://github.com/NousResearch/hermes-agent/commit/66caf62b7c68aebc8952dff0266a7df7f450a88d)) — @Sahil-SS9
- PrintWatch 0.4.0: add Bambu Lab adapter (new SHA pin) ([`226d4994`](https://github.com/NousResearch/hermes-agent/commit/226d499453cd977c0328a6784e389a42194dae9d)) — @clawsyndicate
- PrintWatch to the plugin catalog ([`a57a1154`](https://github.com/NousResearch/hermes-agent/commit/a57a1154e4d8400deb920b10a244092b041a12a6)) — @clawsyndicate
- Catalog): update cardworthscanner catalog to standard format and pin b45c23ed10e2f96b37c3029353bc72929fe6e91b ([`d9d6f8e5`](https://github.com/NousResearch/hermes-agent/commit/d9d6f8e5a764e34ffb034430adbd0dde6a84eaaa)) — @AbigailDavised
- Catalog): add cardworthscanner tcg pricing and psa grading roi plugin ([`115df299`](https://github.com/NousResearch/hermes-agent/commit/115df2992bddd083a1d26f81f0386f29b36d8554)) — @AbigailDavised
- Catalog): pin taofind to c4b6551382f4ceed5cecea6b1219d86153f86615 ([`dff46735`](https://github.com/NousResearch/hermes-agent/commit/dff46735e3560be1a7f06eca3e2c87b83f60ee7f)) — @AbigailDavised
- Add taofind to plugin-catalog ([`4c036e27`](https://github.com/NousResearch/hermes-agent/commit/4c036e27e994cc0ba25ce630e7889350c99abd8c)) — @AbigailDavised
- Catalog): pin chinamedvisit to 95ac3a638798a9ff02447478128dfbf9311990ab ([`8e7a0505`](https://github.com/NousResearch/hermes-agent/commit/8e7a0505415884bdecd0db6b866279a58cc3d444)) — @AbigailDavised
- Add chinamedvisit to plugin-catalog ([`59d6fe1e`](https://github.com/NousResearch/hermes-agent/commit/59d6fe1e199054aac14ac2b4085997888dbb0686)) — @AbigailDavised
- Plugin-catalog): add train-ultra plugin ([`5191eb36`](https://github.com/NousResearch/hermes-agent/commit/5191eb363a228a5c11a3db989a7baa5a1f440ff5)) — @wadewegner
- Plugin-catalog): add resortlife ([`dde8b4f4`](https://github.com/NousResearch/hermes-agent/commit/dde8b4f471c8595ab346974e12e7f51a03310a9f)) — @raidwaleed
- Plugin-catalog: add year-wrapped ([`cca65e14`](https://github.com/NousResearch/hermes-agent/commit/cca65e1443a6479524d8839599e05d72635eb9f8)) — @MadeByBrain
- Catalog): add screenshot and update look-at-this pin ([`4554c6f7`](https://github.com/NousResearch/hermes-agent/commit/4554c6f7402c2c015ad4c6a341680b4c6176cc44)) — @Elshayib
- Catalog: add look-at-this v0.2.1 ([`40be9e57`](https://github.com/NousResearch/hermes-agent/commit/40be9e5792ca285c82f0863d7df6d7f80c0f30b1)) — @Elshayib
- Plugin-catalog): update super-agent to 0.2.2 ([`8fbbf0d4`](https://github.com/NousResearch/hermes-agent/commit/8fbbf0d4e0ff9242389f7cbeecfadc960be3e990)) — @JerryLiu369
- Plugin-catalog): bump stoa to 0.18.0 ([`1c79d269`](https://github.com/NousResearch/hermes-agent/commit/1c79d269838235f881083f7193e8bd9d9f8c11a1)) — @jarrett-del
- Plugin-catalog): bump stoa to 0.16.0 ([`9b2b9ec8`](https://github.com/NousResearch/hermes-agent/commit/9b2b9ec82bdd05ea2be33a5dad3f725fb068b62f)) — @jarrett-del
- Plugin-catalog: pin hermes-action-bar to c848d74 (new settings screenshot) ([`3fb1b707`](https://github.com/NousResearch/hermes-agent/commit/3fb1b7078aa924ae155ecdd9710ff74dde33d8c5)) — @fquresh
- Catalog: add a cover image for vibeleak-atlas ([`549b5db0`](https://github.com/NousResearch/hermes-agent/commit/549b5db0910d1f581fdcfe4ee3141598b957f591)) — @abundantbeing
- Catalog: add a cover image for trophy-room ([`91980996`](https://github.com/NousResearch/hermes-agent/commit/919809968f1a945405b667ca31fae73c97f32606)) — @abundantbeing
- Catalog: add a cover image for cadence ([`93218a5a`](https://github.com/NousResearch/hermes-agent/commit/93218a5a90c18eb6f72e54bee6fe9587eca290ae)) — @abundantbeing
- Plugin-catalog): Update Sigrex plugin version and SHA ([`f9a1b318`](https://github.com/NousResearch/hermes-agent/commit/f9a1b318a0652c9d9a4d6b0696ec1e37afa6a514)) — @0x7s0lt1
- Plugin-catalog): add eol plugin ([`12982f1c`](https://github.com/NousResearch/hermes-agent/commit/12982f1cf3884604c8a585ad3d7c4e04669853e4)) — @adriens
- Plugin-catalog): add aeorank plugin ([`e65dfde8`](https://github.com/NousResearch/hermes-agent/commit/e65dfde870bb6d21a174e533c6e76a70e9381925)) — @aizaloapp
- Catalog): pin esimtao to 8db598c8c2b163511aa97a89ab8196aa3faef12d ([`336cb40c`](https://github.com/NousResearch/hermes-agent/commit/336cb40c46b2c1459c5db90eafda761be80593f4)) — @AbigailDavised
- Add esimtao to plugin-catalog ([`d502ac23`](https://github.com/NousResearch/hermes-agent/commit/d502ac230135e81662f91cbba09df22867cce9d8)) — @AbigailDavised
- Catalog): add hermes-janus temporal state engine ([`07b225f2`](https://github.com/NousResearch/hermes-agent/commit/07b225f2647d9c0bb128512f53d04e37c946bfa3)) — @Yonathan-T
- Plugin-catalog): add blindoracle plugin ([`02dceae3`](https://github.com/NousResearch/hermes-agent/commit/02dceae39aa86dff9e75bdff1c3705c5f1193666)) — @craigmbrown
- Plugin-catalog): add ai-visibility-geo-audit plugin ([`7be41c5d`](https://github.com/NousResearch/hermes-agent/commit/7be41c5d4850d5dc0fa810829433df48243dc208)) — @afzalbuilds
- Plugin-catalog): bump model-explainer to 0.5.0 ([`f1c5483f`](https://github.com/NousResearch/hermes-agent/commit/f1c5483f796cc83ab66699dc61fe5c8865328917)) — @tuancookiez-hub
- Plugin-catalog): add mesh-check ([`4e66d6b8`](https://github.com/NousResearch/hermes-agent/commit/4e66d6b8aebd689fce6c32a19e9d8b2d1dab2bad)) — @TakeshiTGAL
- Catalog: add inbox-sentinel logo image (pinned to repo SHA) ([`c2b2c6a4`](https://github.com/NousResearch/hermes-agent/commit/c2b2c6a4ec1036e56a43c070f5d5196018d47eff)) — @eddwithers
- Plugin-catalog): re-list atmorouter from its new repository ([`1d3c0c66`](https://github.com/NousResearch/hermes-agent/commit/1d3c0c6655f379af7b4def805d9740eb55fb5f5b)) — @BeckleyTenriajeng
- Token-speed to the plugin catalog ([`07e29c53`](https://github.com/NousResearch/hermes-agent/commit/07e29c539cdcaa9971804263bc3cd54883656f12)) — @shengqiqwq-spec
- Plugin-catalog): add bae ([`7875c846`](https://github.com/NousResearch/hermes-agent/commit/7875c846ad535d2d9c559abb200126bbf8d44362)) — @jarrett-del
- Hermes Reading plugin to catalog ([`94aa7970`](https://github.com/NousResearch/hermes-agent/commit/94aa7970a491c4ec8f43a61dd7db7e5d6b410428)) — @forgoneops
- Plugin-catalog): re-pin Finder after scope filters ([`ceae5809`](https://github.com/NousResearch/hermes-agent/commit/ceae580999e0a06901b70445bae2592c020d3580)) — @oways
- Plugin-catalog): pin chineseworksheet to d38ce03ab34acbe50724f011c7fa8c635db462a2 ([`2728e48a`](https://github.com/NousResearch/hermes-agent/commit/2728e48abbf2d33ab377153a03c30ecf289cef7e)) — @AbigailDavised
- Plugin-catalog): add chineseworksheet plugin ([`72a474b1`](https://github.com/NousResearch/hermes-agent/commit/72a474b10aecc0bb0d681d7e541877189c10ce45)) — @AbigailDavised
- Approved vividsites marketplace banner ([`d63ad0c9`](https://github.com/NousResearch/hermes-agent/commit/d63ad0c99c9262d2e5d165d369bb4c147fc6fb6d)) — @krumjahn
- VividSites free-component plugin catalog entry ([`465f2bf2`](https://github.com/NousResearch/hermes-agent/commit/465f2bf28072b351911680cf529729a95ae3ee03)) — @krumjahn
- CrowdCode plugin to the catalog ([`83aa743d`](https://github.com/NousResearch/hermes-agent/commit/83aa743d7a7fd50629ef3bff37230885b30b9538)) — @sr33j
- Plugin-catalog): re-pin wiretap to its hook-only build (0.7.0) ([`2edb9046`](https://github.com/NousResearch/hermes-agent/commit/2edb9046c2690a30d0e89b579a2131a09d806e0b)) — @aka-lacie
- Catalog: add Living Spaces ([`7606086e`](https://github.com/NousResearch/hermes-agent/commit/7606086e546cde1df4d6919f30dc2fc635a27fcb)) — @akinduroifedayo
- Plugin-catalog: add its-in-your-head entry (v0.1.24 @ e53f8e251b) ([`87be1118`](https://github.com/NousResearch/hermes-agent/commit/87be1118eb06fb603fd4e4e119acb628b3e05954)) — @hi4c0ck
- Catalog: add vitam (PS Vita voice/camera handheld bridge) ([`70c5e8c4`](https://github.com/NousResearch/hermes-agent/commit/70c5e8c468d926be57c1894af1a5166056389253)) — @taylorwtf
- Plugin-catalog: add rh-preflight ([`1fb9ae82`](https://github.com/NousResearch/hermes-agent/commit/1fb9ae828bd6d320077318c68bd3c5f932e0fb30)) — @quotumorg
- Plugin-catalog): add zerofactory plugin ([`10dc547b`](https://github.com/NousResearch/hermes-agent/commit/10dc547b750a2066e6480cbcaef0fe1e0d994aa4)) — @ntsd
- Rea-video-hermes plugin (shot-by-shot video reverse-engineering) ([`3ae9d585`](https://github.com/NousResearch/hermes-agent/commit/3ae9d58598bef34dabbc3826b26e09517403be3a)) — @wusanjay
- Plugin-catalog): add worktable plugin ([`f160801c`](https://github.com/NousResearch/hermes-agent/commit/f160801c115a62ec6de4340c39e2a76eff2a1c24)) — @obkaro
- Catalog): add standalone Hermes Teleoperator v1.1.2 ([`c13ddc20`](https://github.com/NousResearch/hermes-agent/commit/c13ddc20ceb9a38837d79ff75dc4eb0fe3d32c23)) — @Tsurgcom
- Catalog): add AutoRAG local document and archive search ([`788d52bb`](https://github.com/NousResearch/hermes-agent/commit/788d52bbfe49eb6783f22802c78792fbef36a647)) — @vkehfdl1
- Gateway): per-profile and profile-management tickets in `gateway tickets` ([`0ca6a150`](https://github.com/NousResearch/hermes-agent/commit/0ca6a15001d2077543dcffda1a8296f037432017)) — @unsupportedpastels

## 🔧 Improvements

- Dosbox-mcp to 0.2.4 ([`bfb9cba1`](https://github.com/NousResearch/hermes-agent/commit/bfb9cba15b7be15995f0840dbacfb682a74d62bc)) — @shakeyourbunny
- Dosbox-mcp to 0.2.3 ([`dff513a8`](https://github.com/NousResearch/hermes-agent/commit/dff513a89a7abc5ed1fe6362bdebb4abc04881f6)) — @shakeyourbunny
- Unblockbruecke.yaml ([`d902c7e8`](https://github.com/NousResearch/hermes-agent/commit/d902c7e862c0cd061eb2624d1ee9db1f2baf735f)) — @studioluftbruecke
- Plugin-catalog: update detonator to v0.3.0 ([`7e38351d`](https://github.com/NousResearch/hermes-agent/commit/7e38351df5540d33b75e83b321989465add50a3c)) — @shreyasudupi
- Eselsbruecke.yaml ([`3f0693a0`](https://github.com/NousResearch/hermes-agent/commit/3f0693a0c16fe99519d7a8ae09d99a90eac93451)) — @studioluftbruecke
- Catalog: update OwnMachine to v1.0.1 with selected promotional gallery ([`0d9c7703`](https://github.com/NousResearch/hermes-agent/commit/0d9c77039167a1993462d8a20f003eacd11ddcbc)) — @rbur0425
- Sentinel Governance catalog pin to v0.6.0 and disclose history replay ([`10d78642`](https://github.com/NousResearch/hermes-agent/commit/10d7864260e766186a234386af35cbe41bbe3b14)) — @ChasClogston
- Forgebruecke.yaml ([`096391ac`](https://github.com/NousResearch/hermes-agent/commit/096391ac5443f2c9fe4fa881c992787a9a3baec5)) — @studioluftbruecke
- Coolifybruecke.yaml ([`e94c7e6c`](https://github.com/NousResearch/hermes-agent/commit/e94c7e6cd15a352b270ca06eb67d8e7f1722548d)) — @studioluftbruecke
- Hive.yaml ([`6d026aa5`](https://github.com/NousResearch/hermes-agent/commit/6d026aa5b0c03402f3b767c4ca4a9447e511a520)) — @MFaiqKhan
- SHA for hive plugin in YAML file ([`0b3deba4`](https://github.com/NousResearch/hermes-agent/commit/0b3deba4c26cff054dae2876c284a4f377d68046)) — @MFaiqKhan
- SHA for hive plugin in catalog ([`98c1e5c3`](https://github.com/NousResearch/hermes-agent/commit/98c1e5c3cfa096e91a8565d2e5e60185ba75d2f8)) — @MFaiqKhan
- Hive.yaml ([`b9dc47f4`](https://github.com/NousResearch/hermes-agent/commit/b9dc47f42fb3aa805f2b2cdf0e5252b1951f07b1)) — @MFaiqKhan
- Catalog(verifiable-math-kernel): update pin to v1.0.5 (0afbb42fa2631b0c9995695125809b91ba36d480) ([`55eb11aa`](https://github.com/NousResearch/hermes-agent/commit/55eb11aac9be3bf0579f48ccd4c1e2574ae8128a)) — @pCwOrM
- Catalog(verifiable-math-kernel): update pin to v1.0.4 (7a85930fa6696375a53624254d549ada582ee0d2) ([`bbb934a2`](https://github.com/NousResearch/hermes-agent/commit/bbb934a2fed9372c79618ef102c77cf88a3eac26)) — @pCwOrM
- Catalog(verifiable-math-kernel): update pin to v1.0.3 (a5a16ec) ([`37c68a8e`](https://github.com/NousResearch/hermes-agent/commit/37c68a8edb1280286a2dfad39ddc40a8197de8c2)) — @pCwOrM
- Yandex plugin pins for marketplace README fixes ([`8452e148`](https://github.com/NousResearch/hermes-agent/commit/8452e14878af09c0cedb3866f2af5fe903ead480)) — @akinfold
- OpenAny: B2A (business to agent) marketplace copy and root endpoint ([`27843560`](https://github.com/NousResearch/hermes-agent/commit/27843560ae1513c3cf7b9707e10e678e7b6a73ce)) — @ComunionIO
- Plugin-catalog: update hermes-action-bar to 41bf242 (0.2.0) ([`08036552`](https://github.com/NousResearch/hermes-agent/commit/080365525bb8c55fe706540b325e56a55e50c957)) — @fquresh
- Plugin-catalog: update lusor tool disclosure and pin ([`81ceed64`](https://github.com/NousResearch/hermes-agent/commit/81ceed6465c2b3615e25a282aabbbf7a8718a61b)) — @illusivejosiah
- Rails catalog submission to 0.4.2 detection fixes (AI-assisted) ([`3ba0fa6f`](https://github.com/NousResearch/hermes-agent/commit/3ba0fa6f4412c4c6b2cdf0fc327ac2d25ae80afc)) — @grimmjoww578
- Hermes Reading to 0.1.1 ([`9db8bcff`](https://github.com/NousResearch/hermes-agent/commit/9db8bcffa069b59ec26f7af47ce24c403bba4dfc)) — @forgoneops
- Hermes Reading plugin pin ([`a9d70c77`](https://github.com/NousResearch/hermes-agent/commit/a9d70c778822e3f7df117f5dff1a30d81e8b76d7)) — @forgoneops
- VividSites entry to combined free and optional paid plugin ([`73191dba`](https://github.com/NousResearch/hermes-agent/commit/73191dba4be0f13bf29086d438a381421fc55d16)) — @krumjahn
- Cli): move config value redaction into config_secret_display ([`142f68f7`](https://github.com/NousResearch/hermes-agent/commit/142f68f7d0dd27c23f3abc0c214647a090d6fcda)) — @KrasimirKralev

## 🐛 Bug Fixes

- Plugins): a docstring critical stops at caution; header and re-encoded lines stay code ([`d1b46d71`](https://github.com/NousResearch/hermes-agent/commit/d1b46d718ffe675427928eff7e5fff69bcb4519b))
- Gateway,desktop): name the primary only when the fallback was refused, and keep the prompt out of a selection ([`296d8388`](https://github.com/NousResearch/hermes-agent/commit/296d83885fdcf063bb614b76b1a53c2626e4733b)) — @yoniebans
- Gateway): a failed turn after a lapsed primary login names the primary on its error card ([`fecec6b4`](https://github.com/NousResearch/hermes-agent/commit/fecec6b48507a9ac53f530505463913cbd61464c)) — @yoniebans
- Cli): show a runnable re-login for external CLI plugins without an auth handler ([`ae363cd5`](https://github.com/NousResearch/hermes-agent/commit/ae363cd53f462b8513dd27f0375819920c2f3bdc)) — @yoniebans
- Desktop): keep the external sign-in command inside its card and selectable ([`08af1809`](https://github.com/NousResearch/hermes-agent/commit/08af1809f53d3d574cb780776d635c6607024349)) — @yoniebans
- Fallback): surface the primary provider's expired login when the backup fails ([`2baaeeba`](https://github.com/NousResearch/hermes-agent/commit/2baaeeba9d6375ed5a63ad82cb04287409cf06be)) — @aantix
- Context): surface SSRF and secret-URL refusals in @url references ([`ed1f43c1`](https://github.com/NousResearch/hermes-agent/commit/ed1f43c1f3177177f0c25fecfed9e0f87ae6a478)) — @c2h5oh
- Video-xray: fix screenshot URLs to real files at v0.2.2 ([`e91d8822`](https://github.com/NousResearch/hermes-agent/commit/e91d8822bcd10948a90c0938f0b68da17879fb01)) — @LuuMoss
- Pin profile-local hostd transport configuration ([`085905dd`](https://github.com/NousResearch/hermes-agent/commit/085905ddbd6308451b2514cb4cf70cd6b3b6521b)) — @violetSoftware
- Pin hostd plugin with native approval hook ([`c9e86a6f`](https://github.com/NousResearch/hermes-agent/commit/c9e86a6fb2e88ea04ade77ea7af8cb73bf993ac4)) — @violetSoftware
- Plugin-catalog): re-pin agentline to 6eda871 (1.2.0) ([`9904d083`](https://github.com/NousResearch/hermes-agent/commit/9904d08333dc988b36f16ae135c2d48b7daabfdf)) — @prakhar-raj-031104
- Re-pin EarnFi catalog to 1.5.2 (3d595e9 listing fixes) ([`b5c2d8e8`](https://github.com/NousResearch/hermes-agent/commit/b5c2d8e8679c3cc20aeaf859bef50f280f2f9b6b)) — @earnfidotfun
- Re-pin EarnFi catalog sha to f8502f9 (1.5.1 HEAD) ([`683d510b`](https://github.com/NousResearch/hermes-agent/commit/683d510b22b13c6ed9abe59f29e7e29f66ac7f74)) — @earnfidotfun
- Re-pin EarnFi catalog to 1.5.1 (listing security follow-up) ([`1bf10663`](https://github.com/NousResearch/hermes-agent/commit/1bf10663cfc6121a7bac04eb626577ed71ad35c2)) — @earnfidotfun
- Re-pin EarnFi catalog to 1.5.0 (security review) ([`afc68d04`](https://github.com/NousResearch/hermes-agent/commit/afc68d04cd4284864336d8e274ccc6ac9e34a1ce)) — @earnfidotfun
- Re-pin EarnFi catalog to 1.4.9 (README fences) ([`83eeacad`](https://github.com/NousResearch/hermes-agent/commit/83eeacad80dc59248d7d40aab4b619122256eec7)) — @earnfidotfun
- Refresh EarnFi catalog banner pin (1.4.7) ([`e866b8a0`](https://github.com/NousResearch/hermes-agent/commit/e866b8a01e5e7509bae114d84904ba39b5702743)) — @earnfidotfun
- Reconcile EarnFi catalog credentials and banner pin ([`aec1e21c`](https://github.com/NousResearch/hermes-agent/commit/aec1e21cd5bd1fcdf4af916657d09a07b5503f38)) — @earnfidotfun
- Secrets): a plugin refresh keeps the launch scope's env and never crosses homes ([`e4888ba0`](https://github.com/NousResearch/hermes-agent/commit/e4888ba0ef4e80a68b84ac221d8102fca64d45a1)) — @c2h5oh
- Catalog): update hermes-janus pin to 1527210 ([`5742f91b`](https://github.com/NousResearch/hermes-agent/commit/5742f91b2f6c8c2e57bb90b7e3d8775d96e3e5e3)) — @Yonathan-T
- Plugin-catalog): re-pin blindoracle to aa1ca16d (review fixes) ([`282e44bc`](https://github.com/NousResearch/hermes-agent/commit/282e44bc5fb054bb7bcc99c6416eb0dda033b745)) — @craigmbrown
- Plugin-catalog): re-pin bae to f450d48 (sample-mode default, onboarding fixes) ([`be31b478`](https://github.com/NousResearch/hermes-agent/commit/be31b478175d94502f5bef8b3dd0554b1b723fd5)) — @jarrett-del
- Plugin-catalog): re-pin bae to 78d4dd9 and declare its pre_tool_call hook ([`0860a6b8`](https://github.com/NousResearch/hermes-agent/commit/0860a6b8fa1f966a94985ec12efb16d03934c53b)) — @jarrett-del
- Plugin-catalog): remove unsupported terminal action ([`1e67a4fb`](https://github.com/NousResearch/hermes-agent/commit/1e67a4fb777c4bb94454e84bcb6b10d31daac2af)) — @oways
- Plugins): pin rh-preflight to the secret scope fix ([`01759b64`](https://github.com/NousResearch/hermes-agent/commit/01759b642be08d45a4bb314d8798730424ab078e)) — @quotumorg
- Plugin-catalog): update zerofactory pinned SHA ([`3bbf0122`](https://github.com/NousResearch/hermes-agent/commit/3bbf0122952a4b26f4c70db449e458d4fe71de9b)) — @ntsd
- Pin: 8ef488f (portable manifest commit, validator green) ([`4207e583`](https://github.com/NousResearch/hermes-agent/commit/4207e5833461dd381feb0d976061bcd1a012091b)) — @wusanjay
- Declare mux_tracks in provides_tools (rule 6) ([`2a182815`](https://github.com/NousResearch/hermes-agent/commit/2a1828157db576b3ab8bd0651fb0b5d6e95a015d)) — @wusanjay
- Security): redact Discord bot tokens outside KEY=value shape ([`bfa85b3e`](https://github.com/NousResearch/hermes-agent/commit/bfa85b3e5f99fb3ad5135ee459dd7575caaeb239)) — @rodricksz4h5
- Approval): preserve assignment and conditional review input ([`4163c81e`](https://github.com/NousResearch/hermes-agent/commit/4163c81e7ebf4f41832c9467731dc171af68c4c8)) — @shoyann
- Approval): preserve extended glob review input ([`a25a479b`](https://github.com/NousResearch/hermes-agent/commit/a25a479bbd5485d41589c69e2659344e3bf68952)) — @shoyann
- Approval): preserve opaque expansions and escaped whitespace ([`ff9ab09c`](https://github.com/NousResearch/hermes-agent/commit/ff9ab09cea681e4086389676dc4462bebf9d22e0)) — @shoyann
- Approval): preserve arithmetic expansion review input ([`265fffb4`](https://github.com/NousResearch/hermes-agent/commit/265fffb45603f00b58f50fce6f21494f2fabe2b8)) — @shoyann
- Approval): isolate comments from heredoc and newline handling ([`b31d6f80`](https://github.com/NousResearch/hermes-agent/commit/b31d6f80b0acedff542b9bb5d845d0776aa04d24)) — @shoyann
- Approval): keep multi-line strings and heredocs intact in smart review ([`e15bf685`](https://github.com/NousResearch/hermes-agent/commit/e15bf685cd19ed9b37ec40eeb8ff48dc9f724117)) — @lolchocotaco
- Approval): preserve in-word hashes in smart review ([`db51a761`](https://github.com/NousResearch/hermes-agent/commit/db51a7610b1f64582fb364dad470a9f24e50679d)) — @shoyann
- Desktop): a messaging-chat paste over the save cap is dropped, not inlined ([`c7a6fa7a`](https://github.com/NousResearch/hermes-agent/commit/c7a6fa7a3d3fdc3652caf28fc945d7a1f5f702de)) — @helix4u
- Telegram): a comment absorbed by an inlined document survives the album's command caption ([`0896d4df`](https://github.com/NousResearch/hermes-agent/commit/0896d4df55bf901579a6957567a6e6c13595771d))
- Telegram): a comment and the video, voice or file sent right after it are one turn ([`f670c8b4`](https://github.com/NousResearch/hermes-agent/commit/f670c8b4a83e062080d280f500fda39296668f26))
- Gateway): a queued follow-up no longer skips the previous turn's post-delivery callback ([`c52207e3`](https://github.com/NousResearch/hermes-agent/commit/c52207e332d6de19cd32ed76f4e89f94e8bcff1a)) — @0xble
- Catalog: re-pin teleoperator to the review-fix commit ([`66d33b84`](https://github.com/NousResearch/hermes-agent/commit/66d33b84bc42a400eef3d61f7a76bef7581dc9b2)) — @Tsurgcom
- Gateway): a busy /moa keeps the stop epoch it arrived under ([`8090a9ef`](https://github.com/NousResearch/hermes-agent/commit/8090a9ef00d67e6809347a13ca9930a336c8743a))
- Cli): a failed requested profile override exits non-zero (#152716) ([#152716](https://github.com/NousResearch/hermes-agent/pull/152716)) — @phon-t
- Cron): scan heredoc bodies a command writes and then executes ([`ee63c993`](https://github.com/NousResearch/hermes-agent/commit/ee63c99341b5cac97d7295e6919ade11fe0d978c)) — @c2h5oh
- Gateway): point the Windows service-session warning at a normal desktop start ([`4bb75bae`](https://github.com/NousResearch/hermes-agent/commit/4bb75bae01cfb1d8502b7ea0b13ae1279a712b95)) — @unsupportedpastels
- Config): keep the Remote Config read base across the mask guard read ([`15aa3fa1`](https://github.com/NousResearch/hermes-agent/commit/15aa3fa13956f0ccbb496e770c1c7af6e90a2e6c)) — @c2h5oh
- Cli): restart waits re-send one frozen request and stop on Ctrl+C ([`daaafa9a`](https://github.com/NousResearch/hermes-agent/commit/daaafa9a66f79baea31c075965439429144893d4))
- Security): keep quotes inside connection-string passwords masked ([`5ea3a8af`](https://github.com/NousResearch/hermes-agent/commit/5ea3a8af0c7a45a55884a8ca74fbc5ef8265ccbc)) — @thejesh23
- Desktop): keep a large paste inline in a messaging-platform chat ([`1a5d7c08`](https://github.com/NousResearch/hermes-agent/commit/1a5d7c085cc9c04cbcdd7b9b16ef83e5e3f8c887)) — @helix4u
- Backup): recover owned ZIP and SQLite staging after interruption ([`389e34af`](https://github.com/NousResearch/hermes-agent/commit/389e34af9b5dab018222e356766bae648ce5539d)) — @helix4u
- Gateway): register the Windows task from its XML principal only ([`e60f483f`](https://github.com/NousResearch/hermes-agent/commit/e60f483f0a3c5efd2f2af2e9889b68a37cb9cc27)) — @c2h5oh
- Skills): keep plaintext secrets out of oss-forensics working files (#155378) ([#155378](https://github.com/NousResearch/hermes-agent/pull/155378)) — @c2h5oh
- Notifications): keep Clear all clearing bottom-right toasts ([`4122b05c`](https://github.com/NousResearch/hermes-agent/commit/4122b05c60f9b24c7eee48020544c28332898013)) — @kshitijk4poor
- Profiles): retire draft setup on rename instead of deleting the draft ([`8d4616a1`](https://github.com/NousResearch/hermes-agent/commit/8d4616a13e9d1c08134399301fd490987893d0bc)) — @kshitijk4poor
- Profiles): keep creation warnings visible across client lifecycles ([`de57009b`](https://github.com/NousResearch/hermes-agent/commit/de57009b02a57b531371d762d78857048b0684c5)) — @kshitijk4poor
- Debug): don't mask systemd unit instances as email addresses ([`e38f5c24`](https://github.com/NousResearch/hermes-agent/commit/e38f5c24576d8c2898bed91da5530cb526c5d65b)) — @c2h5oh
- Gateway): redact the systemctl status process tree ([`5662449a`](https://github.com/NousResearch/hermes-agent/commit/5662449a4c0a68dddf1da40e5eab43fa0b2d1a36)) — @lester076
- Memory): skip bare auto-loads and keep lookalike typed text ([`20efa1ec`](https://github.com/NousResearch/hermes-agent/commit/20efa1ec2c685725c7e09c78ae2c1cf88ff84fa7))
- Pm): carry skills and plugin/MCP catalogs into the snapshot too ([`6e3683a9`](https://github.com/NousResearch/hermes-agent/commit/6e3683a969fe5483544c2815295d1ff3c263e049))
- Telegram): only the card author is captured, whatever their reply points at ([`a40a854a`](https://github.com/NousResearch/hermes-agent/commit/a40a854abc40d9055581d66fac46c2c4fac3ebea))
- Security): bound per-entry inflated size when extracting marketplace theme vsix ([`301a509d`](https://github.com/NousResearch/hermes-agent/commit/301a509dfc3b906999bd95406ec22e1526d571ba)) — @briandevans

## 📚 Documentation

- Refresh EarnFi catalog details and pin (1.4.8) ([`6a37e158`](https://github.com/NousResearch/hermes-agent/commit/6a37e15836d2c717c165302b2225b1b3ae0c218e)) — @earnfidotfun
- Catalog): clarify HermesCRM listing copy ([`9578c774`](https://github.com/NousResearch/hermes-agent/commit/9578c774baac985dc93af5dfbada2eca3d11ceb9)) — @gptnius
- Catalog): add hermes-templates ([`a3d3b0be`](https://github.com/NousResearch/hermes-agent/commit/a3d3b0bea593258e81b2256284e1f18653a78a2c)) — @Ilyassbm
- Gateway): name the heartbeat and the session-namespace exceptions ([`1831ce1c`](https://github.com/NousResearch/hermes-agent/commit/1831ce1cfeb517a0b6008f006d09e2d0558439ac)) — @alt-glitch
- Signal): note why inline code is matched before enclosing pairs ([`64d66d89`](https://github.com/NousResearch/hermes-agent/commit/64d66d89851673ae2b8823342424f5d53f92c41e)) — @c2h5oh
- Cron): document the per-job wrap_response override ([`2eb00141`](https://github.com/NousResearch/hermes-agent/commit/2eb001413e21af5204ae7de3ef71d166848e651d)) — @iamfoz
- Skills): builtin scan trust also covers the official live-repo fallback ([`4b86af50`](https://github.com/NousResearch/hermes-agent/commit/4b86af50c09763250227b3613a2aa10b0987aefb)) — @c2h5oh

## 🧪 Tests

- Cli): the external sign-in card shows the plugin's own login command when it declares one (currently failing) ([`ff52795b`](https://github.com/NousResearch/hermes-agent/commit/ff52795b9f3573c0592e2175abb5bac60284a56d)) — @yoniebans
- Gateway): pin the primary card for auth_permanent and the fallback's retry time ([`2b250eeb`](https://github.com/NousResearch/hermes-agent/commit/2b250eebcb473148c09f5c8b37ac8ffd0c1534d4)) — @yoniebans
- Gateway): the primary's card on messaging turns, and no change without a lapsed primary ([`561501b7`](https://github.com/NousResearch/hermes-agent/commit/561501b7629259e9a8f5957dd8ced950a5aac45c)) — @yoniebans
- Plugins): compare the dropped-cookie warning's home as a home key ([`0be129d1`](https://github.com/NousResearch/hermes-agent/commit/0be129d1e7d2563a6ae34e26c17ec5a5df14cd84)) — @c2h5oh
- Threat_patterns): pin that chars past the scan cut are not reported ([`d310b0c1`](https://github.com/NousResearch/hermes-agent/commit/d310b0c116f0b7654812f73ec4dc4d0155104318)) — @c2h5oh
- Session-search): cover redaction of lower-ranked compact discovery results ([`343e648b`](https://github.com/NousResearch/hermes-agent/commit/343e648b3fe59f1d7122e8643d8a26853fcf680b)) — @c2h5oh
- Pm): every root data dir travels with the snapshot once ([`049dc4cd`](https://github.com/NousResearch/hermes-agent/commit/049dc4cd7fa3449c7e104d3ccfe4f0e4f7c5bc78))
- Cron): pin the exemption removal with expansion-based second destinations ([`0f05ab7f`](https://github.com/NousResearch/hermes-agent/commit/0f05ab7fc1308de34fb1ee63813e3e981129e025)) — @c2h5oh

## 🏗️ Infrastructure

- Contributors): map jim.jones1@gmail.com to aantix ([`e7479b65`](https://github.com/NousResearch/hermes-agent/commit/e7479b656fa23e7e582878e1caac052e1e883e93)) — @yoniebans
- Catalog): review disclosure for dosbox-mcp ([`7a725cfe`](https://github.com/NousResearch/hermes-agent/commit/7a725cfe7612e9dc6e3c098d7c1a9921d46d331a))
- Catalog): drop empty image/screenshots fields from hermes-eye-memory ([`952f7b68`](https://github.com/NousResearch/hermes-agent/commit/952f7b68486365360caff9f7c0156b013fcd029c))
- Plugin-catalog): bump circuit-bench to 0.1.1 ([`ed95cb6c`](https://github.com/NousResearch/hermes-agent/commit/ed95cb6c2e1b81e0bddebb41445666173bc9bd72)) — @juvenile454
- Catalog): livetalk requires_hermes &gt;=0.22.1 (prompt.receipt ships in v0.22.1) ([`be53dd38`](https://github.com/NousResearch/hermes-agent/commit/be53dd385b4ae8994cbdde9b35b55baa90b321cf))
- Map contributor email for lad75020 ([`5d616829`](https://github.com/NousResearch/hermes-agent/commit/5d6168293228e42f2f5299806f92d40279701cdc))
- Catalog): review disclosure for qmd-workspaces ([`ff194672`](https://github.com/NousResearch/hermes-agent/commit/ff194672a2ef6bd59a00a4c590cfcc3389eb2401))
- Catalog): bump Frihet to v0.2.2 ([`c6339f39`](https://github.com/NousResearch/hermes-agent/commit/c6339f39d743747cf099df168bf7fcf3631eeec4)) — @berthelius
- Map contributor email for dev-willbird1936 ([`788bda70`](https://github.com/NousResearch/hermes-agent/commit/788bda7028ccc4dc3242413cde9f32498891cc9f))
- Catalog): review disclosure for asset-curator ([`93adb3fe`](https://github.com/NousResearch/hermes-agent/commit/93adb3fea8042b44a2e1532129ef386294f00759))
- Map contributor email for LuuMoss ([`24c13ddb`](https://github.com/NousResearch/hermes-agent/commit/24c13ddb9fe5bf1ae3d58bc37f67ee1aa77741ef))
- Catalog): review disclosure for video-xray ([`375e34a0`](https://github.com/NousResearch/hermes-agent/commit/375e34a04531e0a187be975bb00622a0c4b2ccee))
- Catalog): review disclosure for detonator ([`fa745a48`](https://github.com/NousResearch/hermes-agent/commit/fa745a484a70ed862b0c127d4748bcafeda7450f))
- Catalog): bump hermes-stage to 0.66.8 ([`f344b15c`](https://github.com/NousResearch/hermes-agent/commit/f344b15c2fbca5630ed240785b46ecb3a3270802)) — @davidpgil
- Plugin-catalog): bump 3ds-platform to 0.2.1 ([`a350cb37`](https://github.com/NousResearch/hermes-agent/commit/a350cb37948d98282b938f9953eea18784d06ca6)) — @rndaom
- Plugin-catalog): bump pinned-folders to v0.1.14 ([`78b0862b`](https://github.com/NousResearch/hermes-agent/commit/78b0862b9583ad78b12305e122a48fd3427c1dc0)) — @jacobhausler
- Catalog): caduceus erase and sync wording ([`c9d2598d`](https://github.com/NousResearch/hermes-agent/commit/c9d2598d69b1423a80941527c8b09aeef3f812dd)) — @100yenadmin
- Catalog): bump caduceus to v0.3.0 ([`a3a35989`](https://github.com/NousResearch/hermes-agent/commit/a3a35989e957b012391102023e6115847a764c30)) — @100yenadmin
- Plugin-catalog): bump alice-voice to 0.3.2 at its renamed repository ([`edb2c13a`](https://github.com/NousResearch/hermes-agent/commit/edb2c13ac4bda366be1abae6ff5810785a4609a7)) — @bablobanov
- Map contributor email for supa-thibaud ([`7239ce3b`](https://github.com/NousResearch/hermes-agent/commit/7239ce3b9624504cf00465f7b583c0b9ffe2d073))
- Map contributor email for jeevships ([`813bd8d1`](https://github.com/NousResearch/hermes-agent/commit/813bd8d1bb25e82d19927682892f3495e0227256))
- Map contributor email for alertxsto ([`57dfc70e`](https://github.com/NousResearch/hermes-agent/commit/57dfc70ed42722e178ec928b5c7dd02429f83035))
- Catalog): review disclosure for luminary ([`865b3833`](https://github.com/NousResearch/hermes-agent/commit/865b3833bc92401593cc29fb3313987f89007753))
- Catalog): review disclosure for plan-mode ([`8e4df2c7`](https://github.com/NousResearch/hermes-agent/commit/8e4df2c7a66af99afdabbec4e9fd34fc42015d30))
- Catalog): review disclosure for deepseek-web-tools ([`1d6a00c9`](https://github.com/NousResearch/hermes-agent/commit/1d6a00c99c9812b9cd2ee42b9b5beec6ab6220c9))
- Catalog): review disclosure for theme-catalog ([`baedc023`](https://github.com/NousResearch/hermes-agent/commit/baedc023614196a2d9cccdbb55ffd6217d137fc7))
- Plugin-catalog): update incognito to v1.0.1 ([`0569c3b6`](https://github.com/NousResearch/hermes-agent/commit/0569c3b69963de452c7469ac7c40a79e896cd04a)) — @nicolasbuelvas
- Catalog): update genealogy recipes to v1.19.0 ([`48a6c9b0`](https://github.com/NousResearch/hermes-agent/commit/48a6c9b073812a2e767d7487dfe5129de96145aa)) — @lazyants
- Catalog): update genealogy recipes to v1.18.0 ([`63182a34`](https://github.com/NousResearch/hermes-agent/commit/63182a349a185b97d6e3548ca40d69126eef865c)) — @lazyants
- Catalog): review disclosure for softhalo-usage ([`9af8a7b8`](https://github.com/NousResearch/hermes-agent/commit/9af8a7b8e1e8c8a27867927758f6fff32a43e3b3))
- Plugin-catalog): update aamio to 0.7.46 ([`958a83c3`](https://github.com/NousResearch/hermes-agent/commit/958a83c3d7b595625b9dc3ebf357df38595f11e2)) — @aisenseapi
- Plugin-catalog): update aamio to 0.7.45 ([`d53c89ca`](https://github.com/NousResearch/hermes-agent/commit/d53c89ca2d8cf8820d12744b85f837b15a6843ed)) — @aisenseapi
- Plugin-catalog): update aamio to 0.7.44 ([`ee4f2c49`](https://github.com/NousResearch/hermes-agent/commit/ee4f2c4928ee470ce6ecbff6c417597e8ea13370)) — @aisenseapi
- Plugin-catalog): update aamio to 0.7.43 ([`c4053c96`](https://github.com/NousResearch/hermes-agent/commit/c4053c966727d5de4f7a56d93377799791fe5b87)) — @aisenseapi
- Plugin-catalog): bump yantrikdb to v0.28.0 ([`3f23f540`](https://github.com/NousResearch/hermes-agent/commit/3f23f540e3267bf0b377edaa3bbe4d269d841037)) — @spranab
- Catalog): review disclosure for modelscout ([`34eea162`](https://github.com/NousResearch/hermes-agent/commit/34eea162e741c2203f3c7306ad26a42c75d78db6))
- Catalog): review disclosure for forgebruecke ([`77bba032`](https://github.com/NousResearch/hermes-agent/commit/77bba03259ec18f756895c12605145d068661ea0))
- Catalog): review disclosure for coolifybruecke ([`7499cb1d`](https://github.com/NousResearch/hermes-agent/commit/7499cb1df88048ea85781179b4dcdb76bd2a692d))
- Map contributor email for violetSoftware ([`7cbc2927`](https://github.com/NousResearch/hermes-agent/commit/7cbc2927ca7381a9a9a0118fa64478907ea7b932))
- Catalog): review disclosure for hostd-client ([`965eff6f`](https://github.com/NousResearch/hermes-agent/commit/965eff6f2a60ecb5d14d75bb4bd752de375b761d))
- Map contributor email for jinsu133 ([`2d3af582`](https://github.com/NousResearch/hermes-agent/commit/2d3af5829ebfa439fb315bb74a1dcd917c6c3d79))
- Catalog): review disclosure for hermes-phone-control ([`9ed53ebe`](https://github.com/NousResearch/hermes-agent/commit/9ed53ebeb3f6ce605fc671072b2f63ce0e401df8))
- Map contributor email for Siioh ([`aa634f7f`](https://github.com/NousResearch/hermes-agent/commit/aa634f7f489270f8d695fcd983431a282784c2df))
- Map contributor email for prakhar-raj-031104 ([`58e98ce8`](https://github.com/NousResearch/hermes-agent/commit/58e98ce84961ab719b5300f2555a0cfa24922208))
- Catalog): review disclosure for earnfi ([`e95536e8`](https://github.com/NousResearch/hermes-agent/commit/e95536e82023ec9f92c551b3e5580f981a03b19d))
- Map contributor email for yogeshchoudhary555 ([`d25d00a8`](https://github.com/NousResearch/hermes-agent/commit/d25d00a8e32a821821fc1320a11cc98d86b88c35))
- Catalog): review disclosure for data-wrangler ([`f28ee0d4`](https://github.com/NousResearch/hermes-agent/commit/f28ee0d4203da73b9a16eb5b02c0c0e98f0b766b))
- Map contributor email for pCwOrM ([`b5333909`](https://github.com/NousResearch/hermes-agent/commit/b533390921b5496dc0a7d60276fe577bf3683584))
- Catalog): review disclosure for verifiable-math-kernel ([`cf8ef23a`](https://github.com/NousResearch/hermes-agent/commit/cf8ef23a0678152f6232e6269b5cfcf50477a05c))
- Map contributor email for unifyWeb3 ([`089a8289`](https://github.com/NousResearch/hermes-agent/commit/089a828900775dd771f2c6ba52035a4b5b808e18))
- Catalog): review disclosure for meridian ([`232f56e1`](https://github.com/NousResearch/hermes-agent/commit/232f56e18132617c38e68ebd8ce918bbba9af728))
- Catalog): re-pin meridian to e876f60 (v1.0.4) after symlink hardening ([`10119f0d`](https://github.com/NousResearch/hermes-agent/commit/10119f0d560d5942e154aa9a1e173dc3f6adad67)) — @unifyWeb3
- Catalog): re-pin meridian to 3587fd5 (demo docs update) ([`e0443179`](https://github.com/NousResearch/hermes-agent/commit/e0443179766348764256861d3b34f9ffaa2fc93b)) — @unifyWeb3
- Catalog): re-pin meridian to 6d2624c (README command fixes) ([`a5941b45`](https://github.com/NousResearch/hermes-agent/commit/a5941b45757f38109518a4a5ed0c47b244856eb2)) — @unifyWeb3
- Catalog): re-pin meridian to d83d218 (style pass) ([`9508327d`](https://github.com/NousResearch/hermes-agent/commit/9508327d8eaa757fc37e22f41112c03fd5781d11)) — @unifyWeb3
- Catalog): lede synced with manifest disclosure ([`f468a751`](https://github.com/NousResearch/hermes-agent/commit/f468a751ba0ebe78c3e662f2b5f01100b66958f6)) — @unifyWeb3
- Catalog): re-pin meridian to 6002020 (docs pass) ([`c9926369`](https://github.com/NousResearch/hermes-agent/commit/c9926369d825df27db51ea2011d046e2cba85c62)) — @unifyWeb3
- Catalog): re-pin meridian to 5b981ac (v1.0.2) after verification fixes ([`fe5f68b8`](https://github.com/NousResearch/hermes-agent/commit/fe5f68b82fbe489c0ff893105a1438bdc251d8fe)) — @unifyWeb3
- Catalog): re-pin meridian to 1a3c103 (v1.0.1) after review fixes ([`4fa2c18e`](https://github.com/NousResearch/hermes-agent/commit/4fa2c18e4a39b128d2fd04b6be189a24332c8d3f)) — @unifyWeb3
- Catalog): review disclosure for code-assurance-engine ([`2c9cfdbb`](https://github.com/NousResearch/hermes-agent/commit/2c9cfdbb846f2f223db7357590a0f96aa05f6bb2))
- Catalog): review disclosure for printwatch ([`9191e79b`](https://github.com/NousResearch/hermes-agent/commit/9191e79b50bfc2e9784beb69d0c7eca13ad3ffda))
- Map contributor email for samundra0 ([`ade10e23`](https://github.com/NousResearch/hermes-agent/commit/ade10e23fc159e1e9446d25066d5579370b50fb3))
- Catalog): review disclosure for visor ([`8ee25574`](https://github.com/NousResearch/hermes-agent/commit/8ee255742c9e9274d4d6515e38cc1ea5f3f8d327))
- Catalog): review disclosure for taofind ([`eb417a9c`](https://github.com/NousResearch/hermes-agent/commit/eb417a9c89eb60627f2d17a03945e0bebf812663))
- Catalog): review disclosure for chinamedvisit ([`5afbc7e3`](https://github.com/NousResearch/hermes-agent/commit/5afbc7e3f77f1d6412606e319cd6ac711abfdee0))
- Catalog): review disclosure for coach ([`2b254acc`](https://github.com/NousResearch/hermes-agent/commit/2b254accb735a08663b4c250719a3009ed2daa9c))
- Map contributor email for wadewegner ([`e258eebd`](https://github.com/NousResearch/hermes-agent/commit/e258eebddf640c368f9e9b239ced9ab084296358))
- Catalog): review disclosure for look-at-this ([`30f44c58`](https://github.com/NousResearch/hermes-agent/commit/30f44c58442af5cd01a891c3b712d11c253ca4f4))
- Map contributor email for InovArcAi ([`d123fe8b`](https://github.com/NousResearch/hermes-agent/commit/d123fe8bd31d3c676b5b3deab67de7a063868bcc))
- Catalog): repin qdrant-memory to Runtime 0.6.3 ([`2560f172`](https://github.com/NousResearch/hermes-agent/commit/2560f172f64d12aa711d2169b27d8611f268627e)) — @cnkang
- Catalog): review disclosure for breadcrumbs ([`5c8a12fe`](https://github.com/NousResearch/hermes-agent/commit/5c8a12fef1b4929c26d399b8679707fc7d63f5e7))
- Catalog): review disclosure for case-trail, creator-studio, game-lab, live2d-rigger, pagecast-director, skill-workshop ([`2f6bee0f`](https://github.com/NousResearch/hermes-agent/commit/2f6bee0fcd2ff26f327dd21243fc9b81eb15871e))
- Plugin-catalog): creator-studio 0.5.1 (GPU device choice fix) ([`c7e29cae`](https://github.com/NousResearch/hermes-agent/commit/c7e29cae3df009a16b911aa7a065389d2a90736f)) — @flabanabba8
- Catalog): pin proofops 0.7.1 - diff command, refusal names its fix ([`e017b32e`](https://github.com/NousResearch/hermes-agent/commit/e017b32e30fdbdbeda632f81cd3493ae99810911)) — @rasrobo
- Plugin-catalog): bump kiro-provider to v1.1.0 ([`d50e92a8`](https://github.com/NousResearch/hermes-agent/commit/d50e92a897c9e09cb4244367ec3dd4c8b927c103)) — @anpicasso
- Plugin-catalog): bump cursor-provider to v0.5.0 ([`cb284428`](https://github.com/NousResearch/hermes-agent/commit/cb28442899a2b0bc5926bebc940d7f632e56fadc)) — @anpicasso
- Catalog): bump go-whatsapp to v0.6.0 ([`842cc138`](https://github.com/NousResearch/hermes-agent/commit/842cc138206f699f15289d35425f6f63e15ade64)) — @anpicasso
- Catalog): bump go-whatsapp to v0.5.0 ([`db03a162`](https://github.com/NousResearch/hermes-agent/commit/db03a162b4f50fae7548ff2b20e625b89a008b48)) — @anpicasso
- Catalog): bump jev-approvals to v0.4.0 ([`f75f8285`](https://github.com/NousResearch/hermes-agent/commit/f75f82856bdcb99bc634b334a6a29df598e58bb5)) — @anpicasso
- Catalog): bump hermes-plugin-chrome-profiles to v2.0.1 ([`175deb22`](https://github.com/NousResearch/hermes-agent/commit/175deb22548f420fba5e39ef24d61ad4090e2551)) — @anpicasso
- Catalog): review disclosure for heartbeat2 ([`e7fe4baa`](https://github.com/NousResearch/hermes-agent/commit/e7fe4baa05bcdbb6863e906e2341bc5a2c3859ac))
- Catalog): review disclosure for hermes-crm ([`2ccdb4e1`](https://github.com/NousResearch/hermes-agent/commit/2ccdb4e134a65d1e07e8106f60911b2525819c0a))
- Catalog): review disclosure for holographic ([`3e3650f2`](https://github.com/NousResearch/hermes-agent/commit/3e3650f2962e8082c0ee4bbd282b5cbdf2ebbc4c))
- Catalog): review disclosure for aeorank ([`6118e0a8`](https://github.com/NousResearch/hermes-agent/commit/6118e0a8dd9f20d23d6206a8d4bf70ce24b5185d))
- Catalog): review disclosure for ciphervault ([`12c9e250`](https://github.com/NousResearch/hermes-agent/commit/12c9e25055714f7270d7bfda45e40392e8ca17ed))
- Catalog): bump ciphervault to 0.6.5 (6009fed) — restrict recovery_drill via to configured public operators ([`666a7c3d`](https://github.com/NousResearch/hermes-agent/commit/666a7c3d9415e87f6df0b3ebf861dc3f351bac62)) — @samuel-1-avson
- Map contributor email for Yonathan-T ([`08d0df03`](https://github.com/NousResearch/hermes-agent/commit/08d0df03097f221a2793610254d6a78c6fe70718))
- Catalog): review disclosure for hermes-janus ([`ea9cc5a1`](https://github.com/NousResearch/hermes-agent/commit/ea9cc5a1447f5ef4d9a34be54965f1b915af26e5))
- Map contributor email for craigmbrown ([`8cb8b85a`](https://github.com/NousResearch/hermes-agent/commit/8cb8b85a4458c833ad7dd576b240301109dfde6c))
- Catalog): review disclosure for blindoracle ([`65f9f43d`](https://github.com/NousResearch/hermes-agent/commit/65f9f43d7a45cd14a670753bf79cdd78769ecdb8))
- Catalog): re-pin cmi to 1.12.3 ([`2076aa4c`](https://github.com/NousResearch/hermes-agent/commit/2076aa4cf2aa88b4ffea0c450dfd2c78d344d646)) — @jeremiebergel
- Plugin-catalog): toll 0.3.0 ([`bab37134`](https://github.com/NousResearch/hermes-agent/commit/bab3713404b2e39c6f7b7fb3459a12e93c0a6978)) — @soli0x
- Catalog): review disclosure for model-explainer ([`ba709bdc`](https://github.com/NousResearch/hermes-agent/commit/ba709bdc1c4bca6b8b5c5ca15c43352ee29accc2))
- Catalog): review disclosure for mesh-check ([`81f28eee`](https://github.com/NousResearch/hermes-agent/commit/81f28eee36c2ec2140d578f6926da051f79356fb))
- Map contributor email for shengqiqwq-spec ([`a99e4240`](https://github.com/NousResearch/hermes-agent/commit/a99e42403e4c735945116c2364c71f45a8380210))
- Map contributor email for nicholaslaldigital ([`c8cb045f`](https://github.com/NousResearch/hermes-agent/commit/c8cb045fd63dc80125490208b94e54bd22baf843))
- Catalog): review disclosure for memorybank ([`e12dad13`](https://github.com/NousResearch/hermes-agent/commit/e12dad131fe87c900937e1ab5e3034dad3744351))
- Plugin-catalog): re-pin memorybank to 1.4.0 ([`788de31b`](https://github.com/NousResearch/hermes-agent/commit/788de31ba36a582ead04dac86c921371ba116594)) — @nicholaslaldigital
- Catalog): update SessionCrew to 0.2.0 ([`4dab8b85`](https://github.com/NousResearch/hermes-agent/commit/4dab8b854f9b908f803f990354b38ccc9d69865e)) — @shirogane-yuine[bot]
- Map contributor email for jarrett-del ([`e0160cd6`](https://github.com/NousResearch/hermes-agent/commit/e0160cd6cc21b458cda66ce63e60d6ce6d6116d2))
- Catalog): review disclosure for bae ([`37834cac`](https://github.com/NousResearch/hermes-agent/commit/37834cacb748192f35c959e7384b006c42f95842))
- Plugin-catalog): re-pin meetstream to 4d43b0f (meeting chat is web-only) ([`beac86db`](https://github.com/NousResearch/hermes-agent/commit/beac86dbed6169d8e745f20912b9b5422042ec71)) — @doluz
- Map contributor email for forgoneops ([`945cf16a`](https://github.com/NousResearch/hermes-agent/commit/945cf16a6237cce05c720b566937f998c09bf1c9))
- Catalog): review disclosure for hermes-reading ([`c9a00232`](https://github.com/NousResearch/hermes-agent/commit/c9a0023233772e3f125e7472b0a123d962cbc342))
- Catalog): review disclosure for hermes-browser-extension ([`645a741c`](https://github.com/NousResearch/hermes-agent/commit/645a741c049424807c506fd86db5b842199a403c))
- Catalog): review disclosure for hermes-workflows ([`365177e5`](https://github.com/NousResearch/hermes-agent/commit/365177e5afe9f576a84a835ca102de0679bcaf3c))
- Plugin-catalog): repin hermes-workflows to v1.4.9 (est-gosrh) ([`ac3370e5`](https://github.com/NousResearch/hermes-agent/commit/ac3370e543cc1e5e871c4447197a439b5d1a9732)) — @jacobhausler
- Plugin-catalog): pin Finder v1.2.0 source ([`2ca88548`](https://github.com/NousResearch/hermes-agent/commit/2ca885484c70b7f86c804436b82f796008ae11eb)) — @oways
- Plugin-catalog): bump Finder to v1.2.0 ([`c7cb4211`](https://github.com/NousResearch/hermes-agent/commit/c7cb4211c46a23db003b88cfa3e096f3bee0d7de)) — @oways
- Map contributor email for AbigailDavised ([`1d1d070c`](https://github.com/NousResearch/hermes-agent/commit/1d1d070cdf0feb7fec6ec7fc387cc1cb67fe4a0f))
- Map contributor email for krumjahn ([`d9b06b7b`](https://github.com/NousResearch/hermes-agent/commit/d9b06b7bcbe11cc43a6a4900766771c4a58f96d2))
- Catalog): review disclosure for vividsites ([`338e355f`](https://github.com/NousResearch/hermes-agent/commit/338e355f52756259a2f63c8d234851a728196ad1))
- Map contributor email for sr33j ([`7f3cd4af`](https://github.com/NousResearch/hermes-agent/commit/7f3cd4af9eb9044093d541d31a98d84310c14a23))
- Catalog): review disclosure for crowdcode ([`814ee52d`](https://github.com/NousResearch/hermes-agent/commit/814ee52d286a353cde74a2c1f6d1ced5bb2a4f40))
- Catalog): review disclosure for wiretap ([`51f7384c`](https://github.com/NousResearch/hermes-agent/commit/51f7384c2feabc701a1846631a470755da89608d))
- Catalog): review disclosure for living-spaces ([`e8899af6`](https://github.com/NousResearch/hermes-agent/commit/e8899af62ed0abd80b77f83cc6a1d7b387f68775))
- Catalog): pin Living Spaces review fixes ([`19825b77`](https://github.com/NousResearch/hermes-agent/commit/19825b77d63a16d8b7b6ffc2e6dabb73dd65e1cc)) — @akinduroifedayo
- Map contributor email for hi4c0ck ([`e5cbf587`](https://github.com/NousResearch/hermes-agent/commit/e5cbf587cf6bc7bb03336a3e8fc0d7eee7750660))
- Catalog): review disclosure for its-in-your-head ([`3656d6c9`](https://github.com/NousResearch/hermes-agent/commit/3656d6c9df0495ff2b5f671675fdc9a73203ad0e))
- Catalog): review disclosure for vitam ([`d99de4cc`](https://github.com/NousResearch/hermes-agent/commit/d99de4ccdc97743e8b6139b03162b5a9540a962b))
- Catalog): review disclosure for rh-preflight ([`fc7b6e11`](https://github.com/NousResearch/hermes-agent/commit/fc7b6e111ecf646958ea3c62f48797e219ae43ff))
- Pin rh-preflight 0.5.4 ([`f0d4415a`](https://github.com/NousResearch/hermes-agent/commit/f0d4415af45cb9bbd2b84846d4c9592278c16c0b)) — @quotumorg
- Catalog): review disclosure for zerofactory ([`5775e245`](https://github.com/NousResearch/hermes-agent/commit/5775e2450d5684cb8b6dbb433efc7ac872817fa5))
- Plugin-catalog): bump zerofactory sha to a8e1e630 ([`0b91b8c5`](https://github.com/NousResearch/hermes-agent/commit/0b91b8c503efe3584160305781628fac0e18b461)) — @ntsd
- Catalog): re-pin zerofactory sha to 626c043 ([`00f8b129`](https://github.com/NousResearch/hermes-agent/commit/00f8b1292b678b0878dfd99a45d438228e643b1f)) — @ntsd
- Plugin-catalog): re-pin zerofactory to 7eab8740 ([`197578bd`](https://github.com/NousResearch/hermes-agent/commit/197578bd3a09a99e13fadfd03266c95fcb079bc9)) — @ntsd
- Update zerofactory to v1.3.0 with self-healing recovery ([`0252637d`](https://github.com/NousResearch/hermes-agent/commit/0252637dabc7f5547de90eabbd201d1b4968ce46)) — @ntsd
- Update zerofactory plugin to v1.3.0 ([`e28aa193`](https://github.com/NousResearch/hermes-agent/commit/e28aa193162a06776bb601ac75092c66f7b6f270)) — @ntsd
- Map contributor email for wusanjay ([`03b25a7e`](https://github.com/NousResearch/hermes-agent/commit/03b25a7e79921815841204da15a8e3999964eddc))
- Catalog): review disclosure for rea-video-hermes ([`3f0b88a8`](https://github.com/NousResearch/hermes-agent/commit/3f0b88a890457baa280a3bde616cc51ee7fde8d5))
- Catalog): review disclosure for hermes-templates ([`bdc78f05`](https://github.com/NousResearch/hermes-agent/commit/bdc78f0519476e09326ad5773707a906a4b4c56a))
- Catalog): review disclosure for antigravity-subscription-directsdk ([`7ec8b2b8`](https://github.com/NousResearch/hermes-agent/commit/7ec8b2b810bb07190dffcc964f9a63f157bc83d7))
- Catalog): bump antigravity-subscription-directsdk to 1.0.27 ([`6b3d45b4`](https://github.com/NousResearch/hermes-agent/commit/6b3d45b4dabcd2860c65ee67238bfc70308d8ebf)) — @soyelmismo
- Catalog): bump antigravity-subscription-directsdk to 1.0.26 ([`79bcfa77`](https://github.com/NousResearch/hermes-agent/commit/79bcfa7717a61579ea6a4be671208cb5bb02ecb4)) — @soyelmismo
- Catalog): pin antigravity-subscription-directsdk to a055427 (v1.0.25) ([`33e35cb7`](https://github.com/NousResearch/hermes-agent/commit/33e35cb7e113840db478132f2ecbfcddfc3d11a8)) — @soyelmismo
- Catalog): review disclosure for operate-hermes-plugin ([`f7838034`](https://github.com/NousResearch/hermes-agent/commit/f7838034f2ff879942df867f8d3c9fccf75ca0b3))
- Plugin-catalog): re-pin operate-hermes-plugin to dea1145e (v1.2.0) ([`a0b794b2`](https://github.com/NousResearch/hermes-agent/commit/a0b794b2bee1ada483e3c68f14194a425e6d50bb)) — @rxdha1
- Catalog): review disclosure for worktable ([`9c191714`](https://github.com/NousResearch/hermes-agent/commit/9c1917144e180cfb5f4358708986b750bbb1a5f2))
- Map contributor email for Tsurgcom ([`1a45f009`](https://github.com/NousResearch/hermes-agent/commit/1a45f0093b489c0d258b6c80b3d91444f4f50a18))
- Catalog): review disclosure for hermes-teleoperator ([`ef0b28fb`](https://github.com/NousResearch/hermes-agent/commit/ef0b28fb366a6f18f5bc5654268113c282fb0d23))
- Catalog): review disclosure for autorag ([`d9855cad`](https://github.com/NousResearch/hermes-agent/commit/d9855cad0f7b39ed36c7e1951bc573c9aafdcafc))
- Map contributor email for lester076 ([`368d982b`](https://github.com/NousResearch/hermes-agent/commit/368d982b7d4c93312aeef90e043b3be38c132a9d)) — @c2h5oh
- Plugins): record the FAL video plugin's direct_fal_client import in the boundary baseline ([`ab7b3ad8`](https://github.com/NousResearch/hermes-agent/commit/ab7b3ad8068129aa707b37ae57c22be46811a2b5)) — @kshitijk4poor

## 📦 Other Changes

- Plugin-catalog: glasses-platform 0.6.8 ([`9dffcfba`](https://github.com/NousResearch/hermes-agent/commit/9dffcfbaa23f4f0a7783e3c58bede8874f8099ed)) — @100yenadmin
- Plugin-catalog: shinjuku pins db1ced6 (0.1.1: setup lines for Windows, Git listed as a prerequisite) ([`8783054e`](https://github.com/NousResearch/hermes-agent/commit/8783054ef6cbafd86f10892241436862c1171a66)) — @Shinjuku-StAItion
- Pin catalog entry to security fix ([`ed8fd34a`](https://github.com/NousResearch/hermes-agent/commit/ed8fd34abc3f6e1cb1eb9ac6084ae1faeadcf348)) — @isthatananya
- Pin hermes-eye-memory to compatibility fix ([`13ba0436`](https://github.com/NousResearch/hermes-agent/commit/13ba0436cfdece193383f6d71dc3c2c371304480)) — @isthatananya
- Catalog: remove follow-through (author withdrew plugin) ([`cd922988`](https://github.com/NousResearch/hermes-agent/commit/cd92298898750af19feb72a3e6e7aff51f4bac12)) — @Agenziamaia
- Catalog: remove eyes (author withdrew plugin) ([`e96ae552`](https://github.com/NousResearch/hermes-agent/commit/e96ae5523f77bf3a782d56400e828d550d4921ae)) — @Agenziamaia
- Catalog: remove card-grader (author withdrew plugin) ([`de9a2f30`](https://github.com/NousResearch/hermes-agent/commit/de9a2f307c9a456e041674f31d5cbd17cdd21914)) — @Agenziamaia
- Plugin-catalog: re-pin tironian to 3b8c1f1 (post-deadline fixes) ([`c0fbe46e`](https://github.com/NousResearch/hermes-agent/commit/c0fbe46ebabe25272063f35e1e66d866639eeddd)) — @angelraph
- Plugin-catalog: bump tironian to 0.2.0 (e25e339) ([`6f0d8dd6`](https://github.com/NousResearch/hermes-agent/commit/6f0d8dd60a5a7be4d26ad8009efc25042bf377c0)) — @angelraph
- Pin: the dependency declaration rides along (websockets floor+bound) ([`129b3427`](https://github.com/NousResearch/hermes-agent/commit/129b3427cccd36f1186c5a02be83641a6b791a69)) — @cruzlxyz
- Rebrand: gemini-live-bridge becomes livetalk (pin v2.0.0) ([`4436eb78`](https://github.com/NousResearch/hermes-agent/commit/4436eb78c961c3a341fca8da1e41b3eb2ae9fd02)) — @cruzlxyz
- Rebrand: gemini-live-bridge becomes livetalk (pin v2.0.0) ([`34244862`](https://github.com/NousResearch/hermes-agent/commit/34244862a59589c820c12d882c340b483f9e3a4e)) — @cruzlxyz
- Create shaderbruecke.yaml ([`84b8e304`](https://github.com/NousResearch/hermes-agent/commit/84b8e304a4c363383a790408cb16e2cdccd94106)) — @studioluftbruecke
- Pin Asset Curator 0.3.0 user-controlled access fix ([`89733a5f`](https://github.com/NousResearch/hermes-agent/commit/89733a5f38a70b3138c5fcaf4e1b2511f8bbc5df)) — @dev-willbird1936
- Video-xray: dedupe screenshot list ([`c4b14bd3`](https://github.com/NousResearch/hermes-agent/commit/c4b14bd34761ba2d3ecf88f5eea57422aae32da3)) — @LuuMoss
- Video-xray: re-pin to v0.2.2 (review round 2 fixes) ([`f43231b4`](https://github.com/NousResearch/hermes-agent/commit/f43231b4f56d73d126d9734e465e8faa2518b527)) — @LuuMoss
- Video-xray: pin v0.2.1 (review fixes: worker env, secret scope, path whitelist, plugin-data storage) ([`e244fcd4`](https://github.com/NousResearch/hermes-agent/commit/e244fcd489c3fe031a0040a938eaa8d8036a9ff6)) — @LuuMoss
- Plugin-catalog: bump lancedb-suite to v1.8.0 ([`6fd0faa9`](https://github.com/NousResearch/hermes-agent/commit/6fd0faa9a7b7c3c3b2c71c0d88e3c7fa5846b2e8)) — @3L0935
- Plugin-catalog: pin luminary at the load fix ([`de0e0741`](https://github.com/NousResearch/hermes-agent/commit/de0e074163ddbe38889bd9e71517d0348eacd587)) — @alertxsto
- Plugin-catalog: bump plan-mode to 1.5.2 ([`4d661c60`](https://github.com/NousResearch/hermes-agent/commit/4d661c609387370ee8ba665d652da2c2cfcad0bb)) — @100yenadmin
- Plugin-catalog: bump plan-mode to 1.5.1 ([`7f484d04`](https://github.com/NousResearch/hermes-agent/commit/7f484d04714303185cfd07d9c0f56cc65a150e1c)) — @100yenadmin
- Catalog: re-pin deepseek-web-tools to 1.0.1 (second review pass) ([`b747a84a`](https://github.com/NousResearch/hermes-agent/commit/b747a84a79be22476aa1969a3f7f0853490ab709)) — @fedebyes
- Catalog: re-pin theme-catalog to 0.4.0 (253a08f7) ([`16f8271e`](https://github.com/NousResearch/hermes-agent/commit/16f8271ebf2aaa030c6c9bac42a05ed6ff6945e3)) — @0-CYBERDYNE-SYSTEMS-0
- Catalog: pin Sentinel Governance v0.7.0 with reviewed disclosures ([`0e5409ab`](https://github.com/NousResearch/hermes-agent/commit/0e5409abe7f4f3ef5fc1fd49b30d3c19d0d9034e)) — @ChasClogston
- Create forgebruecke.yaml ([`90f67668`](https://github.com/NousResearch/hermes-agent/commit/90f6766832b651a649afb325b029b055ce929cee)) — @studioluftbruecke
- Create coolifybruecke.yaml ([`2ebdf0c5`](https://github.com/NousResearch/hermes-agent/commit/2ebdf0c59c0f7f580e3289ddcf759b7f35b4e74b)) — @studioluftbruecke
- Plugin-catalog: re-pin hermes-phone-control to f41e2c67 ([`9af4e6a2`](https://github.com/NousResearch/hermes-agent/commit/9af4e6a2571150b6e683995a60a7f325f5464f29)) — @jinsu133
- Plugin-catalog: bump own-compute to d203de9 ([`709b9df7`](https://github.com/NousResearch/hermes-agent/commit/709b9df7a21f241e4562f46d7ee55e6db6d8fdb8)) — @Siioh
- Plugin-catalog: bump own-compute to 97522db ([`a118cf33`](https://github.com/NousResearch/hermes-agent/commit/a118cf3321ccf077e8ed0fb3bb7a11fbb8ea3f38)) — @Siioh
- Plugin-catalog: bump own-compute to ec3c166 ([`426bdfce`](https://github.com/NousResearch/hermes-agent/commit/426bdfce71b94df0a708da4fbfb5fd2c0c742acb)) — @Siioh
- Catalog: re-pin data-wrangler to 7c32cb8 (approval-gated write fix) ([`bfa7cffc`](https://github.com/NousResearch/hermes-agent/commit/bfa7cffcd3924c953d17aeee5cc391d6c2886177)) — @yogeshchoudhary555
- Code-assurance-engine: pin 4a31218 (allowlisted git env, confined --state-dir, repo filter drivers refused) ([`96cf6def`](https://github.com/NousResearch/hermes-agent/commit/96cf6defdc96aa54ea074f5968892034d2f8b42d)) — @Sahil-SS9
- Printwatch: v0.4.3 (sha 1919e952) — approval gate via pre_tool_call on hardware tools (round-3 delta) ([`684b46bb`](https://github.com/NousResearch/hermes-agent/commit/684b46bbfc88a34ad19d821ae2ded5327d950d92)) — @clawsyndicate
- Printwatch: v0.4.2 (sha 04412872) — public secret_scope + plugin_storage APIs (round-2 review delta) ([`76d89d6d`](https://github.com/NousResearch/hermes-agent/commit/76d89d6d9917992e38c8f9c91814101a21411c26)) — @clawsyndicate
- Printwatch: v0.4.1 catalog entry (sha b5aec03 — review fixes: handler contract, python_dependencies, secret_scope, printer_upload, snapshot path) ([`40fbbbce`](https://github.com/NousResearch/hermes-agent/commit/40fbbbce5cca5535be74ce73548799055cd54f9e)) — @clawsyndicate
- Re-pin visor to 5c89350e (v1.10: second catalog-review round) ([`ee9c7222`](https://github.com/NousResearch/hermes-agent/commit/ee9c7222bd202ffa6b0629decbac86a02dcbf477)) — @samundra0
- Plugin-catalog: visor — pin 17a8ba5 (Docker path fix: container bind + entrypoint token export) ([`c91f9dbc`](https://github.com/NousResearch/hermes-agent/commit/c91f9dbc792911dc746ab1b976305175085b14dc)) — @samundra0
- Plugin-catalog: boardstate 1.5.13 ([`dca59037`](https://github.com/NousResearch/hermes-agent/commit/dca5903772ead77a61b8e5ee424dac1cfbebd532)) — @100yenadmin
- Catalog: bump coach to 1.0.1 ([`d0a28d1e`](https://github.com/NousResearch/hermes-agent/commit/d0a28d1e3b30de75a129a7209dcfc2bee2c40784)) — @Printaga
- Pin merged Yandex README fixes ([`89de04f2`](https://github.com/NousResearch/hermes-agent/commit/89de04f2237238aeae081ccb8794bf6b9d3355ec)) — @akinfold
- Plugin-catalog: bump searchscope-ai-visibility to c32b657 ([`1a3e5837`](https://github.com/NousResearch/hermes-agent/commit/1a3e58372ed692c1a5a5a093b82ccea4ba307bab)) — @InovArcAi
- Plugin-catalog: bump browser-viewer to 0.2.0 (macOS support) ([`d9848654`](https://github.com/NousResearch/hermes-agent/commit/d98486540173c9d8832fbd6b361cf746a1654f3d)) — @vittoriocompagno
- Plugin-catalog: hermes-kame-api-rotation 1.9.0.1 ([`9614ef63`](https://github.com/NousResearch/hermes-agent/commit/9614ef63bdc117013d99843d1e1c3579879ceae4)) — @Kame696
- Plugin-catalog: hermes-kame-provider 1.9.0.0 ([`4e04390c`](https://github.com/NousResearch/hermes-agent/commit/4e04390c513816b82aded53b9587017857339596)) — @Kame696
- Plugin-catalog: hermes-kame-api-rotation 1.9.0.0 ([`45a56137`](https://github.com/NousResearch/hermes-agent/commit/45a56137da4e2dee62512b32a471d1d4467c85fd)) — @Kame696
- Plugin-catalog: bump hermes-teammates to 1.8.0 ([`a7fe1ba9`](https://github.com/NousResearch/hermes-agent/commit/a7fe1ba9d5feb52eac31b25b7b1ee89b34c6170e)) — @100yenadmin
- Plugin-catalog: bump hermes-teammates to 1.7.0 ([`4f8849cf`](https://github.com/NousResearch/hermes-agent/commit/4f8849cf0e147dfc37e35df342cd43c460627df8)) — @100yenadmin
- Plugin-catalog: breadcrumbs 0.5.0 (breadcrumbs-hermes replaces hermes-breadcrumb-plugin) ([`e060ce76`](https://github.com/NousResearch/hermes-agent/commit/e060ce76a3edf9dace224906b0ee498648d7f1b6)) — @jnorthrup
- Plugin-catalog: bump stoa to 0.21.0 ([`7d4e75f9`](https://github.com/NousResearch/hermes-agent/commit/7d4e75f9cc95547bf3530d2ecc53b29cb0def5b3)) — @jarrett-del
- Plugin-catalog: bump stoa to 0.20.4 ([`3eeb698b`](https://github.com/NousResearch/hermes-agent/commit/3eeb698b41469f5a7810d9fc79519f424686f5f5)) — @jarrett-del
- Plugin-catalog: bump stoa to 0.20.3 ([`c648e84e`](https://github.com/NousResearch/hermes-agent/commit/c648e84eb50f34e9216e28df8730c6537d224bb2)) — @jarrett-del
- Plugin-catalog: bump stoa to 0.20.1 ([`4b615e63`](https://github.com/NousResearch/hermes-agent/commit/4b615e6376b2413ed3cb451de8e7edfd91532723)) — @jarrett-del
- Plugin-catalog: bump stoa to 0.20.0 ([`5504bdc4`](https://github.com/NousResearch/hermes-agent/commit/5504bdc4331aedeac0887efbc1d4afc8882849dc)) — @jarrett-del
- Catalog: re-pin case-trail (plugin.yaml floor now matches requires_hermes, rule 14) ([`257a4bf3`](https://github.com/NousResearch/hermes-agent/commit/257a4bf384fe223007f42db50baf8724a3661ff8)) — @flabanabba8
- Catalog: re-pin live2d-rigger (plugin.yaml floor now matches requires_hermes, rule 14) ([`5dd03b58`](https://github.com/NousResearch/hermes-agent/commit/5dd03b5874b92d2fa3a9e2de16073862c683c59d)) — @flabanabba8
- Catalog: re-pin game-lab (plugin.yaml floor now matches requires_hermes, rule 14) ([`0ba2814d`](https://github.com/NousResearch/hermes-agent/commit/0ba2814dcaf116b00e73f5206794b954cb1a02d3)) — @flabanabba8
- Catalog: re-pin creator-studio 0.5.2 (Clip Studio no longer uses browser cookies, rule 11) ([`d70ca673`](https://github.com/NousResearch/hermes-agent/commit/d70ca673cf75460c0275e90a9b214379cdcab3aa)) — @flabanabba8
- Revert "chore(catalog): bump jev-approvals to v0.4.0" ([`55c7eb45`](https://github.com/NousResearch/hermes-agent/commit/55c7eb45ca6e43fa614a8d2538b4fd86c786e6b7)) — @anpicasso
- Plugin-catalog: heartbeat2 0.4.5 ([`189d589c`](https://github.com/NousResearch/hermes-agent/commit/189d589c154d5c259ba5ab09892b5f9ee550b39b)) — @100yenadmin
- Plugin-catalog: re-pin local-hands to d302f63 (1.1.0) ([`b1ef643e`](https://github.com/NousResearch/hermes-agent/commit/b1ef643e947eaab080c09ebca20b8a03a0afca29)) — @noegng
- Plugin-catalog: holographic 0.28.0 ([`5fabf63a`](https://github.com/NousResearch/hermes-agent/commit/5fabf63a7a0cf7d5a7f07477988e0ad4ffb78eeb)) — @itpartypattaya
- Plugin-catalog: bump ciphervault to 0.6.2 ([`6bdc3605`](https://github.com/NousResearch/hermes-agent/commit/6bdc36058ecef43b7361ce3c54a9f9d568042f7a)) — @samuel-1-avson
- Plugin-catalog: construct 1.3.2 ([`dcaba002`](https://github.com/NousResearch/hermes-agent/commit/dcaba002d594a35b112a25829c877b05ecff50cb)) — @rtmandreyev
- Catalog: live-video 1.3.6 (mic state honesty, single permission prompt) ([`e512bf7e`](https://github.com/NousResearch/hermes-agent/commit/e512bf7edc80a2fbec4b8bdf3c315ea3d41d1713)) — @dacheah
- Catalog: live-video 1.3.5 (LAN token cookie) ([`c1621473`](https://github.com/NousResearch/hermes-agent/commit/c162147377f186b0148d8ef84741e21645f8b359)) — @dacheah
- Catalog: live-video 1.3.4 (Windows verified on hardware) ([`3f24260a`](https://github.com/NousResearch/hermes-agent/commit/3f24260ace0b25a003ca96c086c1188753e3ef59)) — @dacheah
- Catalog: live-video 1.3.3 (self-excluding tracker scan) ([`5bbc8ddf`](https://github.com/NousResearch/hermes-agent/commit/5bbc8ddf1549597077d8c412f8417566d2c02721)) — @dacheah
- Catalog: live-video 1.3.2 (Windows child environment) ([`8e81af05`](https://github.com/NousResearch/hermes-agent/commit/8e81af0549a0af44886cef05f1e22c3856f2d08b)) — @dacheah
- Catalog: live-video 1.3.1 (zombie-aware stop, host self-test) ([`7ae853b8`](https://github.com/NousResearch/hermes-agent/commit/7ae853b888ccba22ad33668368b6c79682fae2fd)) — @dacheah
- Catalog: live-video 1.3.0 with Windows support ([`55ee272f`](https://github.com/NousResearch/hermes-agent/commit/55ee272f741235d48014e60b6205c94c09412fba)) — @dacheah
- Plugins: pin Inline 1.2.0 ([`2bc406cc`](https://github.com/NousResearch/hermes-agent/commit/2bc406cc4b3de36253cfe4dbae60fce8ac9f5367)) — @morajabi
- Plugin-catalog: bump emotion-chip to 0.3.4 ([`374c2450`](https://github.com/NousResearch/hermes-agent/commit/374c2450a5935ac10fc58434359dd7fb6bdaef95)) — @100yenadmin
- Catalog: pin Rails 0.4.3 continuation authorization fixes ([`b313d994`](https://github.com/NousResearch/hermes-agent/commit/b313d994f725cf806173832a3a67a84ddac86662)) — @grimmjoww578
- Catalog: rails 0.4.1 — card image + re-pin ([`abe4bfb0`](https://github.com/NousResearch/hermes-agent/commit/abe4bfb047200ee9a9e79db9d47be621972392d3)) — @grimmjoww578
- Correct Hermes Reading plugin pin ([`a7354625`](https://github.com/NousResearch/hermes-agent/commit/a7354625b30bdaba9803eb4f31ca827b5b84e697)) — @forgoneops
- Catalog: use a 2:1 cover image for hermes-browser-extension ([`3c3e7f6d`](https://github.com/NousResearch/hermes-agent/commit/3c3e7f6d280a2e3df6172dc43bb0ae3db5611733)) — @abundantbeing
- Catalog: re-pin hermes-browser-extension to 438460d4 (public profile APIs only) ([`b4afe409`](https://github.com/NousResearch/hermes-agent/commit/b4afe4095d24ff77b82c98f54292f6f0f23d63fc)) — @abundantbeing
- Catalog: re-pin hermes-browser-extension to v0.4.1 (a04b7e12) ([`e08cf0ec`](https://github.com/NousResearch/hermes-agent/commit/e08cf0ec5420c803e96eef98bf095047ee1afcfa)) — @abundantbeing
- Describe VividSites cinematic website design and pin verified metadata update ([`8b38d850`](https://github.com/NousResearch/hermes-agent/commit/8b38d850a0743a6573e10b56eeb8ee9cc4d6e143)) — @krumjahn
- Pin reviewed VividSites source hardening ([`9e3505d5`](https://github.com/NousResearch/hermes-agent/commit/9e3505d5899bbe7ff737b8d8679b3583177716cf)) — @krumjahn
- Crowdcode: re-pin to d23d30f (0.2.2): downloads stay in the session folder unless approved ([`ef781007`](https://github.com/NousResearch/hermes-agent/commit/ef781007f2c20451e5196c4595d1a193006e58ff)) — @sr33j
- Crowdcode: re-pin to 304aa09 (0.2.1): every money move asks for approval by default ([`caa9cbb2`](https://github.com/NousResearch/hermes-agent/commit/caa9cbb28e92b625bf096cd27929c9294ccaf52a)) — @sr33j
- Catalog: pin living-spaces to e6145cc (current release documentation) ([`a4adbfc5`](https://github.com/NousResearch/hermes-agent/commit/a4adbfc5f0823f66eaabd8478fdaf0f2f67def41)) — @akinduroifedayo
- Catalog: pin living-spaces to 4f0b419 (same plugin package, cleaned repo and README) ([`95905d6c`](https://github.com/NousResearch/hermes-agent/commit/95905d6c83b8f42cb680d0d2339b703ad1ee3bf5)) — @akinduroifedayo
- Catalog: simplify Living Spaces listing copy ([`7a7c170c`](https://github.com/NousResearch/hermes-agent/commit/7a7c170c9d9ccec716eb39cf7a86a3d4d1a30a5a)) — @akinduroifedayo
- Catalog: re-pin its-in-your-head to 8c41205 / 0.1.29; re-pin image+screenshots ([`d122c4a1`](https://github.com/NousResearch/hermes-agent/commit/d122c4a1d70e29a9e9830c2615e8fb71f38a2c17)) — @hi4c0ck
- Catalog: repin its-in-your-head to b83e13f77b0c (last main: docs drop + strip retake) ([`b85e852c`](https://github.com/NousResearch/hermes-agent/commit/b85e852c8d397e8b399e3a5a186d8b9906fa6e9c)) — @hi4c0ck
- Plugin-catalog(its-in-your-head): re-pin to 407b05d (final: PULSE-only strip docs sync) ([`e23c2c18`](https://github.com/NousResearch/hermes-agent/commit/e23c2c1855e93796ae54b922b829839004ad2797)) — @hi4c0ck
- Plugin-catalog(its-in-your-head): re-pin to 0a7db3d (v0.1.25 compact PULSE-only strip + recaptured asset) ([`bb8a417f`](https://github.com/NousResearch/hermes-agent/commit/bb8a417f6b41f0676f40e12970113b83ec01fa36)) — @hi4c0ck
- Plugin-catalog(its-in-your-head): re-pin to cbce429 (docs: manual + live screenshots) + gallery shots ([`d81c3da1`](https://github.com/NousResearch/hermes-agent/commit/d81c3da19f9e676672d7cf5cd1e6f9cd7a65257f)) — @hi4c0ck
- Catalog(vitam): re-pin to 35b7abfc (command-handler closure fix) and bump to 1.1.1 ([`f9c119d5`](https://github.com/NousResearch/hermes-agent/commit/f9c119d57aee9be72172df85e05bca6c7ab3d0ac)) — @taylorwtf
- Vitam: re-pin e92b558 (pairing token, caps, env/secret hardening per review of effa783f), bump 1.1.0 ([`c8913e01`](https://github.com/NousResearch/hermes-agent/commit/c8913e01098e8e81c178a9880d0e302eb32e0539)) — @taylorwtf
- Re-pin to 5d2bc03 (PLUGIN_DATA portability fix) ([`065e6e73`](https://github.com/NousResearch/hermes-agent/commit/065e6e7304cb2e74878dde3666d6798093bb9eee)) — @wusanjay
- Re-pin to dda5e7d (security review fixes) ([`48b7b5f1`](https://github.com/NousResearch/hermes-agent/commit/48b7b5f19e27a72e817930884227ac709aba942a)) — @wusanjay
- Pin to portable-plugin commit 7216414 (validator green) ([`cdcf35ca`](https://github.com/NousResearch/hermes-agent/commit/cdcf35cab3cd7185177274ad7cdb1dab560fdfd6)) — @wusanjay
- Plugin-catalog: hermes-templates 1.3.1 (re-pin d42a8a9, approval policy) ([`831ad0b8`](https://github.com/NousResearch/hermes-agent/commit/831ad0b86155110420051fbf87ddf959f4c2bc29)) — @Ilyassbm
- Plugin-catalog: hermes-templates 1.3.0 (re-pin 38aa642, review fixes) ([`e7b888c1`](https://github.com/NousResearch/hermes-agent/commit/e7b888c12d0065bb7e1a9d0209a0a978f0d9d862)) — @Ilyassbm
- Worktable: say pairing also sends an installation id ([`2cc031d6`](https://github.com/NousResearch/hermes-agent/commit/2cc031d6719406ae539fedc6e2bf9da7d69081e1)) — @obkaro
- Worktable: pin 0.1.3, only the owner and the owner's agents can direct it ([`4d65f12c`](https://github.com/NousResearch/hermes-agent/commit/4d65f12c445f402c5bb49436cd8bb1e5ac46b4af)) — @obkaro
- OpenRouter's prompt-injection guardrail 403 no longer reads as a firewall/key problem (#155460, salvage #155472) (#155828) ([#155460](https://github.com/NousResearch/hermes-agent/pull/155460))
- Catalog: pin Hermes Teleoperator 1.2.0 ([`585c65b9`](https://github.com/NousResearch/hermes-agent/commit/585c65b9f08982bb0effc90e3eeb6893f64c54a6)) — @Tsurgcom
- Peer: sanitize peer-controlled text before printing to the terminal ([`12d92b12`](https://github.com/NousResearch/hermes-agent/commit/12d92b1260adcacbeb4a4cfba7880ae97dad83c8)) — @beardthelion
- Port from OpenHands/software-agent-sdk#5143: send the compaction summarizer instructions as system + turns as user ([#5143](https://github.com/NousResearch/hermes-agent/pull/5143))

## 👥 Contributors

Thank you to everyone who contributed to this release!

- @BearHuddleston (162 commits)
- @c2h5oh (14 commits)
- @100yenadmin (10 commits)
- @AbigailDavised (10 commits)
- @jarrett-del (10 commits)
- @unifyWeb3 (9 commits)
- @yoniebans (8 commits)
- @earnfidotfun (8 commits)
- @studioluftbruecke (7 commits)
- @anpicasso (7 commits)
- @dacheah (7 commits)
- @ntsd (7 commits)
- @liuhao1024 (7 commits)
- @krumjahn (6 commits)
- @abundantbeing (6 commits)
- @hi4c0ck (6 commits)
- @wusanjay (6 commits)
- @shoyann (6 commits)
- @LuuMoss (5 commits)
- @MFaiqKhan (5 commits)
- @clawsyndicate (5 commits)
- @flabanabba8 (5 commits)
- @akinduroifedayo (5 commits)
- @unsupportedpastels (5 commits)
- @rodricksz4h5 (4 commits)
- @aisenseapi (4 commits)
- @Siioh (4 commits)
- @pCwOrM (4 commits)
- @forgoneops (4 commits)
- @oways (4 commits)
- @kshitijk4poor (4 commits)
- @beardthelion (4 commits)
- @shakeyourbunny (3 commits)
- @isthatananya (3 commits)
- @Agenziamaia (3 commits)
- @cruzlxyz (3 commits)
- @violetSoftware (3 commits)
- @Kame696 (3 commits)
- @grimmjoww578 (3 commits)
- @sr33j (3 commits)
- @taylorwtf (3 commits)
- @quotumorg (3 commits)
- @Ilyassbm (3 commits)
- @soyelmismo (3 commits)
- @obkaro (3 commits)
- @helix4u (3 commits)
- @Tsurgcom (3 commits)
- @angelraph (2 commits)
- @dev-willbird1936 (2 commits)
- @jacobhausler (2 commits)
- @agent-local (2 commits)
- @jeevships (2 commits)
- @alertxsto (2 commits)
- @tuancookiez-hub (2 commits)
- @lazyants (2 commits)
- @Adolanium (2 commits)
- @ChasClogston (2 commits)
- @TakeshiTGAL (2 commits)
- @Sahil-SS9 (2 commits)
- @samundra0 (2 commits)
- @akinfold (2 commits)
- @Elshayib (2 commits)
- @JerryLiu369 (2 commits)
- @fquresh (2 commits)
- @samuel-1-avson (2 commits)
- @Yonathan-T (2 commits)
- @craigmbrown (2 commits)
- @bertheto (2 commits)
- @webtecnica (2 commits)
- @JoaoMarcos44 (2 commits)
- @fangliquanflq (2 commits)
- @aantix (1 commit)
- @Shinjuku-StAItion (1 commit)
- @imperator-clawdius (1 commit)
- @juvenile454 (1 commit)
- @ptaranat (1 commit)
- @lad75020 (1 commit)
- @berthelius (1 commit)
- @shreyasudupi (1 commit)
- @davidpgil (1 commit)
- @dudicslevente (1 commit)
- @rndaom (1 commit)
- @3L0935 (1 commit)
- @bablobanov (1 commit)
- @trenthalden (1 commit)
- @alexeyeryshev (1 commit)
- @waynehamadi (1 commit)
- @fedebyes (1 commit)
- @0-CYBERDYNE-SYSTEMS-0 (1 commit)
- @nicolasbuelvas (1 commit)
- @fitzss (1 commit)
- @ahujat (1 commit)
- @Lugier (1 commit)
- @rbur0425 (1 commit)
- @spranab (1 commit)
- @iknowterry (1 commit)
- @jinsu133 (1 commit)
- @prakhar-raj-031104 (1 commit)
- @yogeshchoudhary555 (1 commit)
- @Printaga (1 commit)
- @wadewegner (1 commit)
- @raidwaleed (1 commit)
- @MadeByBrain (1 commit)
- @InovArcAi (1 commit)
- @cnkang (1 commit)
- @vittoriocompagno (1 commit)
- @openbotgit[bot] (1 commit)
- @ComunionIO (1 commit)
- @jnorthrup (1 commit)
- @rasrobo (1 commit)
- @0x7s0lt1 (1 commit)
- @noegng (1 commit)
- @gptnius (1 commit)
- @itpartypattaya (1 commit)
- @adriens (1 commit)
- @aizaloapp (1 commit)
- @rtmandreyev (1 commit)
- @jeremiebergel (1 commit)
- @soli0x (1 commit)
- @afzalbuilds (1 commit)
- @illusivejosiah (1 commit)
- @morajabi (1 commit)
- @eddwithers (1 commit)
- @BeckleyTenriajeng (1 commit)
- @shengqiqwq-spec (1 commit)
- @nicholaslaldigital (1 commit)
- @shirogane-yuine[bot] (1 commit)
- @doluz (1 commit)
- @aka-lacie (1 commit)
- @rxdha1 (1 commit)
- @sandeepc25 (1 commit)
- @lolchocotaco (1 commit)
- @alt-glitch (1 commit)
- @ygd58 (1 commit)
- David Lepaux (1 commit)
- @mene-crab (1 commit)
- @0xble (1 commit)
- @phon-t (1 commit)
- @vkehfdl1 (1 commit)
- @Bartok9 (1 commit)
- @zapabob (1 commit)
- @memosr (1 commit)
- @zashraf1337 (1 commit)
- @ZHJay (1 commit)
- @asdlem (1 commit)
- @thejesh23 (1 commit)
- @KrasimirKralev (1 commit)
- @iamfoz (1 commit)
- @kouyichi (1 commit)
- @ooiuuii (1 commit)
- @KoNit-K (1 commit)
- @lester076 (1 commit)
- @Chukwuebuka-2003 (1 commit)
- @briandevans (1 commit)
- @LeonSGP43 (1 commit)

**Full Changelog**: [v0.23.1+canary.20261114T064334Z...v0.23.1+canary.20261115T064406Z](https://github.com/NousResearch/hermes-agent/compare/v0.23.1+canary.20261114T064334Z...v0.23.1+canary.20261115T064406Z)</content>
    <ore:provenance>
      <ore:sourceId>hermes-agent-releases</ore:sourceId>
      <ore:sourceName>Hermes Agent GitHub Releases</ore:sourceName>
      <ore:sourceType>github_releases</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://github.com/NousResearch/hermes-agent/releases</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://api.github.com/repos/NousResearch/hermes-agent/releases</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://github.com/NousResearch/hermes-agent/releases/tag/v0.23.1%2Bcanary.20261115T064406Z</ore:originalUrl>
      <ore:upstreamId>RE_kwDOPRF1G84ak1sb</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hacker-news:8e893b9be938e3ad465ea7c93516fbe8</id>
    <title>Why the Airbus A321XLR often gets stuck climbing for first few hours of flight</title>
    <updated>2026-11-14T09:13:24Z</updated>
    <published>2026-11-14T09:13:24Z</published>
    <link rel="alternate" href="https://simpleflying.com/airbus-a321xlr-often-stuck-climbing-1st-few-hours-flight/" />
    <link rel="via" href="https://news.ycombinator.com/rss" />
    <category scheme="urn:ore-news:sources" term="hacker-news" label="Hacker News" />
    <author>
      <name>Hacker News</name>
    </author>
    <source>
      <id>urn:ore-news:source:hacker-news</id>
      <title>Hacker News</title>
      <link rel="alternate" href="https://news.ycombinator.com/" />
      <link rel="via" href="https://news.ycombinator.com/rss" />
    </source>
    <content type="html" />
    <ore:provenance>
      <ore:sourceId>hacker-news</ore:sourceId>
      <ore:sourceName>Hacker News</ore:sourceName>
      <ore:sourceType>rss</ore:sourceType>
      <ore:sourcePlane>discovery</ore:sourcePlane>
      <ore:sourceHomepage>https://news.ycombinator.com/</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://news.ycombinator.com/rss</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://simpleflying.com/airbus-a321xlr-often-stuck-climbing-1st-few-hours-flight/</ore:originalUrl>
      <ore:upstreamId>https://simpleflying.com/airbus-a321xlr-often-stuck-climbing-1st-few-hours-flight/</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
  <entry>
    <id>urn:ore-news:event:hermes-agent-releases:56d8c858c4aba5effb2ce5c92f126fbc</id>
    <title>Hermes Agent canary v0.23.1+canary.20261114T064334Z</title>
    <updated>2026-11-14T07:46:34Z</updated>
    <published>2026-11-14T07:46:34Z</published>
    <link rel="alternate" href="https://github.com/NousResearch/hermes-agent/releases/tag/v0.23.1%2Bcanary.20261114T064334Z" />
    <link rel="via" href="https://api.github.com/repos/NousResearch/hermes-agent/releases" />
    <category scheme="urn:ore-news:sources" term="hermes-agent-releases" label="Hermes Agent GitHub Releases" />
    <author>
      <name>Hermes Agent GitHub Releases</name>
    </author>
    <source>
      <id>urn:ore-news:source:hermes-agent-releases</id>
      <title>Hermes Agent GitHub Releases</title>
      <link rel="alternate" href="https://github.com/NousResearch/hermes-agent/releases" />
      <link rel="via" href="https://api.github.com/repos/NousResearch/hermes-agent/releases" />
    </source>
    <content type="text"># Hermes Agent v0.23.1+canary.20261114T064334Z (v0.23.1+canary.20261114T064334Z)

**Release Date:** November 14, 2026

&lt;!-- HERMES_BUILDS_TABLE --&gt;
## Downloads

### Hermes Desktop

| OS | Architecture | Download |
|---|---|---|
| macOS | Apple Silicon (M-series) | [DMG](https://hermes-assets.nousresearch.com/releases/tag/v0.23.1%2Bcanary.20261114T064334Z/HermesBundled-0.23.1%2Bcanary.20261114T064334Z-mac-arm64.dmg) |
| Windows | x86 (64-bit) | [MSIX](https://hermes-assets.nousresearch.com/releases/tag/v0.23.1%2Bcanary.20261114T064334Z/HermesBundled-0.23.1%2Bcanary.20261114T064334Z-win-x64.msix) |
| Windows | ARM (arm64 / aarch64) | [MSIX](https://hermes-assets.nousresearch.com/releases/tag/v0.23.1%2Bcanary.20261114T064334Z/HermesBundled-0.23.1%2Bcanary.20261114T064334Z-win-arm64.msix) |

### Native install/chat smoke

Download availability is independent of smoke status. Each result covers all native legs in that format group. Linux bundles are disabled; unsigned Store envelopes are not install-smoked. No-upload dry tags have no download handoff and are not smoke-qualified.

| Packages | Smoke status |
|---|---|
| macOS DMG + ZIP (arm64) | Passed |
| Windows MSIX (arm64) | Passed |
| Windows MSIX (x64) | Passed |
&lt;!-- /HERMES_BUILDS_TABLE --&gt;

**Full Changelog**: [v0.23.1+canary.20261113T064447Z...v0.23.1+canary.20261114T064334Z](https://github.com/NousResearch/hermes-agent/compare/v0.23.1+canary.20261113T064447Z...v0.23.1+canary.20261114T064334Z)</content>
    <ore:provenance>
      <ore:sourceId>hermes-agent-releases</ore:sourceId>
      <ore:sourceName>Hermes Agent GitHub Releases</ore:sourceName>
      <ore:sourceType>github_releases</ore:sourceType>
      <ore:sourcePlane>primary</ore:sourcePlane>
      <ore:sourceHomepage>https://github.com/NousResearch/hermes-agent/releases</ore:sourceHomepage>
      <ore:sourceInterfaceUrl>https://api.github.com/repos/NousResearch/hermes-agent/releases</ore:sourceInterfaceUrl>
      <ore:originalUrl>https://github.com/NousResearch/hermes-agent/releases/tag/v0.23.1%2Bcanary.20261114T064334Z</ore:originalUrl>
      <ore:upstreamId>RE_kwDOPRF1G84ah2mg</ore:upstreamId>
      <ore:collectedAt>2026-11-21T07:00:29Z</ore:collectedAt>
    </ore:provenance>
  </entry>
</feed>