Skip to content

Make the plugin gate run somewhere other than this laptop - #26

Merged
btsouth merged 1 commit into
mainfrom
ci/plugin-checks
Sep 20, 2026
Merged

btsouth merged 1 commit into
mainfrom
ci/plugin-checks

Conversation

@btsouth

@btsouth btsouth commented Sep 20, 2026

Copy link
Copy Markdown
Owner

The gate list I have been following includes omarchy plugin validate .. CI has never run it, because the command only exists on an Omarchy machine. That means the desktop side of this repo has had a check that runs when someone remembers to type it, which is the same as no check, and it is exactly the failure mode Phase 3 has been hunting: a green light that proves nothing.

bin/check-plugin.mjs is the portable part, now in CI:

  • no tracked symlinks, which the plugin loader refuses and which is the failure that stops an install
  • a manifest whose entry points exist on disk
  • the version numbers this repo has drifted apart before: manifest.json, website/package.json, and the newest tag when the checkout has tags (a shallow CI checkout has none, so that comparison skips rather than failing falsely)
  • QML lint when the machine has qmllint, skipped with a note when it does not

It passes on main: no tracked symlinks, 2 entry points resolve, version 1.5.0 matches the website package and the newest tag.

One thing found on the way, recorded rather than fixed: omarchy plugin validate also fails in the dev clone once website/node_modules exists, because it walks the folder and 44 of npm's .bin entries are symlinks. It passes with node_modules moved aside. Nothing is wrong with the repo, but the local gate goes red for a reason that has nothing to do with the plugin.

No product code changes.

The gate list I have been following includes `omarchy plugin validate .`, and CI has
never run it, because it only exists on an Omarchy machine. So the desktop side of
this repo has had a check that runs when someone remembers to type it, which is the
same as no check.

bin/check-plugin.mjs is the portable part of it, now in CI: no tracked symlinks (the
loader refuses them, and that is the failure that stops an install), a manifest whose
entry points exist on disk, and the version numbers this repo has drifted apart before
(manifest.json, website/package.json, and the newest tag when the checkout has tags).

qmllint runs when the machine has it and is skipped with a note when it does not, so
the same script is useful locally and harmless on a runner.

Found while checking this: `omarchy plugin validate` also fails in the dev clone once
`website/node_modules` exists, because it walks the folder and 44 of npm's .bin
entries are symlinks. It passes with node_modules aside. Nothing to fix in the repo,
but worth knowing before someone chases a red gate that is not real.
@coderabbitai

coderabbitai Bot commented Sep 20, 2026

Copy link
Copy Markdown

Important

  • 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: cce89ecb-07cf-4050-9c08-4cf37013db92


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

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

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Sep 20, 2026 •

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Preview URL Updated (UTC)
✅ Deployment successful!
View logs
typearchy abfc804 Commit Preview URL

Branch Preview URL
Sep 20 2026, 09:28 AM

@btsouth
btsouth merged commit 12fd0da into main Sep 20, 2026
3 checks passed
@btsouth
btsouth deleted the ci/plugin-checks branch September 20, 2026 09:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant