chore: update version to 2.1.0

[xixas]

Description

Update api and portal Version to 2.1

Summary by CodeRabbit

• Chores
  • Updated the API app version from 2.0.0 to 2.1.0.

[coderabbitai]

Warning

Rate Limit Exceeded

@xixas has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 57 minutes and 30 seconds before requesting another review.

How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.
Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.
Please see our FAQ for further information.

Commits

Files that changed from the base of the PR and between 658c4ea and 8da2232.

Walkthrough

The primary change in this update is the version increment of the package.json file within the api application, moving from version "2.0.0" to "2.1.0". This signifies a minor update, which typically includes new features, improvements, or non-breaking changes.

Changes

File Path	Change Summary
apps/api/package.json	Updated version from "2.0.0" to "2.1.0"

In the code, a version rose,
From two-point-oh to two-one-oh.
New features bloom, improvements grow,
Like springtime fields where changes show.
A rabbit hops with cheerful cheer,
For progress made this bright new year. 🐇✨

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 as 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 full the review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the 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.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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.

[coderabbitai]

Actionable comments posted: 0

Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 893b706 and 658c4ea.

Files ignored due to path filters (1)

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

Files selected for processing (1)

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

Files skipped from review due to trivial changes (1)

• apps/api/package.json

[xixas]

@coderabbitai Update Summary

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

@xixas, here's the updated summary for PR #39:

PR Summary

Title: chore: update version
User: xixas
Number: 39

Description:
Update Backend Version to 2.1

Detailed Changes

1. Version Update:

   • Updated the package.json in the apps/api directory from version "2.0.0" to "2.1.0".

2. Postman Collection Update:

   • Updated the Transcript Summarization.postman_collection.json with new headers and body configurations for GraphQL operations, including new UUIDs for headers and updated authorization tokens.

3. New Decorator:

   • Added a new file user.decorator.ts in apps/api/src/Decorator. This decorator helps to extract the current user from the request context in GraphQL executions.

4. Authentication Strategy Enhancement:

   • Modified azure-ad.strategy.ts in apps/api/src/auth to include user details extraction from the Azure AD profile and store it in the request profile.

5. Summary Module Enhancements:

   • Updated summary.resolver.ts and summary.service.ts in apps/api/src/modules/summary to support user email extraction from the request and use it in summary creation. This includes changes to handle the user's email as part of the summary creation process, ensuring that the created and modified records are tagged with the user's email.

These updates enhance the functionality and security of the application, particularly in handling user data and authentication processes.

Analysis chain

---

Scripts executed

The following scripts were executed for the analysis:

---

Script:

#!/bin/bash
# List all files changed in the PR
git diff --name-only HEAD~1..HEAD

Length of output: 270

---

---

Script:

#!/bin/bash
# Fetch diffs of the mentioned files to understand the specific changes made
git diff HEAD~1..HEAD apps/api/Transcript\ Summarization.postman_collection.json
git diff HEAD~1..HEAD apps/api/src/Decorator/user.decorator.ts
git diff HEAD~1..HEAD apps/api/src/auth/azure-ad.strategy.ts
git diff HEAD~1..HEAD apps/api/src/modules/summary/summary.resolver.ts
git diff HEAD~1..HEAD apps/api/src/modules/summary/summary.service.ts

Length of output: 22535