Skip to content

fix: restore main deploy workflows after auto-bump#63

Open
WellDunDun wants to merge 6 commits intomainfrom
custom/prefix/router-1773675884536-v1
Open

fix: restore main deploy workflows after auto-bump#63
WellDunDun wants to merge 6 commits intomainfrom
custom/prefix/router-1773675884536-v1

Conversation

@WellDunDun
Copy link
Collaborator

Removes [skip ci] from the auto-bump commit message in the CLI version workflow. Squash merges were carrying that marker into the resulting commit message and suppressing push workflows on main, including deploy/publish automation. The workflow now relies on GITHUB_TOKEN behavior for loop prevention and documents that inline in the script comment.

WellDunDun and others added 6 commits March 16, 2026 18:47
The workspace:* dependency on @selftune/telemetry-contract breaks
npm install because npm doesn't understand the workspace protocol.
Using file: instead works with both bun and npm since the package
is already bundled in the tarball via the files array.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…lure

The merge created a duplicate @selftune/telemetry-contract entry in
bun.lock (both workspace: and file: variants), which caused bun to
fail module resolution in CI.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@coderabbitai
Copy link

coderabbitai bot commented Mar 16, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: f3834c66-455e-4aca-812a-b873bd1de5f0

📥 Commits

Reviewing files that changed from the base of the PR and between cfb874e and 836fd35.

📒 Files selected for processing (1)
  • .github/workflows/auto-bump-cli-version.yml

📝 Walkthrough

Summary by CodeRabbit

  • Chores
    • Optimized the automated version bumping workflow to improve reliability when processing CLI version updates.

Walkthrough

The auto-bump-cli-version GitHub Actions workflow commit step was modified to remove the [skip ci] flag from the commit message. The commit now uses the message "chore: bump cli version to v${NEW_VERSION}". Explanatory comments were added noting that GITHUB_TOKEN pushes do not retrigger workflows and that [skip ci] can persist in squash-merge commit bodies.

Changes

Cohort / File(s) Summary
GitHub Actions Workflow
.github/workflows/auto-bump-cli-version.yml
Removed [skip ci] from git commit message and added explanatory comments about GitHub token behavior and squash-merge commit implications.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed Title uses conventional commits format (fix:) and accurately describes the main change: removing [skip ci] to restore deploy workflows.
Description check ✅ Passed Description clearly explains the problem (squash merges carrying [skip ci] suppressed main workflows) and the solution (removing the marker, relying on GITHUB_TOKEN behavior).
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch custom/prefix/router-1773675884536-v1
📝 Coding Plan
  • Generate coding plan for human review comments

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

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