Skip to content

docs: Add release notes for 0.297#52

Open
unidevel wants to merge 3 commits intomasterfrom
release-notes-0.297
Open

docs: Add release notes for 0.297#52
unidevel wants to merge 3 commits intomasterfrom
release-notes-0.297

Conversation

@unidevel
Copy link
Copy Markdown

Missing Release Notes

Apurva Kumar

Chandrakant Vankayalapati

Dong Wang

Prabhu Shankar

Pramod Satya

Reetika Agrawal

Sreeni Viswanadha

XiaoDu

Zac

adheer-araokar

tanjialiang

unidevel

  • bf5bdfd fix(ci): Update location of presto-release-tools with new version

Extracted Release Notes

All Commits

Release Notes

== NO RELEASE NOTE ==

Note: The full release notes summary was too large (76176 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.

unidevel added a commit to prestodb/presto that referenced this pull request Mar 31, 2026
#27466)

## Description
1. presto-release-tools can not be fetched due to maven central
publishing limitation
2. check maven central publishing requirements
3. add required `<name>` field to presto-lance 

## Motivation and Context
Depends on PRs:
- prestodb/presto-release-tools#65
- prestodb/presto-release-tools#64
- prestodb/presto-release-tools#63
- prestodb/presto-release-tools#62

## Impact
CI

## Test Plan
Tested with:
1. release note check action:
https://github.com/prestodb/presto/actions/runs/23815800338/job/69414865062?pr=27466
2. maven central publishing requirements check:
https://github.com/unix280/presto/actions/runs/23812452401/job/69402863222#step:8:76
3. Prepare release action in presto =>
https://github.com/unix280/presto/actions/runs/23812844511
4. Release notes PR => unix280#52
5. Release notes missing list file =>
https://github.com/unix280/presto/blob/release-notes-0.297/release-notes-missing-0.297.md

## Contributor checklist

- [ ] Please make sure your submission complies with our [contributing
guide](https://github.com/prestodb/presto/blob/master/CONTRIBUTING.md),
in particular [code
style](https://github.com/prestodb/presto/blob/master/CONTRIBUTING.md#code-style)
and [commit
standards](https://github.com/prestodb/presto/blob/master/CONTRIBUTING.md#commit-standards).
- [ ] PR description addresses the issue accurately and concisely. If
the change is non-trivial, a GitHub Issue is referenced.
- [ ] Documented new properties (with its default value), SQL syntax,
functions, or other functionality.
- [ ] If release notes are required, they follow the [release notes
guidelines](https://github.com/prestodb/presto/wiki/Release-Notes-Guidelines).
- [ ] Adequate tests were added if applicable.
- [ ] CI passed.
- [ ] If adding new dependencies, verified they have an [OpenSSF
Scorecard](https://securityscorecards.dev/#the-checks) score of 5.0 or
higher (or obtained explicit TSC approval for lower scores).

## Release Notes
Please follow [release notes
guidelines](https://github.com/prestodb/presto/wiki/Release-Notes-Guidelines)
and fill in the release notes below.

```
== NO RELEASE NOTE ==
```

## Summary by Sourcery

Update CI and release scripts to retrieve presto-release-tools from
GitHub releases using a configurable version instead of Maven Central.

CI:
- Change release-notes-check workflow to download the
presto-release-tools executable directly from GitHub releases and run it
from a temporary path.
- Make the release-notes-check workflow use a configurable
RELEASE_TOOLS_VERSION with a default of 0.13.

Deployment:
- Update release preparation workflow and release-notes script to use a
configurable RELEASE_TOOLS_VERSION (default 0.13) and fetch
presto-release-tools from GitHub releases instead of Maven.

Chores:
- Align release tooling version and retrieval method across CI workflows
and release scripts.
bibith4 pushed a commit to bibith4/presto that referenced this pull request Apr 1, 2026
prestodb#27466)

## Description
1. presto-release-tools can not be fetched due to maven central
publishing limitation
2. check maven central publishing requirements
3. add required `<name>` field to presto-lance 

## Motivation and Context
Depends on PRs:
- prestodb/presto-release-tools#65
- prestodb/presto-release-tools#64
- prestodb/presto-release-tools#63
- prestodb/presto-release-tools#62

## Impact
CI

## Test Plan
Tested with:
1. release note check action:
https://github.com/prestodb/presto/actions/runs/23815800338/job/69414865062?pr=27466
2. maven central publishing requirements check:
https://github.com/unix280/presto/actions/runs/23812452401/job/69402863222#step:8:76
3. Prepare release action in presto =>
https://github.com/unix280/presto/actions/runs/23812844511
4. Release notes PR => unix280#52
5. Release notes missing list file =>
https://github.com/unix280/presto/blob/release-notes-0.297/release-notes-missing-0.297.md

## Contributor checklist

- [ ] Please make sure your submission complies with our [contributing
guide](https://github.com/prestodb/presto/blob/master/CONTRIBUTING.md),
in particular [code
style](https://github.com/prestodb/presto/blob/master/CONTRIBUTING.md#code-style)
and [commit
standards](https://github.com/prestodb/presto/blob/master/CONTRIBUTING.md#commit-standards).
- [ ] PR description addresses the issue accurately and concisely. If
the change is non-trivial, a GitHub Issue is referenced.
- [ ] Documented new properties (with its default value), SQL syntax,
functions, or other functionality.
- [ ] If release notes are required, they follow the [release notes
guidelines](https://github.com/prestodb/presto/wiki/Release-Notes-Guidelines).
- [ ] Adequate tests were added if applicable.
- [ ] CI passed.
- [ ] If adding new dependencies, verified they have an [OpenSSF
Scorecard](https://securityscorecards.dev/#the-checks) score of 5.0 or
higher (or obtained explicit TSC approval for lower scores).

## Release Notes
Please follow [release notes
guidelines](https://github.com/prestodb/presto/wiki/Release-Notes-Guidelines)
and fill in the release notes below.

```
== NO RELEASE NOTE ==
```

## Summary by Sourcery

Update CI and release scripts to retrieve presto-release-tools from
GitHub releases using a configurable version instead of Maven Central.

CI:
- Change release-notes-check workflow to download the
presto-release-tools executable directly from GitHub releases and run it
from a temporary path.
- Make the release-notes-check workflow use a configurable
RELEASE_TOOLS_VERSION with a default of 0.13.

Deployment:
- Update release preparation workflow and release-notes script to use a
configurable RELEASE_TOOLS_VERSION (default 0.13) and fetch
presto-release-tools from GitHub releases instead of Maven.

Chores:
- Align release tooling version and retrieval method across CI workflows
and release scripts.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants