Skip to content

fix: split CI into test + tag-triggered publish - #8

Merged
royosherove merged 1 commit into
mainfrom
fix/ci-publish-workflow
May 7, 2026
Merged

fix: split CI into test + tag-triggered publish#8
royosherove merged 1 commit into
mainfrom
fix/ci-publish-workflow

Conversation

@royosherove

Copy link
Copy Markdown
Member

- Test workflow: runs on push to main + PRs
- Publish workflow: only on v* tags (no auto-bump)
- Fixes branch protection conflict in CI
@royosherove
royosherove merged commit 8b4834d into main May 7, 2026
@royosherove
royosherove deleted the fix/ci-publish-workflow branch May 7, 2026 19:39

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c513418538

ℹ️ 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".

on:
push:
branches: [main]
tags: ["v*"]

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Restrict tag-triggered publish to commits on main

This workflow now publishes on any v* tag push, but it no longer enforces that the tagged commit is on main. In practice, any collaborator who can push tags can publish a package from an arbitrary or stale commit (for example, a feature branch commit that never passed the protected main merge path), which can ship unreviewed code to npm. Add a guard before npm publish (or an if condition) that verifies the tag SHA is reachable from origin/main.

Useful? React with 👍 / 👎.

royosherove added a commit that referenced this pull request May 8, 2026
#5 — Suppress npm deprecation spam:
  - Set NODE_NO_WARNINGS=1 when spawning gateway subprocess
  - All install commands already use stdio:'pipe' (hide npm stderr)

#6 — Whisper/STT setup improvements:
  - Default voice=false on macOS (whisper pip install is heavy)
  - Add whisper check in postflight with install hint
  - Linux keeps voice=true (auto-install on first message)

#8 — Simplify getting started:
  - 'roundhouse install' now deprecated with redirect to setup
  - Removed 60+ lines of redundant install logic from cli.ts
  - README Quick Start: 3 lines (npm install, setup, start)
  - Cleaned up unused imports (mkdir, writeFile, envQuote, etc.)

Co-authored-by: Loki FastStart <loki@faststart.internal>
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