Promote dev to main#22
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 2ac35f3d7f
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| <!ENTITY pluginURL "https://raw.githubusercontent.com/&github;/main/folderview.plus.plg"> | ||
| <!ENTITY version "2026.03.25.04"> | ||
| <!ENTITY md5 "4fbaa276a494052e78c686ff2f44a694"> | ||
| <!ENTITY pluginURL "https://raw.githubusercontent.com/&github;/dev/folderview.plus.plg"> |
There was a problem hiding this comment.
Point stable manifest back to main channel URLs
This commit promotes dev into main, but the manifest now hard-codes the dev branch for update/download URLs. On main, this makes stable installs fetch packages from dev (including the archive URL later in the same file), and it also causes scripts/release_guard.sh to fail whenever FVPLUS_EXPECT_PLUGIN_BRANCH/GITHUB_REF_NAME resolves to main (the CI/release-on-main path). Please keep main manifests on main URLs and reserve dev URLs for dev-branch artifacts only.
Useful? React with 👍 / 👎.
Summary
Validation
ode --test tests/versioning-guard.test.mjs
Notes