Add context7 config and update vnext versions

[yilmaztayfun]

Added new context7.json with URL and public key. Updated vnext.config.json to increment runtimeVersion and schemaVersion.

Summary by Sourcery

Add a new context7 configuration file and bump version metadata in the vnext configuration.

New Features:

• Introduce a context7.json configuration containing the new service URL and public key.

Enhancements:

• Increment runtimeVersion and schemaVersion in vnext.config.json to reflect the updated configuration.

Summary by CodeRabbit

• Chores
  • Added new context mapping configuration.
  • Updated runtime version to 0.0.23 and schema version to 0.0.28.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Introduces a new context7 configuration file with URL and public key, and increments runtime and schema versions in vnext.config.json to align with the new context configuration.

File-Level Changes

Change	Details	Files
Add a new context7 configuration file describing the context endpoint and key material.	Create context7.json to define the context7 URL. Include the public key in the new context7 configuration file.	context7.json
Update vnext configuration versions to account for the new context configuration.	Increment runtimeVersion in vnext.config.json. Increment schemaVersion in vnext.config.json.	vnext.config.json

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Configuration updates introducing a new context mapping file and incrementing version numbers in the main configuration. Both changes are metadata-only with no functional logic modifications or behavioral alterations.

Changes

Cohort / File(s)	Summary
Configuration Updates context7.json, vnext.config.json	New context configuration file added with URL and public key mappings; runtimeVersion and schemaVersion both incremented (0.0.22→0.0.23 and 0.0.27→0.0.28)

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Verify context7.json has valid JSON syntax and expected structure
• Confirm version number increments align with semantic versioning scheme

Poem

🐰 A new context hops into view,
Versions climb the mountain too,
Public keys and URLs align,
Configuration so divine!
✨

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch f/sprint24

---

📜 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 895bf80 and a0a6520.

📒 Files selected for processing (2)

• context7.json (1 hunks)
• vnext.config.json (1 hunks)

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Summary of Changes

Hello @yilmaztayfun, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a new configuration file, "context7.json", which specifies a URL and public key for an external service. Concurrently, it updates the "runtimeVersion" and "schemaVersion" within "vnext.config.json", indicating a progression in the application's versioning.

Highlights

• New Configuration File: A new "context7.json" file has been added, containing a URL and a public key for "context7.com/burgan-tech/vnext-example".
• Version Updates: The "vnext.config.json" file has been updated to increment the "runtimeVersion" from "0.0.22" to "0.0.23" and the "schemaVersion" from "0.0.27" to "0.0.28".

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[sourcery-ai]

Hey there - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[gemini-code-assist]

Code Review

This pull request introduces a new configuration file context7.json and increments the runtimeVersion and schemaVersion in vnext.config.json. The changes are straightforward. However, I have a couple of suggestions for the new context7.json file. Firstly, it's missing a newline at the end, which is a common convention. Secondly, and more importantly, it contains a hardcoded public key. It is recommended to load such values from environment variables or a configuration service to improve security and maintainability.

[gemini-code-assist]

Hardcoding keys, even public ones, is not recommended as a best practice. It makes key rotation difficult and couples the configuration to the codebase. It's better to load this value from an environment variable or a configuration service at runtime. This allows for different keys in different environments (dev, staging, production) without changing the code.

[gemini-code-assist]

The file should end with a newline character. It's a standard convention for text files in Unix-like systems and can prevent issues with some tools that process text files.

Suggested change

	}
	}