chore: update major version to v3.0.0

[kshitij-k-osmosys]

Portal PR Checklist

Task Link

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

REST-1612

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 api and portal major version to v3.0.0

Summary by CodeRabbit

• Chores
  • Updated the version number for both the API and Portal applications to 3.0.0. No other changes were made.

[coderabbitai]

Walkthrough

The version numbers in the package.json files for both the API and Portal applications were updated from "2.3.1" to "3.0.0". No other changes were made to dependencies, scripts, or configurations.

Changes

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

Possibly related PRs

• chore: update version to 1 #30: Updates version fields in the same package.json files for both api and portal applications.
• chore: update patch version to 2.3.1 #73: Updates the version fields in the same files, but for a different version increment.
• chore: update version to 2 #36: Updates the version fields in api and portal package.json files, following a similar version bump pattern.

Suggested labels

Ready for review, dependencies

Suggested reviewers

• osm-vishnukyatannawar

Poem

A hop and a skip, the numbers have grown,
From two-point-three-one to three-oh-oh shown.
No scripts rearranged, no configs to tweak,
Just a versioning leap in a single quick streak.
🐇✨

---

📜 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 5b6ca12 and f6793fc.

⛔ 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/api/package.json (1)

3-3: Ensure ancillary artifacts reflect the major bump to v3.0.0

The version jump from 2.3.1 → 3.0.0 implies breaking-change semantics.
Please confirm that:
• CHANGELOG / release notes enumerate the breaking changes behind this major.
• Any workspace‐level or root package.json, lock-files (package-lock.json / pnpm-lock.yaml / yarn.lock), CI version tags, and deployment manifests are regenerated or updated to keep the repo consistent.

Skipping these updates can cause reproducible-build drift or publish failures.

apps/portal/package.json (1)

3-3: Propagate the v3.0.0 bump across portal collateral

Same concern as for the API package: verify that portal-specific lock files, Docker images, Helm charts, and any documentation referencing 2.x are updated to 3.0.0. This guards against mixed-version artefacts during the next release cycle.

---

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