fix(LD Importer): Archive deprecated LaunchDarkly flags on import

[emyller]

Import deprecated flags from LaunchDarkly as archived features in Flagsmith.

Changes

• Archive deprecated flags on import.
• Removed white text from "importing" overlay — it was very hard to read, and not useful.

I was also very annoyed that there is no user feedback after importing, and came to an improvement I like:

or

---

Closes #5642

Review effort: 2/5

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview, Comment	Feb 17, 2026 3:17pm

2 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
flagsmith-frontend-preview	Ignored	Preview	Feb 17, 2026 3:17pm
flagsmith-frontend-staging	Ignored	Preview	Feb 17, 2026 3:17pm

[github-actions]

Docker builds report

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.23%. Comparing base (cf16f3d) to head (e5ab999).
⚠️ Report is 27 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #6447      +/-   ##
==========================================
+ Coverage   98.22%   98.23%   +0.01%     
==========================================
  Files        1313     1311       -2     
  Lines       47481    48479     +998     
==========================================
+ Hits        46636    47622     +986     
- Misses        845      857      +12     

☔ 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.

[khvn26]

LGTM!

[Zaimwa9]

Looks good. I have one comment about the expiry that can lead to some a bit annoying UX.
And just putting it on the radar. I wouldn't do it in this PR and it doesn't look very prio but because the archived flag relies on a boolean flag (and not a tag as the other). We can not filter on deprecated alone.

We need to filter on both archived (to have the boolean) and deprecated to see them

[emyller]

We need to filter on both archived (to have the boolean) and deprecated to see them

Great catch. I'd say this PR introduces poor UX without this addressed, or at least documented as a new issue. However, I don't see a good solution to be coupling the Deprecated tag and archived state together... Maybe the tag filter should include features regardless of their "archived" state if that makes sense. Let's discuss internally.

[cursor]

You have run out of free Bugbot PR reviews for this billing cycle. This will reset on March 10.

To receive reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

[emyller]

We need to filter on both archived (to have the boolean) and deprecated to see them

Great catch. I'd say this PR introduces poor UX without this addressed, or at least documented as a new issue. However, I don't see a good solution to be coupling the Deprecated tag and archived state together... Maybe the tag filter should include features regardless of their "archived" state if that makes sense. Let's discuss internally.

I've decided to remove the newly introduced "Deprecated" tag entirely, see e5ab999. Although it looks helpful upfront, it also creates an UX problem we don't need IMO.

[Zaimwa9]

👍 Thanks. Good call I think for now to keep both of them archived. Hopefully it's sufficient for customers