Add patch version release notes for 3.16.1, 3.15.5, 3.14.4, 3.13.5, and 3.12.8

[josh-wong]

Description

This PR adds patch version release notes for ScalarDB 3.16, 3.15, 3.14, 3.13, and 3.12.

Related issues and/or PRs

N/A

Changes made

• Added patch version release notes for the following versions:
  • 3.16.1
  • 3.15.5
  • 3.14.4
  • 3.13.5
  • 3.12.8

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)

Provide any additional information or notes that may be relevant to the reviewers or stakeholders.
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 is solely focused on updating the ScalarDB documentation. It introduces comprehensive release notes for recent patch versions across multiple major releases, providing users with detailed information on bug fixes and critical vulnerability patches for both Community and Enterprise editions.

Highlights

• Documentation Update: I've added new patch version release notes for ScalarDB versions 3.16.1, 3.15.5, 3.14.4, 3.13.5, and 3.12.8.
• Bug Fixes: The new release notes detail various bug fixes across different ScalarDB versions, including issues related to transaction commits, Cassandra mutation error handling, JDBC connection leaks, and specific problems within ScalarDB Cluster like data tag updates and UnsupportedOperationException with ABAC.
• Vulnerability Patches: Several security vulnerability fixes are highlighted, such as upgrades to grpc_health_probe, jetty library, and the PostgreSQL driver to address identified CVEs.
• Multi-language Support: The updates include both English and Japanese versions of the release notes for consistency across documentation.

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 is currently in preview and 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 to provide feedback.

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 adds release notes for several patch versions. The changes are mostly correct, but I've identified some minor inconsistencies in both the English and Japanese documentation. My feedback includes suggestions to fix a typo, correct the document structure, and improve consistency in terminology and grammar to enhance the overall quality of the release notes.

[josh-wong]

/gemini review

[gemini-code-assist]

Code Review

This PR adds release notes for several patch versions. Some of the Japanese release notes are missing a key heading, leading to a confusing structure. There's also inconsistent use of trailing spaces in list items, which can cause unintended line breaks. The suggestions aim to fix these formatting and structural problems to improve the clarity and consistency of the documentation.