You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The v1.11.1 release attempt exposed two bugs in the VSIX step added in #344:
1. The "Warn if SSMS extension build failed" step had `(issue #343)` in a
single-line `run:` value. YAML treated ` #343)"` as a comment, leaving
pwsh an unterminated string. The step failed, and because it was not
continue-on-error it failed the whole job - skipping signing, Velopack,
and every artifact upload. v1.11.1 was created empty and has been deleted.
2. The VSIX build itself failed: `msbuild -t:Restore,Build` evaluates the
project once before Restore writes the package-generated props, so
VSToolsPath never got redirected into the Microsoft.VSSDK.BuildTools
package and the VSSDK targets could not be found (MSB4226).
Fixes:
- Build the VSIX with `msbuild -restore -t:Build` so Restore runs in its
own evaluation and the VSSDK targets resolve without the VS workload.
- Remove the separate warn step. The build step now only sets a `BUILT`
output on success and the upload is gated on it - nothing in the SSMS
path can fail the job anymore.
- Drop non-ASCII characters from the run-block strings.
- Bump version to 1.11.2 (1.11.1 is burned).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Write-Host "::warning::VSIX manifest version ($manifestVersion) != release version ($env:VERSION) — bump source.extension.vsixmanifest and Properties/AssemblyInfo.cs"
86
+
Write-Host "::warning::VSIX manifest version ($manifestVersion) does not match release version ($env:VERSION) - bump source.extension.vsixmanifest and Properties/AssemblyInfo.cs"
0 commit comments