Fix v4 build workflow

[nicktrn]

The branch check didn't quite work as expected so it's disabled now until we fix it.

Summary by CodeRabbit

• Chores
  • Streamlined the deployment pipeline by removing redundant workflow checks for improved efficiency and reliability.

[changeset-bot]

⚠️ No Changeset found

Latest commit: de511a5

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Walkthrough

The pull request modifies the GitHub Actions workflow by commenting out the check-branch job and removing its dependency from the build job. This change eliminates the previously implemented branch-checking logic that verified if a tag starting with re2-prod- was pushed from a non-main branch before proceeding with the build.

Changes

File	Change Summary
.github/workflows/publish-worker-re2.yml	Commented out the check-branch job and removed the needs: check-branch dependency from the build job

Sequence Diagram(s)

sequenceDiagram
    participant Repo as Repository
    participant Workflow as Workflow Runner
    participant Build as Build Job

    Repo->>Workflow: Trigger workflow on push/tag
    %% Previously: Workflow->>CheckBranch: Evaluate branch condition
    Workflow->>Build: Execute build job directly (branch check removed)

Loading

Poem

In the code garden, I hop with cheer,
Branch checks now skipped, nothing to fear.
My little paws tap a new-found beat,
With build jobs running smooth and neat.
A bunny’s joy in every commit so dear!
🐰🌸

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

.github/workflows/publish-worker-re2.yml (1)

21-28: Temporarily Disabled Branch Check Job

The check-branch job has been commented out as intended for this temporary fix. However, please add a descriptive TODO or comment clarifying the reason for its disablement (e.g., branch check failing) along with a plan to re-enable it once the appropriate fix is implemented.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 56a880f and de511a5.

📒 Files selected for processing (1)

• .github/workflows/publish-worker-re2.yml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (5)

• GitHub Check: e2e / 🧪 CLI v3 tests (windows-latest - pnpm)
• GitHub Check: e2e / 🧪 CLI v3 tests (windows-latest - npm)
• GitHub Check: typecheck / typecheck
• GitHub Check: units / 🧪 Unit Tests
• GitHub Check: Analyze (javascript-typescript)

🔇 Additional comments (1)

.github/workflows/publish-worker-re2.yml (1)

30-30: Disabled Dependency on Branch Check

The dependency (needs: check-branch) in the build job has been commented out in alignment with the temporary branch check removal. Ensure this removal does not inadvertently allow unexpected builds and that future re-introduction of the branch check job is coordinated with any dependent workflow changes.