This document is no longer actual for kotlin-metadata-jvm (although it is still theoretically possible to release it separately from Kotlin using neighbor configuration), but can be used for kotlinx-metadata-klib.
Release is usually done from master branch, unless specific circumstances occur (e.g. incompatibility of protobuf between master and current Kotlin's release branch).
To release version N of kotlinx-metadata-klib:
Update ChangeLog.md and other documentation (ReadMe.md, Migration.md) if necessary. If release is done with different version of Kotlin than the previous one, add note about metadata version update.
If changes are large: Send changes for the review as a separate branch and merge them into master after approve.
Run the TeamCity build with parameters:
deployVersion is a version of Kotlin and kotlin-stdlib which kotlinx-metadata-klib should depend on.kotlinxMetadataDeployVersion is a version N you want to release.In Sonatype admin interface:
Announce new version in forum topic. Additionally, you may announce it in the #compiler public Slack channel and in the internal channel #ext-google-compiler.