feat: phased rollout

[gagantrivedi]

Thanks for submitting a PR! Please check the boxes below:

• I have added information to docs/ if required so people know about the feature!
• I have filled in the "Changes" section below?
• I have filled in the "How did you test this code" section below?
• I have used a Conventional Commit title for this Pull Request

Changes

Add database models required by release-pipeline-logic to implement phased rollout

How did you test this code?

Covered by unit tests

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

3 Skipped Deployments

Project	Deployment	Preview	Comments	Updated (UTC)
docs	⬜️ Ignored	Preview		Aug 13, 2025 11:15am
flagsmith-frontend-preview	⬜️ Ignored	Preview		Aug 13, 2025 11:15am
flagsmith-frontend-staging	⬜️ Ignored	Preview		Aug 13, 2025 11:15am

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 97.84%. Comparing base (c533d95) to head (f68303c).
⚠️ Report is 6 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #5890      +/-   ##
==========================================
+ Coverage   97.83%   97.84%   +0.01%     
==========================================
  Files        1258     1261       +3     
  Lines       44630    44883     +253     
==========================================
+ Hits        43664    43917     +253     
  Misses        966      966              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Copilot]

Pull Request Overview

This PR introduces a phased rollout feature for release pipelines, enabling gradual feature deployment through system segments with automated split percentage increases.

• Adds system segments that are hidden from regular API operations and skip audit logging
• Implements PhasedRolloutState model for managing gradual rollout progression
• Introduces new pipeline stage action type for phased rollouts with automated split increases

Reviewed Changes

Copilot reviewed 13 out of 13 changed files in this pull request and generated 4 comments.

Show a summary per file

File	Description
api/segments/models.py	Adds is_system_segment field and audit log skipping logic
api/segments/views.py	Filters out system segments from API responses
api/features/release_pipelines/core/models.py	Implements PhasedRolloutState model and phased rollout stage action
api/features/versioning/models.py	Links feature versions to phased rollout states
Various test files	Comprehensive test coverage for new functionality
Migration files	Database schema changes for new fields and models

[github-actions]

Docker builds report

Image	Build Status	Security report
ghcr.io/flagsmith/flagsmith-e2e:pr-5890	Finished ✅	Skipped
ghcr.io/flagsmith/flagsmith-api-test:pr-5890	Finished ✅	Skipped
ghcr.io/flagsmith/flagsmith-frontend:pr-5890	Finished ✅	Results ✅
ghcr.io/flagsmith/flagsmith-api:pr-5890	Finished ✅	Results ✅
ghcr.io/flagsmith/flagsmith:pr-5890	Finished ✅	Results ✅
ghcr.io/flagsmith/flagsmith-private-cloud:pr-5890	Finished ✅	Results ✅

[Zaimwa9]

Kudos for the thorough test cases.
2 comments:

• To me we have a One-one relationship EFV <> rollout_state no? it would make sense the DB follows
• A default timezone not at the right place

[Zaimwa9]

👍