Skip to content

chore: bump version to 0.9.0 in package.json and package-lock.json#94

Merged
aimensahnoun merged 1 commit intomainfrom
chore/0.9.0-release
Jul 22, 2025
Merged

chore: bump version to 0.9.0 in package.json and package-lock.json#94
aimensahnoun merged 1 commit intomainfrom
chore/0.9.0-release

Conversation

@aimensahnoun
Copy link
Member

@aimensahnoun aimensahnoun commented Jul 22, 2025 •
edited by coderabbitai bot
Loading

  • bump to version 0.9.0 for release

Summary by CodeRabbit

  • Chores
    • Updated the application version to 0.9.0.

@aimensahnoun aimensahnoun self-assigned this Jul 22, 2025
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jul 22, 2025 •
edited
Loading

Walkthrough

The only change in this pull request is an update of the version number in the package.json file from "0.7.0" to "0.9.0". No other modifications to dependencies, scripts, or metadata are present.

Changes

File(s) Change Summary
package.json Version number updated from 0.7.0 to 0.9.0

Estimated code review effort

1 (~2 minutes)

Possibly related PRs

Suggested reviewers

  • rodrigopavezi
  • bassgeta
  • MantisClone
📜 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 3822b0e and a7f4069.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (1)
  • package.json (1 hunks)
🔇 Additional comments (1)
package.json (1)

4-4: Version bump looks fine – please verify accompanying artifacts (lockfile, changelog, tag).

The package.json version is now 0.9.0.
Double-check that:

  1. package-lock.json (or pnpm-lock.yaml, etc.) carries the same new version.
  2. A matching git tag / release note or CHANGELOG entry is prepared, so consumers can trace what changed between 0.7.0 → 0.9.0.
  3. CI/CD pipelines that rely on the version string (e.g., Docker image tags, publish steps) pick up the new value.

No code changes required here; this is just a consistency reminder before merging.

🪧 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

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

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 generate sequence diagram to generate a sequence diagram of the changes in 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.

@aimensahnoun aimensahnoun enabled auto-merge (squash) July 22, 2025 06:32
bassgeta
bassgeta approved these changes Jul 22, 2025
View reviewed changes
Copy link
Contributor

@bassgeta bassgeta left a comment

Choose a reason for hiding this comment

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

Version be like 📈

@aimensahnoun aimensahnoun merged commit 24be483 into main Jul 22, 2025
9 checks passed
@aimensahnoun aimensahnoun deleted the chore/0.9.0-release branch July 22, 2025 08:05
@coderabbitai coderabbitai bot mentioned this pull request Aug 7, 2025
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@bassgeta bassgeta bassgeta approved these changes

@rodrigopavezi rodrigopavezi Awaiting requested review from rodrigopavezi

Assignees

@aimensahnoun aimensahnoun

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@aimensahnoun @bassgeta