Repository navigation
fix(comparisons): stop recommending Flowise after its end of life and source its facts from Flowise - #9239
Merged
Conversation
… source its facts from Flowise
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
Contributor
[Medium impact] The PR appears safe to merge. SummaryAdds a profile-specific verdict so Flowise is recommended only for existing teams prepared to maintain a fork.
No actionable issues found. Reviews (1) · Last reviewed commit: "fix(comparisons): stop recommending Flow..." · Reviewed by Greptile |
This branch was previously deployed
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
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.
Summary
chooseCompetitorAnswerprofile field that replaces the generated verdict, and sets it for Flowise: choose it only if you already run it and will maintain a forkdateModified, and sitemap date to 2026-10-19;getLatestVerifiedDateonly reads fact-source dates, so the earlier prose-only update never reached themType of Change
Testing
buildBottomLine,buildComparisonFaqs, and the latest-verified date for all 20 competitors before and after: only Flowise changed (verdict, limitation FAQs, date 2026-10-15 → 2026-10-19); Sim's verdict is byte-identicalnpm view flowise, and the GitHub repositorycheck:source-conventions,check:comment-hygiene,check:unused-exports,check:site-urlsChecklist
test-auditauthoring gate)