Bump version to 1.17.0 - #397
Merged
Merged
Conversation
All three version sources, kept in sync: - src/Directory.Build.props (single source for SDK-style projects) - src/PlanViewer.Ssms/source.extension.vsixmanifest - src/PlanViewer.Ssms/Properties/AssemblyInfo.cs The two SSMS files are not covered by Directory.Build.props because PlanViewer.Ssms is a legacy non-SDK project; they have drifted on past releases, so they are bumped by hand here. Verified: clean Release build 0 warnings, 202/202 tests pass. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Its software `version` had been left at 1.2.0 since the file was added in #111 (2026-03-18), 15 minor versions behind. It likely went unnoticed because it happened to match the `cff-version: 1.2.0` schema version on line 1, which is a different field and correctly stays at 1.2.0. Co-Authored-By: Claude Fable 5 <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.
Bumps the version to 1.17.0 ahead of the
dev->mainrelease merge.Bumped in all three places, since
PlanViewer.Ssmsis a legacy non-SDK project not covered byDirectory.Build.props(these have drifted on past releases):src/Directory.Build.props->1.17.0src/PlanViewer.Ssms/source.extension.vsixmanifest->1.17.0src/PlanViewer.Ssms/Properties/AssemblyInfo.cs->1.17.0.0(both AssemblyVersion and AssemblyFileVersion)Keeping the vsixmanifest in sync also means the "Build SSMS extension" step in
release.ymlwill not emit its version-mismatch warning.What 1.17.0 contains
#395 - quarterly maintenance
server/PlanSharepulled a vulnerable SQLite transitively; pinnedSQLitePCLRaw.bundle_e_sqlite32.1.12ListenLocalhostalone did not prevent a malicious page from rebinding a DNS name to 127.0.0.1 and reading saved server names, query text, and plan XML. Runtime-verified: rebound Host and hostile Origin both 403, legitimate loopback handshake 200sp_executesqlbatch; DDL identifier escaping did not double]Avalonia.Diagnostics, zero-warning build restored (drag/drop migrated to Avalonia'sDataTransferAPI), 5 GitHub Actions bumped#396 - Claude Code PR review workflows. Note these only become active once they land on
main, which this release accomplishes: the action refuses to run unless the workflow file is byte-identical on the default branch.Test plan
release.ymlconfirmed to trigger only on a merged PR tomainwith head refdev, so the follow-up merge is what cuts the release🤖 Generated with Claude Code