Update @burgan-tech/vnext-schema to v0.0.27

[yilmaztayfun]

Bump @burgan-tech/vnext-schema dependency from version 0.0.26 to 0.0.27 in package-lock.json for both dependencies and devDependencies.

Summary by Sourcery

Build:

• Update locked version of @burgan-tech/vnext-schema to 0.0.27 in package-lock.json.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ 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

---

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

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the locked version of @burgan-tech/vnext-schema from 0.0.26 to 0.0.27 in package-lock.json for both dependencies and devDependencies, ensuring the project uses the newer schema package consistently.

File-Level Changes

Change	Details	Files
Bumped the locked @burgan-tech/vnext-schema version to 0.0.27 wherever it appears in package-lock.json.	Updated the dependency entry for @burgan-tech/vnext-schema from version 0.0.26 to 0.0.27 under dependencies. Updated the devDependency entry for @burgan-tech/vnext-schema from version 0.0.26 to 0.0.27 under devDependencies. Ensured resolved/version/integrity fields for @burgan-tech/vnext-schema in the lockfile align with version 0.0.27 if present.	package-lock.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.

[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 performs a routine maintenance update by bumping the @burgan-tech/vnext-schema dependency to its latest patch version, 0.0.27. This ensures the project benefits from any bug fixes or minor improvements introduced in the new release, maintaining the stability and security of the application's dependencies.

Highlights

• Dependency Update: The @burgan-tech/vnext-schema package has been updated from version 0.0.26 to 0.0.27.
• Scope of Update: This update applies to both the dependencies and devDependencies sections within the package-lock.json file.

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 updates the @burgan-tech/vnext-schema dependency to version 0.0.27. While the version bump is correct, I've noticed a maintainability issue in how the dependency is declared. The package @burgan-tech/vnext-schema is listed in both dependencies and devDependencies, which is redundant. I've left a comment with a recommendation to fix this.

[gemini-code-assist]

The dependency @burgan-tech/vnext-schema is listed in both dependencies and devDependencies. This is redundant and can lead to confusion about the package's role.

A package should be either a production dependency (in dependencies) or a development dependency (in devDependencies), but not both.

• If @burgan-tech/vnext-schema is required for your application to run in production, it should only be in dependencies.
• If it's only needed for development purposes like building, testing, or validation, it should only be in devDependencies.

Given its name and the scripts in package.json (like validate, build), it seems more likely to be a development dependency.

Please determine the correct scope for this dependency and remove it from the other list in your package.json file. After updating package.json, run npm install to regenerate the package-lock.json file accordingly.