chore: update patch version to 2.3.1

[kshitij-k-osmosys]

Portal PR Checklist

Task Link

Osmosys Developers must include the Pinestem task link in the PR.

REST-1300

Pre-requisites

• I have gone through the Contributing guidelines for Submitting a Pull Request (PR) and ensured that this is not a duplicate PR.
• I have performed preliminary testing to ensure that any existing features are not impacted and any new features are working as expected.

PR Details

PR details have been updated as per the given format (see below)

• PR title adheres to the format specified in guidelines (e.g., feat: add admin login page)
• Description has been added
• Related changes have been added (optional)
• Screenshots have been added (optional)
• Pending actions have been added (optional)
• Any other additional notes have been added (optional)

Additional Information

• Appropriate label(s) have been added (ready for review should be added if the PR is ready to be reviewed)
• Assignee(s) and reviewer(s) have been added (optional)

---

Description:

Updated the API and Portal app version from 2.3.0 to 2.3.1

Summary by CodeRabbit

• Chores
  • Updated the API to version 2.3.1, introducing minor improvements and bug fixes.
  • Updated the Portal application to version 2.3.1, reflecting similar enhancements.

[coderabbitai]

Walkthrough

This pull request updates the version numbers in the package.json files for both the API and Portal applications. The version is incremented from "2.3.0" to "2.3.1", indicating a minor change that may include bug fixes or small improvements.

Changes

File(s)	Change Summary
apps/api/package.json, apps/portal/package.json	Updated version from "2.3.0" to "2.3.1"

Possibly related PRs

• chore: update minor version #71: Involved similar version updates in package files, aligning with the changes made here.

Suggested labels

Ready for review, dependencies

Suggested reviewers

• osm-vishnukyatannawar

Poem

I'm a bunny with code in my paws,
Hopping through updates without any flaws.
A slight version lift, quick and neat,
Bugs nibble away while the fixes meet.
With joyful hops and ASCII cheer,
I celebrate the changes with a carrot beer!
🥕🐰 Happy coding from your CodeRabbit!

Tip

⚡💬 Agentic Chat (Pro Plan, General Availability)

• We're introducing multi-step agentic chat in review comments and issue comments, within and outside of PR's. This feature enhances review and issue discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments and add commits to existing pull requests.

---

📜 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 0a5264b and b10bbdc.

⛔ Files ignored due to path filters (2)

• apps/api/package-lock.json is excluded by !**/package-lock.json
• apps/portal/package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (2)

• apps/api/package.json (1 hunks)
• apps/portal/package.json (1 hunks)

🔇 Additional comments (2)

apps/portal/package.json (1)

3-3: Version Bump Confirmed for Portal Application:
The version update from "2.3.0" to "2.3.1" is correctly applied and aligns with the PR objectives. This patch version bump should maintain backward compatibility, and all dependent build and deployment pipelines should handle this update accordingly.

apps/api/package.json (1)

3-3: Version Bump Confirmed for API Application:
The version change from "2.3.0" to "2.3.1" is properly updated and consistent with the portal application’s version increment. This update meets the PR’s objectives and helps ensure uniformity across the applications.

---

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.