release: 1.0.1 - #35
Merged
Merged
Conversation
Bump Version to 1.0.1 and cut the CHANGELOG [Unreleased] section to [1.0.1] — 2026-08-22, adding the compare/tag link refs. Maintenance release, no consumer-facing API or behavior change: - FileCredentialManager null-check hardening (behavior-identical; resolves the cs/dereferenced-value-may-be-null CodeQL alert). - CI-only move to buildless CodeQL analysis (Standards §4.4). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
Release 1.0.1
Maintenance release. No consumer-facing API or behavior change — safe drop-in over 1.0.0.
Contents (cut from
[Unreleased])FileCredentialManager.ListCredentialsAsyncnull-check hardening —credential?.… == true→credential is not null && …. Behavior-identical; resolves thecs/dereferenced-value-may-be-nullCodeQL alert with a genuine fix. (Shipped code — this is why 1.0.1 is a real package.)Release mechanics
<Version>bumped 1.0.0 → 1.0.1.[Unreleased]cut to[1.0.1] — 2026-08-22; compare/tag link refs updated.dotnet build -c Releasepacks1.0.1.nupkg+.snupkgclean (0 warnings, package validation OK).After this merges, tagging
v1.0.1triggers thepublishjob (OIDC → nuget.org).🤖 Generated with Claude Code