Skip to content

docs: Add release notes for 0.297#27484

Open
prestodb-ci wants to merge 7 commits intomasterfrom
release-notes-0.297
Open

docs: Add release notes for 0.297#27484
prestodb-ci wants to merge 7 commits intomasterfrom
release-notes-0.297

Conversation

@prestodb-ci
Copy link
Copy Markdown
Contributor

@prestodb-ci prestodb-ci commented Apr 1, 2026 •
edited by sourcery-ai bot
Loading

Missing Release Notes

Apurva Kumar

Chandrakant Vankayalapati

Dong Wang

Maria Basmanova

Prabhu Shankar

Pramod Satya

Reetika Agrawal

Sreeni Viswanadha

XiaoDu

Zac

adheer-araokar

tanjialiang

Extracted Release Notes

All Commits

Release Notes

== NO RELEASE NOTE ==

Note: The full release notes summary was too large (76874 characters) for GitHub's PR body limit.
The complete summary has been saved to release-notes-missing-0.297.md in this pull request.
Please delete this file before merging.

Summary by Sourcery

Documentation:

  • Document the 0.297 release in the Sphinx docs under release notes.

@prestodb-ci prestodb-ci requested review from a team, elharo and steveburnett as code owners April 1, 2026 14:32
@sourcery-ai
Copy link
Copy Markdown
Contributor

sourcery-ai bot commented Apr 1, 2026 •
edited
Loading

Reviewer's Guide

Adds release notes documentation for Presto 0.297 by introducing a new Sphinx release page and temporarily checking in a large, auto-generated markdown file of missing release notes that must be deleted before merge.

Flow diagram for 0_297 release notes authoring workflow

flowchart TD
  dev_start[Developer prepares 0_297 release notes] --> gen_notes[Run release notes generator]
  gen_notes --> missing_md[Create release_notes_missing_0_297_md]
  gen_notes --> rst_page[Create release_0_297_rst Sphinx page]

  missing_md --> checklist[Review and complete missing release notes checklist]
  checklist --> done_checklist[All release notes accounted for]

  done_checklist --> remove_md[Delete release_notes_missing_0_297_md from repo]
  rst_page --> review_pr[Open documentation pull request]
  missing_md --> review_pr

  review_pr --> ci_docs[Run docs build and release notes checks]
  ci_docs --> approve_pr[Reviewer verifies release notes and missing file removal]
  approve_pr --> merge[Merge PR with final 0_297 release notes]
Loading

Flow diagram for Sphinx release documentation structure with 0_297 page

flowchart TD
  release_index[release_rst index] --> v296[release_0_296_rst]
  release_index --> v297[release_0_297_rst]
  release_index --> future_versions[Future_release_pages]

  v297 --> sections[Per_feature_and_fix_sections]
  sections --> links_prs[Links_to_GitHub_PRs]
  sections --> user_visible_changes[Summaries_of_user_visible_changes]

  sphinx_conf[Sphinx_configuration] --> release_index
  sphinx_conf --> doctree[Docs_build_tree]
  doctree --> html_output[Built_release_notes_html]

  v297 --> html_output
Loading

File-Level Changes

Change Details Files
Add a new Sphinx release notes page for version 0.297 and integrate it into the documentation release index.
  • Create release-0.297.rst under the Sphinx release directory to hold the 0.297 notes.
  • Update the top-level release.rst index (or related config) so that the 0.297 page is part of the rendered documentation navigation.
 presto-docs/src/main/sphinx/release.rst
presto-docs/src/main/sphinx/release/release-0.297.rst
Check in an auto-generated markdown file containing the full list of missing and extracted release notes and commits for 0.297, intended only as a temporary artifact for review.
  • Add release-notes-missing-0.297.md at the repo root containing all missing/extracted release notes and commit metadata for 0.297.
  • Document in the PR description that this markdown file exceeds normal PR-body limits and must be deleted before merging.
 release-notes-missing-0.297.md
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

sourcery-ai[bot]
sourcery-ai bot reviewed Apr 1, 2026
View reviewed changes
Copy link
Copy Markdown
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 - I've found 2 issues, and left some high level feedback:

  • The helper file release-notes-missing-0.297.md is currently checked in at the repo root; since the PR description already calls this a temporary artifact, please remove it from the tree (or move it under a dedicated tooling location and .gitignore it) before merging so it doesn't ship with the release.
  • In release-notes-missing-0.297.md, the trailing == NO RELEASE NOTE == block contradicts the large extracted notes above; if you keep using this generator, consider removing or updating that placeholder so it doesn't cause confusion about whether release notes exist for 0.297.
Prompt for AI Agents 
Please address the comments from this code review:

## Overall Comments
- The helper file `release-notes-missing-0.297.md` is currently checked in at the repo root; since the PR description already calls this a temporary artifact, please remove it from the tree (or move it under a dedicated tooling location and .gitignore it) before merging so it doesn't ship with the release.
- In `release-notes-missing-0.297.md`, the trailing `== NO RELEASE NOTE ==` block contradicts the large extracted notes above; if you keep using this generator, consider removing or updating that placeholder so it doesn't cause confusion about whether release notes exist for 0.297.

## Individual Comments

### Comment 1
<location path="presto-docs/src/main/sphinx/release/release-0.297.rst" line_range="20" />
<code_context>
+* Fix Materilized Views with ``DEFINER`` rights to require ``CREATE_VIEW_WITH_SELECT_COLUMNS`` on base tables. `#26902 <https://github.com/prestodb/presto/pull/26902>`_
</code_context>
<issue_to_address>
**issue (typo):** Correct spelling of 'Materilized' to 'Materialized'.

For consistency with the rest of the docs, this bullet should say “Materialized Views.”

```suggestion
* Fix Materialized Views with ``DEFINER`` rights to require ``CREATE_VIEW_WITH_SELECT_COLUMNS`` on base tables. `#26902 <https://github.com/prestodb/presto/pull/26902>`_
```
</issue_to_address>

### Comment 2
<location path="presto-docs/src/main/sphinx/release/release-0.297.rst" line_range="96" />
<code_context>
+* Upgrade ajvto 8.18.0 in response to `CVE-2025-69873 <https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-69873>`_. `#27154 <https://github.com/prestodb/presto/pull/27154>`_
</code_context>
<issue_to_address>
**issue (typo):** Add a missing space between 'ajv' and 'to'.

Update this line to `Upgrade ajv to 8.18.0...` to fix the merged `ajvto` typo.

```suggestion
* Upgrade ajv to 8.18.0 in response to `CVE-2025-69873 <https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-69873>`_. `#27154 <https://github.com/prestodb/presto/pull/27154>`_
```
</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.

@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 1, 2026 •
edited
Loading

Dependency Review

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

Snapshot Warnings

⚠️: No snapshots were found for the head SHA 4142459.
Ensure that dependencies are being submitted on PR branches. Re-running this action after a short time may resolve the issue. See the documentation for more information and troubleshooting advice.

Scanned Files

None

steveburnett
steveburnett reviewed Apr 1, 2026
View reviewed changes
steveburnett
steveburnett reviewed Apr 1, 2026
View reviewed changes
steveburnett
steveburnett reviewed Apr 1, 2026
View reviewed changes
steveburnett
steveburnett reviewed Apr 1, 2026
View reviewed changes
steveburnett
steveburnett reviewed Apr 1, 2026
View reviewed changes
steveburnett
steveburnett reviewed Apr 1, 2026
View reviewed changes
steveburnett
steveburnett reviewed Apr 1, 2026
View reviewed changes
steveburnett
steveburnett reviewed Apr 1, 2026
View reviewed changes
steveburnett
steveburnett reviewed Apr 1, 2026
View reviewed changes
steveburnett
steveburnett reviewed Apr 1, 2026
View reviewed changes
steveburnett
steveburnett reviewed Apr 1, 2026
View reviewed changes
steveburnett
steveburnett reviewed Apr 1, 2026
View reviewed changes
steveburnett
steveburnett reviewed Apr 1, 2026
View reviewed changes
steveburnett
steveburnett reviewed Apr 1, 2026
View reviewed changes
steveburnett
steveburnett reviewed Apr 1, 2026
View reviewed changes
steveburnett
steveburnett reviewed Apr 1, 2026
View reviewed changes
steveburnett
steveburnett reviewed Apr 1, 2026
View reviewed changes
steveburnett
steveburnett reviewed Apr 1, 2026
View reviewed changes
steveburnett
steveburnett reviewed Apr 1, 2026
View reviewed changes
steveburnett
steveburnett reviewed Apr 1, 2026
View reviewed changes
steveburnett
steveburnett reviewed Apr 1, 2026
View reviewed changes
steveburnett
steveburnett reviewed Apr 1, 2026
View reviewed changes
steveburnett
steveburnett reviewed Apr 1, 2026
View reviewed changes
steveburnett
steveburnett reviewed Apr 1, 2026
View reviewed changes
steveburnett
steveburnett reviewed Apr 1, 2026
View reviewed changes
steveburnett
steveburnett reviewed Apr 1, 2026
View reviewed changes
steveburnett
steveburnett reviewed Apr 1, 2026
View reviewed changes
steveburnett
steveburnett reviewed Apr 1, 2026
View reviewed changes
steveburnett
steveburnett reviewed Apr 1, 2026
View reviewed changes
steveburnett
steveburnett reviewed Apr 1, 2026
View reviewed changes
steveburnett
steveburnett reviewed Apr 1, 2026
View reviewed changes
steveburnett
steveburnett reviewed Apr 1, 2026
View reviewed changes
steveburnett
steveburnett reviewed Apr 1, 2026
View reviewed changes
steveburnett and others added 2 commits April 1, 2026 14:44
@steveburnett
Apply suggestions from code review
dccfdb5 
Co-authored-by: Steve Burnett <burnett@pobox.com>
@hantangwangd
Fix up release notes
72ab886
steveburnett
steveburnett reviewed Apr 1, 2026
View reviewed changes
steveburnett
steveburnett reviewed Apr 1, 2026
View reviewed changes
steveburnett
steveburnett reviewed Apr 1, 2026
View reviewed changes
steveburnett
steveburnett reviewed Apr 1, 2026
View reviewed changes
steveburnett
steveburnett reviewed Apr 1, 2026
View reviewed changes
steveburnett
steveburnett reviewed Apr 1, 2026
View reviewed changes
@steveburnett
Apply suggestions from code review
1c05955 
Co-authored-by: Steve Burnett <burnett@pobox.com>
steveburnett
steveburnett reviewed Apr 1, 2026
View reviewed changes
@steveburnett
Apply suggestions from code review
4142459 
Co-authored-by: Steve Burnett <burnett@pobox.com>
@steveburnett
Copy link
Copy Markdown
Contributor

steveburnett commented Apr 1, 2026

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

What I have done:

  • Reviewed every entry and light editing for phrasing, readability, and consistency.
  • Fixed broken links.
  • Checked for product names, capitalization, and such being correct.
  • Deleted redundant PR links to the PR that the entry is drawn from, where they had been manually edited and then the automation created a second link to the same PR.
  • Fixed formatting issues.
  • Added links from the release note entry to 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.
  • 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 - one to Prestissimo Changes, three to Documentation Changes.
  • I deleted the following release note entry in Oracle Connector Changes, and the topic, as not relevant to a user.
    Update Oracle test classes to re-enable them. #25762

What I did not do:

  • Look at any of the Missing Release Notes PRs to decide if any of them should be added.
  • Copy any release note entry to Breaking Changes or Highlights.

Work left to do:

Thank you @hantangwangd for already populating the Breaking Changes and Highlights sections!

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 you feel 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
  • Delete the file release-notes-missing-0.297.md‎.
  • Squash commits and merge

If there's anything else I can do to help, or any questions, please ask and I'm happy to.

@github-project-automation github-project-automation bot moved this to 🆕 Unprioritized in Presto Documentation Apr 1, 2026
@steveburnett steveburnett moved this from 🆕 Unprioritized to 🏗 In progress in Presto Documentation Apr 1, 2026
@github-actions github-actions bot removed the docs label Apr 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@steveburnett steveburnett steveburnett left review comments

@sourcery-ai sourcery-ai[bot] sourcery-ai[bot] left review comments

@elharo elharo Awaiting requested review from elharo elharo is a code owner

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

None yet

Projects

Presto Documentation
Status: 🏗 In progress

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@prestodb-ci @steveburnett @hantangwangd