feat: Release Pipeline Publish and Add Flag

[tiagoapolo]

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

Ref: #5301
#5275

Implements:

• Publishing release pipeline, changes release pipeline from draft to published
• Adding a feature flag to published pipeline

How did you test this code?

⚠️ Tested using branch containing backend and frontend release-pipe-publish-back-front

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
flagsmith-frontend-preview	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 25, 2025 2:31pm
flagsmith-frontend-staging	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 25, 2025 2:31pm

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
docs	⬜️ Ignored (Inspect)	Visit Preview		Jun 25, 2025 2:31pm

[github-actions]

Docker builds report

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

[Zaimwa9]

Almost good to go, 2 things to solve before ✅ :

• The update of a stage removing the following stages
• The catch on getReleasePipelines

We can create a ticket to properly deal with enterprise

[Zaimwa9]

Sorry, I'm adding here some comments about something I didn't notice => Non-enteprise orgs.

• The release pipelines nav item is available (I would personally disable it and adding a tooltip to warn it's for enterprise but tbd with product)
• You have access to the whole flow and only get the error at the end
• The failure message is success and not error

[Zaimwa9]

It might be out of this PR scope so maybe we can create a ticket specifically to address the non available state of this feature

[Zaimwa9]

So we have this in the organisation payload:

{
  "id": 2,
  "has_active_billing_periods": true,
  "deleted_at": null,
  "uuid": "xxxx",
  "subscription_id": "123",
  "subscription_date": null,
  "plan": "enterprise",
  "max_seats": 400,
  "max_api_calls": 50000,
  "cancellation_date": null,
  "customer_id": null,
  "billing_status": null,
  "payment_method": null,
  "notes": null
}

In the context of release, the backend definition of enterprise is:
!!subscription_id && !is_cancellation_date && plan === 'enterprise, to see if it exactly matches the frontend one

[tiagoapolo]

This can be handled in a separate ticket

[Zaimwa9]

Re-opening as this one hasn't been resolved

https://www.loom.com/share/81069cfa500747b19e88aef5c5dbf753

[Zaimwa9]

👍