prepare releases

[github-actions]

Prepared by the Prepare release workflow.

• aspnetcore 1.0.0-rc.2
• model-generator 11.0.0-rc.2

Review each version property and its promoted changelog entry, then merge.

Publishing happens per product, when a GitHub Release is created for each tag:

aspnetcore-v1.0.0-rc.2
model-generator-v11.0.0-rc.2

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

package                               floor        latest       status
------------------------------------  -----------  -----------  ------
Kontent.Ai.Delivery                   20.0.0-rc.2  20.0.0-rc.2  current
Kontent.Ai.Delivery.Abstractions      20.0.0-rc.2  20.0.0-rc.2  current
Kontent.Ai.Urls                       20.0.0-rc.2  20.0.0-rc.2  current
Kontent.Ai.Delivery.SourceGeneration  20.0.0-rc.2  20.0.0-rc.2  current
Kontent.Ai.Management                 9.0.0-rc.2   9.0.0-rc.2   current

Every floor is at the latest published version.

Releasing a product does not change what its siblings depend on. These floors
live in Directory.Packages.props and are raised in their own PR, after the
dependency 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 release
workflow 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.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.40%. Comparing base (e913d07) to head (c73b589).

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #14   +/-   ##
=======================================
  Coverage   90.40%   90.40%           
=======================================
  Files         505      505           
  Lines       10830    10830           
  Branches     1017     1017           
=======================================
  Hits         9791     9791           
  Misses        701      701           
  Partials      338      338           

Flag	Coverage Δ
aspnetcore	90.40% <ø> (ø)
delivery	90.40% <ø> (ø)
management	90.40% <ø> (ø)
model-generator	90.40% <ø> (ø)
sync	90.40% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.