ci: fix publish

[LGLabGreg]

Summary by CodeRabbit

• Chores
  • Improved the component package’s publishing process by adding a build step before release, ensuring greater consistency and reliability in package delivery.

[coderabbitai]

Walkthrough

This pull request introduces a patch for the package @lglab/react-qr-code. It updates the CI publishing process by modifying the "ci:publish" script in package.json to run a build step (pnpm build:lib) prior to executing the publishing (pnpm publish -r) and changeset tagging (pnpm changeset tag) commands. No changes were made to the declarations of any exported or public entities.

Changes

File(s)	Change Summary
.changeset/eleven-lobsters-pretend.md	Added AI-generated summary for the patch to @lglab/react-qr-code's publishing process; no public API alterations.
package.json	Modified the "ci:publish" script to include a build step ("pnpm build:lib") before the publish and changeset tagging commands.

Sequence Diagram(s)

sequenceDiagram
    participant CI as CI Pipeline
    participant Build as Build Process
    participant Publish as Publishing Command
    participant Tag as Changeset Tagger

    CI->>Build: Execute pnpm build:lib
    Build-->>CI: Build successful
    CI->>Publish: Execute pnpm publish -r
    Publish-->>CI: Publishing complete
    CI->>Tag: Execute pnpm changeset tag
    Tag-->>CI: Tag created

Loading

Possibly related PRs

• ci: use secrets npm token vs creating npmrc #48: Addresses enhancements in the package's publishing workflow, closely relating to the build step integration in this PR.

Poem

I'm a rabbit, quick on my feet,
Hopping through code with a rhythmic beat,
Build before publish, my new happy tune,
Changes so clear like a bright full moon,
Celebrating with hops and a joyful cheer 🐇✨!

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 185ad08 and d387fa7.

📒 Files selected for processing (2)

• .changeset/eleven-lobsters-pretend.md (1 hunks)
• package.json (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• .changeset/eleven-lobsters-pretend.md

🔇 Additional comments (1)

package.json (1)

16-16: Integrating Build Step into CI Publish Process

The updated "ci:publish" command now includes the "pnpm build:lib" step before publishing and tagging changesets. This ensures that the library is built and up-to-date prior to the publishing process, which helps prevent deployment issues related to outdated artifacts.

---

🪧 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. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @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.