Remove ScalarDB 3.11 end-of-support message from notifications

[josh-wong]

Description

This PR removes the notification about the end of support for ScalarDB 3.11 since that version is officially no longer supported.

Related issues and/or PRs

• Mark ScalarDB 3.11 as no longer supported #1420

Changes made

• Removed the notification about the upcoming end of support for ScalarDB 3.11.
• Updated a notification message to refer to "ScalarDB Cluster 3.15" instead of "ScalarDB Cluster" for vector search capabilities.

Checklist

The following is a best-effort checklist. If any items in this checklist are not applicable to this PR or are dependent on other, unmerged PRs, please still mark the checkboxes after you have read and understood each item.

• I have updated the side navigation as necessary.
• I have commented my code, particularly in hard-to-understand areas.
• I have updated the documentation to reflect the changes.
• Any remaining open issues linked to this PR are documented and up-to-date (Jira, GitHub, etc.).
• My changes generate no new warnings.
• Any dependent changes in other PRs have been merged and published.

Additional notes (optional)

N/A

[gemini-code-assist]

Summary of Changes

Hello @josh-wong, 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 refines the in-app notifications by removing outdated information and clarifying an existing message. The primary goal is to ensure that users receive accurate and current information regarding ScalarDB versions and features. This change improves the user experience by preventing confusion from obsolete notifications.

Highlights

• Notification Removal: The notification warning about the upcoming end of support for ScalarDB 3.11 has been removed, as this version is now officially unsupported.
• Notification Update: The message for discovering vector search capabilities in ScalarDB Cluster has been updated to specifically refer to "ScalarDB Cluster 3.15" for improved clarity.

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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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. ↩

[gemini-code-assist]

Code Review

This pull request removes an outdated notification about the end of support for ScalarDB 3.11 and updates another notification to specify the version for vector search capabilities. The changes are generally good, but I've pointed out a potential version mismatch in the updated notification message. The message refers to version 3.15, while the linked documentation uses version 3.16.0 in its examples. I've suggested aligning the version numbers to avoid confusion.