Bump VS Code extension version from 1.0.3 to 1.0.4#14860
Bump VS Code extension version from 1.0.3 to 1.0.4#14860adamint merged 1 commit intodotnet:release/13.2from
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
🚀 Dogfood this PR with:
curl -fsSL https://raw.githubusercontent.com/dotnet/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 14860Or
iex "& { $(irm https://raw.githubusercontent.com/dotnet/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 14860" |
There was a problem hiding this comment.
Pull request overview
This PR bumps the Aspire VS Code extension’s published version in extension/package.json from 1.0.3 to 1.0.4, which is used by the extension packaging pipeline to produce versioned VSIX artifacts.
Changes:
- Update VS Code extension
package.jsonversion to1.0.4.
| "description": "%extension.description%", | ||
| "publisher": "microsoft-aspire", | ||
| "version": "1.0.3", | ||
| "version": "1.0.4", |
There was a problem hiding this comment.
The extension version was bumped in package.json, but extension/package-lock.json still has the root package version set to 1.0.3 (top-level "version" and packages[""].version). This leaves the repo in an inconsistent state for anyone using npm-based workflows; please update or regenerate the lockfile (or remove it if it's intentionally unused).
| "version": "1.0.4", | |
| "version": "1.0.3", |
| "description": "%extension.description%", | ||
| "publisher": "microsoft-aspire", | ||
| "version": "1.0.3", | ||
| "version": "1.0.4", |
There was a problem hiding this comment.
PR description includes a placeholder “Fixes # (issue)”. Please either link the actual issue/PR being fixed or remove this line so release notes/auto-linking don’t end up with an invalid reference.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Description
Bumps the VS Code extension
package.jsonversion from1.0.3to1.0.4.Fixes # (issue)
Checklist
<remarks />and<code />elements on your triple slash comments?aspire.devissue: