Skip to content

chore: update UMPK packages to 0.9.0-beta.5 - #3

Merged
milutinke merged 1 commit into
masterfrom
chore/umpk-beta5
Oct 9, 2026
Merged

milutinke merged 1 commit into
masterfrom
chore/umpk-beta5

Conversation

@milutinke

Copy link
Copy Markdown
Member

Update all nine direct UMPK package pins to the published 0.9.0-beta.5 release so DMCBK consumes the ARM32 AES-CFB8 improvement. Update the README and guide version declarations to match.

UMPK release: https://github.com/MCCTeam/UMPK/releases/tag/v0.9.0-beta.5

Existing plugin minimum-version ranges remain valid for beta.5 and retain their earlier compatibility baseline.

Validated commit e5dd8ba6a495b039c1d5d26d40923cba62fab323 with .NET SDK 10.0.401 on Linux:

  • Restore from public NuGet into an isolated cache; all 13 resolved UMPK libraries use beta.5 and their NuGet metadata identifies release commit cdf8f1bedda742439bac2011feca4567fa566f08.
  • Release build: zero warnings or errors.
  • Full solution tests: 1,950 passed, none skipped or failed.
  • Pack: all nine DMCBK packages identify the PR commit and their UMPK dependencies reference beta.5.
  • All 17 sample projects compiled against the locally packed DMCBK packages and public UMPK packages. Source mapping kept DMCBK packages on the local feed, and package metadata confirmed the tested commit.
  • ClientGuide self-test, MarketplaceGuide, advanced compiled-plugin verifier, and tutorial stage 4 runtime checks passed. These exchange protocol traffic in memory; they do not require a public server or account.
  • git diff --check passed. No runtime C# changes or new tests were needed for the package update.

Commands used dotnet restore DMCBK.slnx, dotnet build DMCBK.slnx -c Release --no-restore, dotnet test DMCBK.slnx -c Release --no-build --no-restore, and dotnet pack DMCBK.slnx -c Release --no-build --no-restore, with MSBuild -m:1 -nr:false. Package artifacts and logs stayed under /tmp.

@milutinke
milutinke merged commit 5e50ade into master Oct 9, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant