Skip to content

Conversation

@JounQin
Copy link
Member

@JounQin JounQin commented Sep 1, 2025

Important

Add a Build step to the CI workflow in release.yml to run npm run build unconditionally before publishing.

  • CI Workflow:
    • Adds a Build step in .github/workflows/release.yml to run npm run build unconditionally before publishing to npm.

This description was created by Ellipsis for 6ae7af5. You can customize this summary. It will automatically update as commits are pushed.

Summary by CodeRabbit

  • Chores

    • Updated release workflow to always run a build before publishing, improving the reliability and consistency of released packages.
    • Added release metadata to track this process adjustment and ensure correct versioning.
  • Bug Fixes

    • Ensures build steps run unconditionally during releases, reducing the risk of incomplete or broken publishes.

@JounQin JounQin self-assigned this Sep 1, 2025
@JounQin JounQin added the bug Something isn't working label Sep 1, 2025
@changeset-bot
Copy link

changeset-bot bot commented Sep 1, 2025

🦋 Changeset detected

Latest commit: 715f644

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@dual-bundle/import-meta-resolve Patch

Not sure what this means? Click here to learn what changesets are.

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

@coderabbitai
Copy link

coderabbitai bot commented Sep 1, 2025

Caution

Review failed

The pull request is closed.

Walkthrough

Adds a new changeset for a patch release message and updates the release GitHub Actions workflow to always run a build by inserting an explicit “npm run build” step between dependency installation and publishing. No source code or public API changes.

Changes

Cohort / File(s) Summary
Release metadata
./.changeset/fresh-houses-listen.md
Adds changeset marking a patch for @dual-bundle/import-meta-resolve: “fix: run build on CI unconditionally”.
CI workflow: release
.github/workflows/release.yml
Inserts a Build step (npm run build) after Install Dependencies and before Publish to npm.

Sequence Diagram(s)

sequenceDiagram
  autonumber
  actor Dev as Developer
  participant GH as GitHub Actions (release.yml)
  participant NPM as npm Registry

  Dev->>GH: Push tag / trigger release workflow
  GH->>GH: Checkout code
  GH->>GH: Setup Node & install dependencies
  note over GH: New step
  GH->>GH: Run build (npm run build)
  GH->>NPM: Publish package
  NPM-->>GH: Publish result
Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

I hopped through pipelines swift and bright,
A build now runs in morning light.
With tags that twinkle, steps align,
We pack the bundle, right on time.
Thump-thump! to npm’s moonlit door—
Patch released, and hop once more. 🐇✨


📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 03f703e and 715f644.

📒 Files selected for processing (2)
  • .changeset/fresh-houses-listen.md (1 hunks)
  • .github/workflows/release.yml (1 hunks)
✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch fix/build

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
🪧 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.
    • 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.
  • 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

  • Add @coderabbitai ignore or @coderabbit 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

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • 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.

Signed-off-by: JounQin <admin@1stg.me>
Copy link

@ellipsis-dev ellipsis-dev bot left a comment

Choose a reason for hiding this comment

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

Important

Looks good to me! 👍

Reviewed everything up to 6ae7af5 in 17 seconds. Click for details.
  • Reviewed 14 lines of code in 1 files
  • Skipped 0 files when reviewing.
  • Skipped posting 1 draft comments. View those below.
  • Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.
1. .github/workflows/release.yml:32
  • Draft comment:
    Unconditionally running the build step looks correct for releasing. Ensure the build output is as expected for your publish step.
  • Reason this comment was not posted:
    Confidence changes required: 0% <= threshold 50% None

Workflow ID: wflow_pZWQzUUHHZjX6Bpc

You can customize Ellipsis by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.

@JounQin JounQin merged commit febc67e into fork-release Sep 1, 2025
10 checks passed
@JounQin JounQin deleted the fix/build branch September 1, 2025 04:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants