<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>openstack/keystonemiddleware — Stackers Network</title>
    <link>https://stackers.network/projects/openstack-keystonemiddleware/</link>
    <atom:link href="https://stackers.network/projects/openstack-keystonemiddleware/feed.xml" rel="self" type="application/rss+xml"/>
    <language>en</language>
    <lastBuildDate>Sat, 24 Oct 2026 00:00:00 +0000</lastBuildDate>
    <description>Weekly code-activity digest for openstack/keystonemiddleware from Stackers Network.</description>
    <item>
      <title>openstack/keystonemiddleware — Week of 2026-10-24</title>
      <link>https://stackers.network/projects/openstack-keystonemiddleware/2026-10-24</link>
      <guid>https://stackers.network/projects/openstack-keystonemiddleware/2026-10-24</guid>
      <pubDate>Sat, 24 Oct 2026 00:00:00 +0000</pubDate>
      <description>Caching. The auth_token middleware gained an oslo.cache backend option, broadening the set of supported cache stores beyond the long-standing memcached path (979374). A follow-up reworks the cache encryption options to be generic rather than memcache-specific, so the new backend…</description>
      <content:encoded><![CDATA[<p><strong>Caching.</strong> The auth_token middleware gained an <strong>oslo.cache</strong> backend option, broadening the set of supported cache stores beyond the long-standing memcached path (<a href="https://review.opendev.org/c/openstack/keystonemiddleware/+/979374">979374</a>). A follow-up reworks the cache encryption options to be generic rather than memcache-specific, so the new backend can reuse the same key/encryption configuration surface.</p>
<p><strong>Tooling and lint.</strong> The bulk of the week's ~12k lines of churn is a sweeping adoption of <strong>pre-commit</strong>, which rewires formatting and lint enforcement across the tree. Layered on top, several patches turn on additional <strong>ruff</strong> rule groups (<code translate="no">G</code>, <code translate="no">LOG</code>, <code translate="no">UP</code>, plus previously ignored rules) and bring hacking under pre-commit, producing a lot of mechanical cleanup across the codebase.</p>
<p><strong>Fixes.</strong> A couple of small behavioral tweaks also landed: service entries in the generated catalog now carry an <code translate="no">id</code>, an outdated catalog-data comment was corrected, and unknown paste options are now logged at debug level instead of a louder severity to cut noise from legitimate deployer config.</p>]]></content:encoded>
    </item>
  </channel>
</rss>
