Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(breaking change) Remove support of GO Feature Flag v0.x.x flag format #2398

Open
thomaspoignant opened this issue Sep 20, 2024 · 2 comments
Assignees
Labels
📍 Assigned breaking change p2 Medium priority 📌 Pinned stop v0 support Tag to group everything about the un-support of v0.x.x flag format

Comments

@thomaspoignant
Copy link
Owner

thomaspoignant commented Sep 20, 2024

Context

In version v1.0.0 GO Feature Flag has dropped the legacy format of the flag of the v0.0.0 in order to move to a multi-variations format that has enable new features for GO Feature Flag.

To avoid any breaking changes we have kept the compatibility with the v0.x.x and continue to support it.

The last release of version v0.x.x was 12 December 2022 (v0.28.2) and since then we have released more than 34 versions of GO Feature Flag v1.x.x it is now time to clean the code and remove any trace of the v0.x.x format.

In this issue we will link all the associated issues of this project to be able to track the progress of this initiative.

You are still using the legacy format?

If you are still using the legacy format you can easily convert your file containing GO Feature Flag flags with the migration cli.

How to do that? Just follow the instruction in our documentation.

List of issues to complete to consider this one done

All those issues have to be executed in the order of this list.

  1. Log error when v0.x.x flag format is used #2399
  2. Stop releasing migration cli #2400
  3. Change all tests using v0.x.x flag format #2401
  4. Remove migration cli code #2402
  5. Refactor DTO layer to support v1 flag format only #2403
@thomaspoignant
Copy link
Owner Author

/assign-me

Copy link
Contributor

👋 Hey @thomaspoignant, thanks for your interest in this issue! 🎉

⚠ Note that this issue will become unassigned if it isn't closed within 10 days.

🔧 A maintainer can also add the 📌 Pinned label to prevent it from being unassigned automatically.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
📍 Assigned breaking change p2 Medium priority 📌 Pinned stop v0 support Tag to group everything about the un-support of v0.x.x flag format
Projects
None yet
Development

No branches or pull requests

1 participant