chore: add lock file for ci

[HoikanChan]

Summary by CodeRabbit

• Chores
  • Updated the deployment process configuration to enhance the continuous release workflow.
  • Modified dependency management settings to now track the lockfile for improved consistency.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 98c7ddf

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 changes update the continuous-release job in the CI workflow and adjust Git tracking. In the CI workflow, the --compact flag has been removed from the publish command in the "Release" step. In the repository’s .gitignore, the entry for pnpm-lock.yaml has been deleted, allowing this file to be tracked by Git.

Changes

File	Change Summary
.github/workflows/ci.yml	Removed the --compact flag from the pnpx pkg-pr-new publish command in the Release step.
.gitignore	Deleted the pnpm-lock.yaml line, so the file will now be tracked by Git.

Sequence Diagram(s)

sequenceDiagram
    participant Runner as CI Runner
    participant Job as Continuous Release Job
    participant Step as Release Step
    Runner->>Job: Trigger continuous-release job
    Job->>Step: Execute "Release" step
    Step->>Job: Run publish command (without --compact)
    Job-->>Runner: Return job status

Loading

Poem

I'm a rabbit with hops so swift,
Watching CI jobs give our code a lift.
The --compact flag hopped out of sight,
While Git now tracks pnpm-lock.yaml right.
With joyful code and a bouncy beat,
I celebrate these changes, oh so sweet! 🐰

Tip

⚡🧪 Multi-step agentic review comment chat (experimental)

• We're introducing multi-step agentic chat in review comments. This experimental feature enhances review discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments.
  - To enable this feature, set early_access to true under in the settings.

---

🪧 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 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.

[pkg-pr-new]

Open in Stackblitz

create-inula

npm i https://pkg.pr.new/openInula/inula/create-inula@13

openinula

npm i https://pkg.pr.new/openInula/inula/openinula@13

inula-dev-tools

npm i https://pkg.pr.new/openInula/inula/inula-dev-tools@13

inula-intl

npm i https://pkg.pr.new/openInula/inula/inula-intl@13

inula-cli

npm i https://pkg.pr.new/openInula/inula/inula-cli@13

inula-request

npm i https://pkg.pr.new/openInula/inula/inula-request@13

inula-router

npm i https://pkg.pr.new/openInula/inula/inula-router@13

commit: 98c7ddf

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

.github/workflows/ci.yml (1)

57-57: Ensure Proper File Formatting

YAML linting reported a missing newline at the end of the file. To adhere to standard practices and avoid linting issues, please add a newline at the end.

🧰 Tools

🪛 YAMLlint (1.35.1)

[error] 57-57: no new line character at the end of file

(new-line-at-end-of-file)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 41e7983 and 98c7ddf.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (2)

• .github/workflows/ci.yml (1 hunks)
• .gitignore (0 hunks)

💤 Files with no reviewable changes (1)

• .gitignore

🧰 Additional context used

🪛 YAMLlint (1.35.1)

.github/workflows/ci.yml

[error] 57-57: no new line character at the end of file

(new-line-at-end-of-file)

🔇 Additional comments (1)

.github/workflows/ci.yml (1)

57-57: Revised Release Command: Removal of --compact Flag

The updated command in the Release step now omits the --compact flag as intended. Please verify that this change produces the desired output format during the publish process.

🧰 Tools

🪛 YAMLlint (1.35.1)

[error] 57-57: no new line character at the end of file

(new-line-at-end-of-file)