Revert "docs: publish customer release notes (#37)" - #38
Merged
Conversation
charitra-prem
approved these changes
Aug 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Reverts #37 (commit 15ba3ad).
#37 was merged by mistake. It adds the customer-facing v1.5.0 release-notes entry to
release-notes.mdx, and that entry is not meant to go out yet.Nothing else is affected: the entry never reached docs.fluso.ai, because the
deploy to Mintlifyworkflow fails on missingMINTLIFY_API_KEY/MINTLIFY_PROJECT_IDsecrets and the live site is triggered from the Mintlify side. So this revert restoresmainbefore anything was published.The GitHub releases
prod-v1.5.0on premapp-backend and fluso-frontend stay as they are — this only touches the docs entry.