Skip to content

Conversation

jjw24
Copy link
Member

@jjw24 jjw24 commented Sep 3, 2025

For v2.0.0 flow, we switch the manifest file plugins.json back to the main branch. This is due to .NET 9 upgrade, we need to prevent older flow versions from updating to plugins in this release. Default plugins are now on .NET 9 and will not work with older versions.

Follows on from #3286

@github-actions github-actions bot added this to the 2.0.0 milestone Sep 3, 2025
@jjw24 jjw24 added the enhancement New feature or request label Sep 3, 2025
Copy link

gitstream-cm bot commented Sep 3, 2025

🥷 Code experts: Jack251970, taooceros

Jack251970 has most 👩‍💻 activity in the files.
taooceros, Jack251970 have most 🧠 knowledge in the files.

See details

Flow.Launcher.Core/ExternalPlugins/PluginsManifest.cs

Activity based on git-commit:

Jack251970
SEP
AUG
JUL 5 additions & 1 deletions
JUN
MAY
APR 10 additions & 7 deletions

Knowledge based on git-blame:
taooceros: 32%
Jack251970: 21%

✨ Comment /gs review for LinearB AI review. Learn how to automate it here.

Copy link

gitstream-cm bot commented Sep 3, 2025

Be a legend 🏆 by adding a before and after screenshot of the changes you made, especially if they are around UI/UX.

@coderabbitai coderabbitai bot added the bug Something isn't working label Sep 3, 2025
@jjw24 jjw24 removed the bug Something isn't working label Sep 3, 2025
Copy link
Contributor

coderabbitai bot commented Sep 3, 2025

📝 Walkthrough

Walkthrough

Updated plugin manifest source URLs in PluginsManifest initialization from the plugin_api_v2 branch to the main branch. No logic changes to fetching, filtering, caching, or synchronization.

Changes

Cohort / File(s) Summary of changes
Manifest source URLs
Flow.Launcher.Core/ExternalPlugins/PluginsManifest.cs
Repointed 4 manifest URLs from plugin_api_v2 to main (raw GitHub and CDN endpoints). No changes to timing, locking, version filtering, or caching logic.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

Suggested labels

bug

Suggested reviewers

  • taooceros
  • Jack251970
  • Garulf
✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch point_pluginsmanifest_to_main

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

  • Add @coderabbitai ignore or @coderabbit ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
Flow.Launcher.Core/ExternalPlugins/PluginsManifest.cs (1)

74-77: Enforce MinimumAppVersion ≥ 2.0.0 for all plugins in main/plugins.json
20 plugins are missing MinimumAppVersion (Google Search Plus, Plugin Runner, Dictionary, SpotifyPremium, ClipboardHistory, Window Walker, Everything, Colors, Currency Converter, IP Address, Flow.Plugin.UrlEncode, Putty, LibreTranslate, Todoist, Todos, Direct Translate, GitHub, isPrime, RollDice, Fancy Emoji). Without these fields, older Flow releases will install .NET 9 plugins and fail at runtime. Add "MinimumAppVersion": "2.0.0" to each entry in main/plugins.json.

🧹 Nitpick comments (1)
Flow.Launcher.Core/ExternalPlugins/PluginsManifest.cs (1)

15-19: Factor branch/repo into constants to avoid multi-point edits next time.

Prevents future churn if the branch changes again; also improves readability.

Apply this diff:

-        private static readonly CommunityPluginStore mainPluginStore =
-            new("https://raw.githubusercontent.com/Flow-Launcher/Flow.Launcher.PluginsManifest/main/plugins.json",
-                "https://fastly.jsdelivr.net/gh/Flow-Launcher/Flow.Launcher.PluginsManifest@main/plugins.json",
-                "https://gcore.jsdelivr.net/gh/Flow-Launcher/Flow.Launcher.PluginsManifest@main/plugins.json",
-                "https://cdn.jsdelivr.net/gh/Flow-Launcher/Flow.Launcher.PluginsManifest@main/plugins.json");
+        private const string ManifestBranch = "main";
+        private const string ManifestRepo = "Flow-Launcher/Flow.Launcher.PluginsManifest";
+        private static readonly CommunityPluginStore mainPluginStore =
+            new($"https://raw.githubusercontent.com/{ManifestRepo}/{ManifestBranch}/plugins.json",
+                $"https://fastly.jsdelivr.net/gh/{ManifestRepo}@{ManifestBranch}/plugins.json",
+                $"https://gcore.jsdelivr.net/gh/{ManifestRepo}@{ManifestBranch}/plugins.json",
+                $"https://cdn.jsdelivr.net/gh/{ManifestRepo}@{ManifestBranch}/plugins.json");
📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 09366f5 and ffb7c25.

📒 Files selected for processing (1)
  • Flow.Launcher.Core/ExternalPlugins/PluginsManifest.cs (1 hunks)
🧰 Additional context used
🧠 Learnings (2)
📚 Learning: 2025-07-06T12:21:37.947Z
Learnt from: Jack251970
PR: Flow-Launcher/Flow.Launcher#3572
File: Flow.Launcher/App.xaml.cs:214-216
Timestamp: 2025-07-06T12:21:37.947Z
Learning: In Flow Launcher, the UpdatePluginManifestAsync method in PluginsManifest.cs already has comprehensive internal try-catch handling that logs exceptions and returns false on failure rather than throwing, making external try-catch wrappers unnecessary.

Applied to files:

  • Flow.Launcher.Core/ExternalPlugins/PluginsManifest.cs
📚 Learning: 2025-07-01T05:46:13.251Z
Learnt from: Jack251970
PR: Flow-Launcher/Flow.Launcher#3791
File: Flow.Launcher.Core/Plugin/PluginManager.cs:293-295
Timestamp: 2025-07-01T05:46:13.251Z
Learning: In Flow.Launcher.Core/Plugin/PluginManager.cs, when checking if a plugin is modified within the PluginManager class itself, prefer using the internal static PluginModified(string id) method directly rather than going through API.PluginModified() for better performance and architectural design.

Applied to files:

  • Flow.Launcher.Core/ExternalPlugins/PluginsManifest.cs
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
  • GitHub Check: gitStream.cm
  • GitHub Check: build
🔇 Additional comments (1)
Flow.Launcher.Core/ExternalPlugins/PluginsManifest.cs (1)

16-19: URLs switched to main — LGTM.

This aligns with the v2.0.0/.NET 9 rollout intent and keeps CDN fallbacks intact.

@VictoriousRaptor VictoriousRaptor merged commit 8ec5026 into dev Sep 4, 2025
20 checks passed
@VictoriousRaptor VictoriousRaptor deleted the point_pluginsmanifest_to_main branch September 4, 2025 00:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants