gh pr merge --auto requires branch protection with required status
checks on the target branch. firecrawl-claude-plugin and
firecrawl-cursor-plugin don't have that configured, so the workflows
fail with "Protected branch rules not configured for this branch
(enablePullRequestAutoMerge)" after successfully creating the PR.
There's nothing to wait for on a sync PR anyway, so drop --auto and
merge immediately.
Instead of auto-bumping on every skill change, the workflow now only
triggers when plugin.json version is explicitly changed. The CLI repo
is the source of truth for versioning.
- Add sync-plugin.yml workflow that triggers on changes to skills/ or
.claude-plugin/ on main, copies files to firecrawl-claude-plugin,
bumps the patch version, and opens a PR
- Update plugin.json version to 1.0.3 to match the plugin repo
Developers Digest