Skip to content

Copilot Pace 0.2.3 (Pilot)

Pre-release
Pre-release

Choose a tag to compare

View all tags
@github-actions github-actions released this 15 Oct 15:17
· 23 commits to main since this release
v0.2.3
bca8e81
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Pilot update using the final publisher identity intended for 1.0.0. Real account and corporate network validation remain pending. This release does not publish to Marketplace.

  • Set the publisher to rubenblancomanzano and the extension ID to rubenblancomanzano.copilot-pace.
  • Record Ruben Blanco Manzano as author and add the extension-specific issue tracker. The GitHub repository remains rublaman/copilot-pace.
  • Align installed-extension tests and release provenance checks with the new publisher.
  • Document replacing earlier pilots, the personal publisher profile shared by future extensions, and the remaining acceptance and promotion steps for 1.0.0.

Install or replace an earlier pilot

Versions through 0.2.2 used rublaman.copilot-pace. VS Code treats this publisher change as a separate extension, not an automatic update. Uninstall the earlier pilot before installing this one so both identities are not active together. Existing copilotPace.* user settings are retained.

Download copilot-pace-0.2.3.vsix and choose Extensions → … → Install from VSIX…, or run:

# Only if an earlier pilot is installed:
code --uninstall-extension rublaman.copilot-pace
code --install-extension .\copilot-pace-0.2.3.vsix

Reload VS Code and run Copilot Pace: Connect GitHub. Reading usage requires the intended Copilot account through VS Code's GitHub authentication. Future versions, including 1.0.0, will keep the new publisher identity.

Validation and limits

Branch CI and tagged release validation passed on the same commit, covering Node 24.21.0 / 26.11.1, VS Code 1.120.0 / 1.141.0, dependency audit, installed production-package tests and VSIX inspection.

Local preflight passed 133 unit tests, 8 release-script tests, 16 integration tests on VS Code 1.141.0 and all 6 installed-package tests; npm audit reported no vulnerabilities. The local VS Code 1.120.0 runner could not start because an active Windows VS Code installer held its update mutex; a retry reproduced that environment block. CI passed that version without changing its checks.

The attached draft VSIX was downloaded and tested unchanged on Windows 11 / VS Code 1.141.0: all 6 package tests passed. In the same isolated profile, the original published 0.2.2 VSIX was installed, its old identity uninstalled, and this file installed; the new identity was verified and user settings were retained. Production ignored obsolete demo settings. The VSIX manifest, contents, demo exclusion and checksum were checked; publication uses this exact file without rebuilding.

These checks are synthetic and do not establish real sign-in, authenticated reconnection, account switching, quota accuracy or corporate proxy/certificate compatibility. The internal GitHub endpoint may change; GHE.com, GitHub Enterprise Server and web hosts remain unsupported. Complete the documented real-account acceptance and validate the final stable candidate before publishing 1.0.0 to Marketplace.

Commit: bca8e8106395381cce7267f3f5391380573ea4d2
Annotated tag: v0.2.3
VSIX SHA-256: 579f46f994d65d84d8fc1530e7b06e2aa3c005f5224dfb53d12b75d5a20be690

SHA256SUMS.txt and build-info.json identify the attached artifact. The published 0.2.0, 0.2.1 and 0.2.2 tags and assets remain unchanged.

Assets 5
Loading