prepare releases - #12
Merged
Merged
Conversation
- delivery 20.0.0-rc.2 - management 9.0.0-rc.2 - sync 2.0.0-rc.2
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #12 +/- ##
==========================================
+ Coverage 90.29% 90.40% +0.10%
==========================================
Files 505 505
Lines 10762 10830 +68
Branches 999 1017 +18
==========================================
+ Hits 9718 9791 +73
+ Misses 708 701 -7
- Partials 336 338 +2
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
pokornyd
approved these changes
Aug 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Prepared by the Prepare release workflow.
Review each version property and its promoted changelog entry, then merge.
Publishing happens per product, when a GitHub Release is created for each tag:
Once this is merged, run Actions -> Publish batch to create those releases.
It releases dependency-first and waits for each product to reach NuGet before
starting the next, so ordering is handled for you. It defaults to a dry run,
and re-running skips whatever is already published.
Releases are independent - publish or abandon one without affecting the others.
Cross-product dependency floors
Releasing a product does not change what its siblings depend on. These floors
live in
Directory.Packages.propsand are raised in their own PR, after thedependency is on NuGet. Being behind is normal - raise a floor only when the
consuming code needs the newer API.
Note
Creating these releases by hand instead? Then order matters: if this batch
also re-points a product at a sibling's new version in
Directory.Packages.props, release that dependency first. The releaseworkflow refuses to publish a package whose cross-product
Kontent.Ai.*dependency is not yet on NuGet. Packages within one product are exempt -
they are published together.