Release activities check-list for releases:
- Run code inspections (fix typos, Kotlin issues, fix code formatting, linter). RC
- Write missed KDocs for new APIs. RC
- Update tutorials according to the latest code changes.
- Update README.MD according last code changes:
- update an artifact version.
- update a Kotlin version.
- update the section about library versions.
- Check the project version in the file
gradle.properties
(i.e. it's 0.10.0 when trying to release version 0.10.0).- For major releases: update a project version in the file
v.list
- For major releases: update a project version in the file
main.yml
- For major releases: update a project version in the file
project.ihp
- For major releases: update a project version in the file
- Update
libs.versions.toml
file if required, run./gradlew dependencyUpdates
to check for updates. RC - Create and checkout the release branch. RC
- Make last commit with release tag (v0.1.1 for example) to the release branch. RC
- Run tests and build artifacts on TC for the commit with the release tag. RC
- Deploy artifacts on Maven Central via the
Publish
task running on TC based on the commit with the release tag. RC - Check artifacts' availability on MavenCentral. RC
- Check Gradle Plugin portal availability (usually it takes 12 hours). RC
- Update a bootstrap dependency version in the
libs.versions.toml
file (only after the plugin's publication). RC - Do final testing: RC
- Check on Datalore with a test project (TODO: add link).
- Check for Android with a test project (TODO: add link).
- Check for ServerSide with a test project (TODO: add link).
- Run
./gradlew korro
to update the code snippets for the docs. - Publish Documentation from GitHub Action
- Prepare and publish the Release Notes. RC
- Create a Release from the release tag on GitHub. RC
- Update a KDF version in the Kotlin Jupyter Descriptor. Now the Renovate bot does this.
- Update the DataFrame version in the
gradle.properties
file for the next release cycle (i.e. 0.10.0 -> 0.11.0) - Update deprecated functions in deprecationMessages.kt
such that
Level.WARNING
messages are changed toLevel.ERROR
Level.ERROR
messages and their functions are removed.- Update regions in the file accordingly.
- Update Notebook examples, both in the project and on Datalore.
(Activities that need to be done for Release Candidate releases are marked as such)