Repository navigation
feat(versioning): remove Stale tag when a new feature version is published - #8964
TejasLamba2006 wants to merge 1 commit into
Conversation
…is published Disconnect any TagType.STALE tag from the feature when environment_feature_version_published fires, leaving user tags and other system tags untouched.
|
@TejasLamba2006 is attempting to deploy a commit to the Flagsmith Team on Vercel. A member of the Team first needs to authorize it. |
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
 |
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
No issues found across 2 files
Confidence score: 5/5
- Automated review surfaced no issues in the provided summaries.
- No files require special attention.
Requires human review: Auto-approval skipped because this PR is from an external contributor.
View guided diff | Re-trigger cubic
Contributes to #8705.
Changes
remove_stale_tagreceiver toenvironment_feature_version_publishedinapi/features/versioning/receivers.pyso publishing a newEnvironmentFeatureVersion(direct saves, scheduled changes, and change requests) removes anyTagType.STALEtag from the feature while keeping user tags and other system tags (UNHEALTHY, etc.) intact.api/tests/unit/features/versioning/test_unit_versioning_receivers.py.(Note: the background staleness tagging task itself lives outside the OSS repository, so this PR covers the tag-removal side on feature modification.)