<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>openstack/mistral — Stackers Network</title>
    <link>https://stackers.network/projects/openstack-mistral/</link>
    <description>Weekly code-activity digest for openstack/mistral from Stackers Network.</description>
    <item>
      <title>openstack/mistral — Week of 2026-06-13</title>
      <link>https://stackers.network/projects/openstack-mistral/2026-06-13</link>
      <guid>https://stackers.network/projects/openstack-mistral/2026-06-13</guid>
      <pubDate>Sat, 13 Jun 2026 00:00:00 +0000</pubDate>
      <description>Publicize policy sweep. The bulk of the week landed a coordinated set of policies governing which resources can be marked public, with new publicize policies and enforcement added for workbooks, environments, cron_triggers, code_sources, and dynamic_actions. Alongside the new…</description>
      <content:encoded><![CDATA[<p><strong>Publicize policy sweep.</strong> The bulk of the week landed a coordinated set of policies governing which resources can be marked public, with new <code translate="no">publicize</code> policies and enforcement added for workbooks, environments, cron_triggers, code_sources, and dynamic_actions. Alongside the new policies, the existing publicize behavior was tightened so that those actions — plus <code translate="no">code_sources</code> and <code translate="no">dynamic_actions</code> management — are restricted to admin only. A small cleanup removed unnecessary <code translate="no">expect_errors=True</code> from the policy test suite.</p>
<p><strong>API reference.</strong> A ~2,600-line drop added API reference documentation covering all Mistral v2 resources (<a href="https://review.opendev.org/c/openstack/mistral/+/981192">981192</a>), filling a long-standing gap in the published docs.</p>
<p><strong>Bug fixes.</strong> A failure in the keystone client when using trust-scoped tokens was fixed, and a piece of dead <code translate="no">management_url</code> code was removed.</p>
<p><strong>Stable and CI.</strong> CI for <code translate="no">unmaintained/2024.1</code> was restored, and a stable-only patch excludes a test case tied to bug #2147178.</p>]]></content:encoded>
    </item>
    <item>
      <title>openstack/mistral — Week of 2026-06-06</title>
      <link>https://stackers.network/projects/openstack-mistral/2026-06-06</link>
      <guid>https://stackers.network/projects/openstack-mistral/2026-06-06</guid>
      <pubDate>Sat, 06 Jun 2026 00:00:00 +0000</pubDate>
      <description>Publicize policy overhaul. The week is almost entirely one coordinated effort: introducing publicize policies and enforcement across Mistral's cross-tenant-shareable resources, and locking the relevant policies down to admin by default. New publicize policy + enforcement landed…</description>
      <content:encoded><![CDATA[<p><strong>Publicize policy overhaul.</strong> The week is almost entirely one coordinated effort: introducing <code translate="no">publicize</code> policies and enforcement across Mistral's cross-tenant-shareable resources, and locking the relevant policies down to admin by default. New <code translate="no">publicize</code> policy + enforcement landed for workbooks, environments, <code translate="no">cron_triggers</code>, <code translate="no">code_sources</code>, and <code translate="no">dynamic_actions</code>, and the existing publicize paths were restricted to admin-only. A companion change also restricts the <code translate="no">code_sources</code> and <code translate="no">dynamic_actions</code> policies themselves to admins. Each patch was carried across master plus three stable backport branches, accounting for most of the ~7,100 lines of churn. See <a href="https://review.opendev.org/c/openstack/mistral/+/991421">the workbooks policy addition</a> as the representative change.</p>
<p><strong>Hardening.</strong> A separate fix <a href="https://review.opendev.org/c/openstack/mistral/+/991391">strips sensitive information from the workflow execution context</a> so it no longer leaks through execution data, also backported across the supported branches. Policy tests were tidied to drop unnecessary <code translate="no">expect_errors=True</code> usage now that the new enforcement returns proper status codes.</p>
<p><strong>Tooling and CI.</strong> A small change disables currently failing jobs to unstick the gate.</p>]]></content:encoded>
    </item>
  </channel>
</rss>
