Skip to content

v9.17.0 - segment targeting reaches the remaining policy planes

Choose a tag to compare

View all tags
@saurabhjain1592 saurabhjain1592 released this 12 Aug 12:54
v9.17.0
c210a36
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

This release completes the segment-scoped policy rollout that began in v9.14.0. Those notes introduced segment targeting for static policies on the governed request plane and named the planes deliberately left out of scope; this release closes that list, so a segment-scoped policy is honoured wherever a caller identity is validated rather than on the request plane alone.

For the Community edition:

  • The fleet / MCP-server, gateway check and OpenAI-compatible planes now apply the same segment gate through the shared policy engine.
  • Strictly additive: a policy with no segment behaves exactly as it always has, and no policy decision changes anywhere until a segment-scoped policy is authored.
  • Segment resolution has no resolver on the Community edition, so the capability is inert there. The schema carries the column on both editions so it does not fork.

Migration: one additive migration (core/159) adds a nullable segment_id column plus a partial index to dynamic_policies, using IF NOT EXISTS on both. It rewrites no data and is safe to re-run.

The customer-portal password-recovery work in this release is part of the Enterprise edition.

Full release notes: https://docs.getaxonflow.com/docs/releases/v9-17-0

Assets 2
Loading