Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update version to 0.22.0 #175

Merged
merged 2 commits into from
May 31, 2024
Merged

Conversation

nineinchnick
Copy link
Member

This also attempts to fix generating release notes.

@nineinchnick
Copy link
Member Author

I'd like to wait for #174 and #172. I attempted fixing release notes because #172 can be considered a breaking change, and we should communicate this better.

We can also wait for Trino 449 to be released.

@mosabua
Copy link
Member

mosabua commented May 30, 2024

We can look at adding a simple website using mkdocs in the same way we do it in Trino Gateway .. could be just overview, release notes, the generated docs somehow and thats it for now.

The generated changelog was not used, because it was not located in the
chart directory. Releases should only include files commited in the
repository, so avoid generatic a changelog file and instead use the
GitHub API to generate notes automatically in the GitHub release.
@nineinchnick nineinchnick merged commit cda8130 into trinodb:main May 31, 2024
9 checks passed
@nineinchnick nineinchnick deleted the prepare-release branch May 31, 2024 08:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

3 participants