Skip to content

chore: restrict npm publish to main releases and remove slim clonedeps cache - #1

Merged
mrzturn merged 4 commits into
mainfrom
dev
Sep 6, 2026
Merged

mrzturn merged 4 commits into
mainfrom
dev

Conversation

@mrzturn

@mrzturn mrzturn commented Sep 6, 2026

Copy link
Copy Markdown
Owner

Summary

  1. Guard the publish workflow so only releases cut from main trigger npm publish; releases from dev are skipped (dev pushes were never triggering).
  2. Remove the oh-my-opencode-slim clonedeps cache (.slim/), the tracked manifest, and its ignore-file entries — dev-only reference material, unused at build/publish time.

Verification

  • YAML parses correctly (jobs.publish.if = github.event.release.target_commitish == 'main')
  • No source/build changes; plugin behavior untouched

1. Add target_commitish == 'main' guard to the publish job so releases cut from dev are skipped
2. Dev-branch pushes remain non-triggering (workflow only listens to release published)
1. Delete .slim/ cloned opencode repo and clonedeps.json manifest (dev-only reference, unused at build time)
2. Drop the matching .gitignore block and the now-empty .ignore
1. Add CI workflow (typecheck, unit tests, build) with a build gate that fails on any warning or error output
2. Add CODEOWNERS mapping all paths to the repository owner for review enforcement
@mrzturn mrzturn self-assigned this Sep 6, 2026
@mrzturn

mrzturn commented Sep 6, 2026

Copy link
Copy Markdown
Owner Author

ok

1 similar comment
@mrzturn

mrzturn commented Sep 6, 2026

Copy link
Copy Markdown
Owner Author

ok

@mrzturn
mrzturn merged commit bb68e8a into main Sep 6, 2026
3 checks passed
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