Repository navigation
MP Core 1.0.1
A patch version. It follows 1.0.0. No behaviour and no public API of any package changes: apart from its
version number and the baseline setting, the code of every package, of MPCore.Cli and of MPCore.Templates is the
code of 1.0.0 (git diff v1.0.0 HEAD -- src tools lists only version declarations, the baseline setting, the removed
suppression files and two README files). The version exists because the API baseline cannot move without one
(eng/check-version-moved.sh counts all of src as shipped).
Moving from 1.0.0
Nothing to do in a product.
Changed
| Area | Now |
|---|---|
| The API baseline | MPCoreBaselineVersion is 1.0.0, the last published version: on pack, every runtime package of this cohort is validated against its 1.0.0 package, which eng/restore-api-baseline.sh downloads from nuget.org and checks. The CompatibilitySuppressions.xml files of the review of 1.0 are removed: 1.0.0 carries the reviewed API, so the breaks they recorded against 0.10.1 are in the baseline itself, and ApiReviewTests fail if one of them remains |
| CI and the release | as in 1.0.0: they restore and check the baseline package by package, after the script's self-test; require mode for the whole restore is not switched on |
| One test's time bound | tests only, nothing ships: ResourceKeyTests allowed 5 s from the first request of a host that had just started, and failed on a cold host with the status right. It now allows 20 s, 10 s below the 30 s the port holds on, so a hanging port that is not cut off still fails it |
What stays as it is
The baseline names the last published version, so after 1.0.1 is published MPCoreBaselineVersion stays 1.0.0 until the
next version starts; that version's first change takes the baseline step. Nothing is wrong in the meantime: 1.0.1 has the
API of 1.0.0.
Checking a download
The release run freezes the SHA-256 of every package it built in SHA256SUMS.txt, uploaded with the packages
as the run's artifact. The sums are of the packages as the release run built them. nuget.org adds its
repository signature (.signature.p7s) to every package after upload, so a downloaded file has another
SHA-256. To check a download, verify its signatures with dotnet nuget verify --all <file> and compare its
entries other than .signature.p7s with the built package.