Repository navigation
release: prepare 3.0.0 - #77
Merged
Merged
Conversation
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
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
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.
Release preparation for 3.0.0 of both packages (stack #69 is merged into
master).This PR
CHANGELOG.md:[Unreleased]becomes[v3.0.0](linked to thev3.0.0release tag, like earlier entries); the "not yet published" line is replaced by the two package versions.Living docs drop "unreleased" from the 3.0.0 descriptions: client runtime, Extensions and composition, platform and packaging, maintenance playbook (date lines set to 2026-10-24).
Directory.Build.propsis already 3.0.0 for both packages.CHANGELOG.mdand the three README copies: the AWS package pins 3.0.0 needs.AWSSDK.Extensions.NETCore.Setup4.0.102.4 needsAWSSDK.Core4.0.102.11, so a project that pins lower versions getsNU1605on restore.Dogfood (CI-built
3.0.0-nightly.20261023.49573c2from GitHub Packages, local win-x64)Upgraded by changing only
Directory.Packages.propsandnuget.config; no consumer code changed.netstandard2.0, net10 resolvesnet10.0. Unit tests 486/486 on both base and nightly (built withNuGetAudit=false, because the base already fails on existing NU1901/NU1902 audit errors). Integration tests on nightly: 17/22. The same 5 Lambda playground tests also fail on base: the Aspire Lambda emulator cannot find itsWrapperLocalStack.Lambda.*.exe.AWSSDK.Corepin is raised to 4.0.102.11. Its only test project contains no tests.The only upgrade friction found: consumers that pin
AWSSDK.Core(4.0.9.6, 4.0.100.3) or Setup (4.0.4.10) centrally hitNU1605until they raise the pins. Documented in this PR.Merge timing
Merge this immediately before publishing, so
masterdoes not describe 3.0.0 as released while the feed still lacks it. Then:LocalStack.Client3.0.0 →nuget. Wait until nuget.org indexes it.LocalStack.Client.Extensions3.0.0 with client version 3.0.0 →nuget.v3.0.0and the GitHub release from this changelog section.Docs-only change; no runtime tests run for this PR.