chore: update minor version

[kshitij-k-osmosys]

Portal PR Checklist

Task Link

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

REST-1275

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:

Update transcript summarizer minor version for release 2.3.0

Summary by CodeRabbit

• Chores
  • Updated release versions for the API and Portal components from 2.2.0 to 2.3.0.

[coderabbitai]

Walkthrough

This pull request updates the version numbers for the "api" and "portal" projects by modifying their respective package.json files. Both files have the version field changed from "2.2.0" to "2.3.0". There are no other alterations to properties or dependencies.

Changes

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

Possibly related PRs

• chore: update portal version to v2.2.0 #42: Involved version updates in package files for similar projects, though with a different version increment.
• chore: update version to 2 #36: Also made version number updates in the "api" and "portal" projects' package files.

Suggested reviewers

• osm-vishnukyatannawar

Poem

I'm just a little bunny with ears so keen,
Hopping through the code where changes are seen.
From "2.2.0" to "2.3.0", the versions now gleam,
A carrot of progress in our development dream.
With a twitch of my whiskers and a joyful hop,
I celebrate these updates—coding never stops!
(_/)( •_• )(>🐰<)

---

📜 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 dd5afc8 and 5c0a67b.

⛔ 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 Update Verified
The version field has been correctly updated from "2.2.0" to "2.3.0". This aligns with the intended minor version release for the portal project. Please ensure that any additional release documentation (e.g., changelog) is updated accordingly.

apps/api/package.json (1)

3-3: Minor Version Update for API Project
The API project’s version has been updated to "2.3.0", matching the portal project's update. This consistent update across projects supports the coordinated release strategy. Please check that related documentation or scripts referencing the version are updated if necessary.

---

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.