Skip to content

Conversation

@prestodb-ci
Copy link
Contributor

@prestodb-ci prestodb-ci commented Dec 1, 2025

Missing Release Notes

Amit Dutta

Jiaqi Zhang

Joe Abraham

Mariam AlMesfer

Pedro Pedreira

Tal Galili

XiaoDu

Xiaoxuan

tanjialiang

Extracted Release Notes

All Commits

Release Notes

== NO RELEASE NOTE ==

@prestodb-ci prestodb-ci requested review from a team, elharo and steveburnett as code owners December 1, 2025 18:43
@sourcery-ai
Copy link
Contributor

sourcery-ai bot commented Dec 1, 2025

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Adds release notes documentation for Presto 0.296, aggregating missing and extracted release notes into a new Sphinx release page and wiring it into the docs release index.

File-Level Changes

Change Details Files
Introduce a new Sphinx release notes page for version 0.296.
  • Create presto-docs/src/main/sphinx/release/release-0.296.rst containing the curated 0.296 release notes, including missing and previously extracted items.
  • Structure the new release notes file with sections per feature/fix area (connectors, native, security, UI, docs, etc.) and link each entry to its originating pull request where applicable.
presto-docs/src/main/sphinx/release/release-0.296.rst
Register the 0.296 release notes page in the main releases index so it appears in the published documentation navigation.
  • Update presto-docs/src/main/sphinx/release.rst to include the 0.296 release entry in the releases toctree, ensuring the new page is built and linked.
  • Maintain ordering and formatting consistency with existing release entries to keep the release index stable.
presto-docs/src/main/sphinx/release.rst

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

@github-actions
Copy link

github-actions bot commented Dec 1, 2025

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

Copy link
Contributor

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey there - I've reviewed your changes - here's some feedback:

  • Several release note entries contain obvious typos (e.g., senstive, senstivity, versio, enbled) and minor grammatical issues; it would be good to clean these up for a more polished 0.296 release page.
  • Some bullets appear duplicated or redundant (e.g., the compression codecs entry mentions ZSTD/ORC/Parquet twice, and the Postgres timestamp fix description is repeated); consider deduplicating or consolidating these for clarity.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- Several release note entries contain obvious typos (e.g., `senstive`, `senstivity`, `versio`, `enbled`) and minor grammatical issues; it would be good to clean these up for a more polished 0.296 release page.
- Some bullets appear duplicated or redundant (e.g., the compression codecs entry mentions ZSTD/ORC/Parquet twice, and the Postgres timestamp fix description is repeated); consider deduplicating or consolidating these for clarity.

## Individual Comments

### Comment 1
<location> `presto-docs/src/main/sphinx/release/release-0.296.rst:17` </location>
<code_context>
+* Improve  ``MergeJoinForSortedInputOptimizer`` to do sort merge join when one side of the input is sorted. `#26361 <https://github.com/prestodb/presto/pull/26361>`_
+* Add :func:`array_transpose` to return a transpose of an array. `#26470 <https://github.com/prestodb/presto/pull/26470>`_
+* Add a configurable `clusterTag` config flag, which is returned from the `/v1/cluster` endpoints and displayed in the UI. `#26485 <https://github.com/prestodb/presto/pull/26485>`_
+* Add a new optimizer which do null skew mitigation for applicable semi joins. `#26251 <https://github.com/prestodb/presto/pull/26251>`_
+* Add a session property `query_types_enabled_for_history_based_optimization` to specifiy query types which will use HBO. `#26183 <https://github.com/prestodb/presto/pull/26183>`_
+* Add compression support for http2 protocol on cpp worker. `#26382 <https://github.com/prestodb/presto/pull/26382>`_
</code_context>

<issue_to_address>
**suggestion (typo):** Fix grammar in "which do null skew mitigation" phrase.

Change to either "which does null skew mitigation" or "which performs null skew mitigation" to fix the subject–verb agreement.

```suggestion
* Add a new optimizer which performs null skew mitigation for applicable semi joins. `#26251 <https://github.com/prestodb/presto/pull/26251>`_
```
</issue_to_address>

### Comment 2
<location> `presto-docs/src/main/sphinx/release/release-0.296.rst:18` </location>
<code_context>
+* Add :func:`array_transpose` to return a transpose of an array. `#26470 <https://github.com/prestodb/presto/pull/26470>`_
+* Add a configurable `clusterTag` config flag, which is returned from the `/v1/cluster` endpoints and displayed in the UI. `#26485 <https://github.com/prestodb/presto/pull/26485>`_
+* Add a new optimizer which do null skew mitigation for applicable semi joins. `#26251 <https://github.com/prestodb/presto/pull/26251>`_
+* Add a session property `query_types_enabled_for_history_based_optimization` to specifiy query types which will use HBO. `#26183 <https://github.com/prestodb/presto/pull/26183>`_
+* Add compression support for http2 protocol on cpp worker. `#26382 <https://github.com/prestodb/presto/pull/26382>`_
+* Add configuration property ``max-prefixes-count``. `#25550 <https://github.com/prestodb/presto/pull/25550>`_
</code_context>

<issue_to_address>
**issue (typo):** Correct the spelling of "specifiy".

Change "specifiy" to "specify" in this line.

```suggestion
* Add a session property `query_types_enabled_for_history_based_optimization` to specify query types which will use HBO. `#26183 <https://github.com/prestodb/presto/pull/26183>`_
```
</issue_to_address>

### Comment 3
<location> `presto-docs/src/main/sphinx/release/release-0.296.rst:42` </location>
<code_context>
+______________________________________
+* Fix Prestissimo Iceberg connector mixed case column name query error. `#26163 <https://github.com/prestodb/presto/pull/26163>`_
+* Add back session property native_max_partial_aggregation_memory for Presto C++. `#26389 <https://github.com/prestodb/presto/pull/26389>`_
+* Add support basic insertion to iceberg tables. `#26338 <https://github.com/prestodb/presto/pull/26338>`_
+* Add support for custom schemas in native sidecar function registry. `#26236 <https://github.com/prestodb/presto/pull/26236>`_
+* Support TPC-DS connector in Presto C++. `#24751 <https://github.com/prestodb/presto/pull/24751>`_
</code_context>

<issue_to_address>
**suggestion (typo):** Add missing preposition in "Add support basic insertion".

Consider changing this to: "Add support for basic insertion to Iceberg tables." for more natural phrasing and consistency with the other bullets.

```suggestion
* Add support for basic insertion to Iceberg tables. `#26338 <https://github.com/prestodb/presto/pull/26338>`_
```
</issue_to_address>

### Comment 4
<location> `presto-docs/src/main/sphinx/release/release-0.296.rst:50` </location>
<code_context>
+________________
+* Upgrade Netty to 4.1.128.Final to address `CVE-2025-59419 <https://github.com/advisories/GHSA-jq43-27x9-3v86>`_. `#26349 <https://github.com/prestodb/presto/pull/26349>`_
+* Upgrade RoaringBitmap to 1.3.0. `#26238 <https://github.com/prestodb/presto/pull/26238>`_
+* Upgrade at.favre.lib:bcrypt versio to 0.10.2 in response to `CVE-2020-15250<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-15250>`_. `#26463 <https://github.com/prestodb/presto/pull/26463>`_
+* Upgrade calcite-core to 1.41.0 in response to `CVE-2025-48924 <https://github.com/advisories/GHSA-j288-q9x7-2f5v>`_. `#26248 <https://github.com/prestodb/presto/pull/26248>`_
+* Upgrade com.google.api:google-api-client version to 2.8.0 in response to the use of an outdated version. `#26063 <https://github.com/prestodb/presto/pull/26063>`_
</code_context>

<issue_to_address>
**issue (typo):** Fix "versio" typo and add missing space before the CVE link.

For the CVE reference, use valid reStructuredText link syntax so it renders properly, e.g.:

``... in response to `CVE-2020-15250 <https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-15250>`_``

```suggestion
* Upgrade at.favre.lib:bcrypt version to 0.10.2 in response to `CVE-2020-15250 <https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-15250>`_. `#26463 <https://github.com/prestodb/presto/pull/26463>`_
```
</issue_to_address>

### Comment 5
<location> `presto-docs/src/main/sphinx/release/release-0.296.rst:53` </location>
<code_context>
+* Upgrade io.dropwizard.metrics:metrics-core versio to 4.2.33 in response to the use of an outdated version. `#26199 <https://github.com/prestodb/presto/pull/26199>`_
</code_context>

<issue_to_address>
**issue (typo):** Correct "versio" to "version".

Suggested implementation:

```
* Upgrade at.favre.lib:bcrypt version to 0.10.2 in response to `CVE-2020-15250<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-15250>`_. `#26463 <https://github.com/prestodb/presto/pull/26463>`_

```

```
* Upgrade io.dropwizard.metrics:metrics-core version to 4.2.33 in response to the use of an outdated version. `#26199 <https://github.com/prestodb/presto/pull/26199>`_

```
</issue_to_address>

### Comment 6
<location> `presto-docs/src/main/sphinx/release/release-0.296.rst:101-102` </location>
<code_context>
+* Replace default iceberg compression codec from GZIP to ZSTD. `#26399 <https://github.com/prestodb/presto/pull/26399>`_
+* Update iceberg time column catalog type from string to long. `#26523 <https://github.com/prestodb/presto/pull/26523>`_
+
+Mongodb Connector Changes
+_________________________
+* Add TLS/SSL support with automatic JKS and PEM certificate format detection. Configure using ``mongodb.tls.enabled``, ``mongodb.tls.keystore-path``, ``mongodb.tls.keystore-password``, ``mongodb.tls.truststore-path``, and ``mongodb.tls.truststore-password`` properties. `#25374 <https://github.com/prestodb/presto/pull/25374>`_
</code_context>

<issue_to_address>
**suggestion (typo):** Use the standard "MongoDB" capitalization.

Consider updating the heading text to "MongoDB Connector Changes" to match the product’s official styling.

```suggestion
MongoDB Connector Changes
_________________________
```
</issue_to_address>

### Comment 7
<location> `presto-docs/src/main/sphinx/release/release-0.296.rst:106` </location>
<code_context>
+* Add TLS/SSL support with automatic JKS and PEM certificate format detection. Configure using ``mongodb.tls.enabled``, ``mongodb.tls.keystore-path``, ``mongodb.tls.keystore-password``, ``mongodb.tls.truststore-path``, and ``mongodb.tls.truststore-password`` properties. `#25374 <https://github.com/prestodb/presto/pull/25374>`_
+* Upgrade MongoDB Java Driver to 3.12.14. `#25374 <https://github.com/prestodb/presto/pull/25374>`_
+
+Mysql Connector Changes
+_______________________
+* Fix timestamp handling when ``legacy_timestamp`` is disabled. Timestamp values are now correctly stored and retrieved as wall-clock times without timezone conversion. Previously, values were incorrectly converted using the JVM timezone, causing data corruption. `#26449 <https://github.com/prestodb/presto/pull/26449>`_
</code_context>

<issue_to_address>
**suggestion (typo):** Use the standard "MySQL" capitalization.

Update the heading text to "MySQL Connector Changes" to match the product name spelling.

```suggestion
MySQL Connector Changes
```
</issue_to_address>

### Comment 8
<location> `presto-docs/src/main/sphinx/release/release-0.296.rst:120` </location>
<code_context>
+* Add support for case-sensitive identifiers in Pinot. It can be enabled by setting ``case-sensitive-name-matching=true`` configuration in the catalog configuration. `#26239 <https://github.com/prestodb/presto/pull/26239>`_
+* Upgrade Pinot version to 1.3.0. `#25785 <https://github.com/prestodb/presto/pull/25785>`_
+
+Postgresql Connector Changes
+____________________________
+* Fix timestamp handling when ``legacy_timestamp`` is disabled. Timestamp values are now correctly stored and retrieved as wall-clock times without timezone conversion. Previously, values were incorrectly converted using the JVM timezone, causing data corruption. `#26449 <https://github.com/prestodb/presto/pull/26449>`_
</code_context>

<issue_to_address>
**suggestion (typo):** Use the standard "PostgreSQL" capitalization.

Consider renaming this heading to "PostgreSQL Connector Changes" to match the proper database name and maintain consistency.

Suggested implementation:

```
PostgreSQL Connector Changes

```

1. Ensure this section header actually exists in `release-0.296.rst` with the exact spelling "Postgresql Connector Changes". If the capitalization or spacing differs, adjust the `SEARCH` text accordingly.
2. Confirm that the underline below the heading (the line of `_` characters) is at least as long as the new heading text; Sphinx/RST requires the underline length to be ≥ the heading length. If necessary, extend the underline by one character to keep formatting correct.
</issue_to_address>

### Comment 9
<location> `presto-docs/src/main/sphinx/release/release-0.296.rst:128-129` </location>
<code_context>
+_______________________
+* Add support for case-sensitive identifiers in Redis. It can be enabled by setting ``case-sensitive-name-matching=true`` configuration in the catalog configuration. `#26078 <https://github.com/prestodb/presto/pull/26078>`_
+
+Singlestore Connector Changes
+_____________________________
+* Improved string type mapping, now supports varchar(len) where len <= 21844. `#25476 <https://github.com/prestodb/presto/pull/25476>`_
</code_context>

<issue_to_address>
**suggestion (typo):** Use the standard "SingleStore" capitalization.

To align with the vendor’s naming, rename this heading to “SingleStore Connector Changes”.

```suggestion
SingleStore Connector Changes
_____________________________
```
</issue_to_address>

### Comment 10
<location> `presto-docs/src/main/sphinx/release/release-0.296.rst:35-38` </location>
<code_context>
+* Replace the java standard base64 encoder with BaseEncoding from Guava. `#26557 <https://github.com/prestodb/presto/pull/26557>`_
+* Change encoding of refresh token secret key to AES. `#26487 <https://github.com/prestodb/presto/pull/26487>`_
+* Upgrade dagre-d3-es to 7.0.13 in response to `CVE-2025-57347 <https://github.com/advisories/GHSA-cc8p-78qf-8p7q>`_. `#26422 <https://github.com/prestodb/presto/pull/26422>`_
+* Upgrade the procedure architecture to support distributed executing procedures. `#26373 <https://github.com/prestodb/presto/pull/26373>`_
+
+Prestissimo (native Execution) Changes
</code_context>

<issue_to_address>
**suggestion (typo):** Rephrase "distributed executing procedures" for clarity.

Consider rewording to something like "support procedures executed in a distributed manner" or "support distributed execution of procedures" for clearer phrasing.

```suggestion
* Upgrade dagre-d3-es to 7.0.13 in response to `CVE-2025-57347 <https://github.com/advisories/GHSA-cc8p-78qf-8p7q>`_. `#26422 <https://github.com/prestodb/presto/pull/26422>`_
* Upgrade the procedure architecture to support distributed execution of procedures. `#26373 <https://github.com/prestodb/presto/pull/26373>`_

Prestissimo (native Execution) Changes
```
</issue_to_address>

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Applying sourcery-ai suggestions

Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>
@github-project-automation github-project-automation bot moved this from 🆕 Unprioritized to 🏗 In progress in Presto Documentation Dec 1, 2025
@steveburnett
Copy link
Contributor

steveburnett commented Dec 1, 2025

I am done with the first set of reviews, and the PR is now ready for the Release Shepherd - who for this release is @tdcmeehan.

What I have done:

  • Reviewed and applied sourcery-ai recommended edits, which were mostly fixing capitalization of product names
  • Reviewed every entry, some light editing for phrasing, readability, and consistency
  • Edited initial keywords for entries following the Order of changes in the Release Notes Guidelines and moved them if necessary
  • Fixed broken links.
  • Added links into the Presto documentation where I thought having a doc link would help the reader
  • Tested and verified in a new local doc build that all links, including auto-gen links to the PR for each entry, work - including the ones that I added
  • Manually added Breaking Changes topic heading as that's not automated yet
  • Reviewed section headings to confirm they are in the order as shown in Order of sections in the Release Notes Guidelines.
  • Reviewed all release note entries, and revised where needed, to begin with a keyword shown in the Order of changes in the Release Notes Guidelines.
  • Moved some entries out of General Changes and into topics that were more appropriate for them
  • Moved some entries within sections following the Order of changes in the Release Notes Guidelines
  • Edited the PR title to pass the failing - and required - CI test.
  • Added a NO RELEASE NOTES heading to the PR's Description to pass the not-required CI test. It feels ironic to add NO RELEASE NOTES to a PR consisting entirely of release notes, but here we are. Now all CI checks on this PR pass.

Work left to do:

I believe that the work remaining in this PR for the Release Shepherd is:

  • Review the PRs in the Missing Release Notes section of this PR
    • Identify any of those PRs that should have release notes added for this release
    • Write (work with the PR author as needed) any needed release notes and add them
  • Identify any entries that should not be in the Release Notes, and delete them
  • Revise some of the existing entries as needed, to
    • Show the user-facing effect of the PR to the reader
    • Make the value of the change in the PR understandable to a non-developer
      (I've done a little of this, but there are more that would benefit from a committer's revision of them)
  • Re-request a review from me to review the new and revised entries
  • Select notable entries and copy those into the Highlights topic
  • Identify any entries that should be copied into the Breaking Changes topic
  • Squash commits and merge

@steveburnett steveburnett changed the title Add release notes for 0.296 fix(docs): Add release notes for 0.296 Dec 1, 2025
Copy link
Contributor

@steveburnett steveburnett left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the updated release notes @tdcmeehan! I pulled the updated branch and run a new local doc build, tested the new links, everything present looks good.

I see these items as done:

  • Identify any entries that should not be in the Release Notes, and delete them
  • Revise some of the existing entries as needed, to
    • Show the user-facing effect of the PR to the reader
    • Make the value of the change in the PR understandable to a non-developer

What I see left to do is:

  • Review the PRs in the Missing Release Notes section of this PR
    • Identify any of those PRs that should have release notes added for this release
    • Write (work with the PR author as needed) any needed release notes and add them
      (Note: You may have decided there are none that need to be added - the result would be the same in the file.)
  • Select notable entries and copy those into the Highlights topic
  • Identify any entries that should be copied into the Breaking Changes topic, or delete the Breaking Changes topic if there are no breaking changes in this release
  • Squash commits and merge

Copy link
Contributor

@steveburnett steveburnett left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add one comment to link to Materialized Views doc in the entry for Memory Connector Changes.

@tdcmeehan tdcmeehan force-pushed the release-notes-0.296 branch from 9ae5eb4 to 17a03d1 Compare December 4, 2025 20:49
@tdcmeehan
Copy link
Contributor

tdcmeehan commented Dec 4, 2025

@steveburnett I made a bunch of edits, do you mind reviewing again? I already added the missing release notes that I felt were noteworthy. There is no need to squash manually anymore, as the only Github merge command allowed will automatically squash commits.

Copy link
Contributor

@steveburnett steveburnett left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the update! Just two items.

@steveburnett
Copy link
Contributor

@steveburnett I made a bunch of edits, do you mind reviewing again? I already added the missing release notes that I felt were noteworthy.

Reviewed! Thanks for clarifying about the missing release notes already being addressed.

There is no need to squash manually anymore, as the only Github merge command allowed will automatically squash commits.

I've updated the Release Shepherd topic of Working with the Presto release notes PR to remove that step. Thanks!

Copy link
Contributor

@steveburnett steveburnett left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! (docs)

Pull latest updated branch, and a new local doc build. Reviewed end-to-end, no new concerns found.

@github-project-automation github-project-automation bot moved this from 🏗 In progress to ✅ Done in Presto Documentation Dec 4, 2025
@tdcmeehan tdcmeehan self-assigned this Dec 4, 2025
@tdcmeehan tdcmeehan merged commit 26ae5aa into master Dec 5, 2025
89 of 91 checks passed
@tdcmeehan tdcmeehan deleted the release-notes-0.296 branch December 5, 2025 02:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

4 participants