Andrew Scott 910f391674 build(vscode-extension): dynamically resolve upstream remote and use token for https pushes ...

Previously, the release script hardcoded the upstream repository URL as an unauthenticated HTTPS URL (https://github.com/angular/angular.git). Although the script verified that a GITHUB_TOKEN environment variable was present, it only used that token for REST API calls (such as creating the GitHub release) and did not provide it to Git commands. As a result, users who authenticate to GitHub via SSH (and do not have an HTTPS Git credential helper configured) were prompted interactively for GitHub login credentials when pushing the release tag.

This change dynamically resolves the upstream remote name from the user's configured remotes by checking for any remote pointing to angular/angular. When pushing over SSH, Git uses the user's existing SSH credentials. When pushing over HTTPS (or falling back), the script injects GITHUB_TOKEN into the push URL to prevent interactive authentication prompts.

(cherry picked from commit 6f848db435)

2026-08-13 15:38:56 +00:00

..

BUILD.bazel

test: add golden file test for VSCode extension package contents (#64991)

2025-11-07 11:36:31 -08:00

release.mts

build(vscode-extension): dynamically resolve upstream remote and use token for https pushes

2026-08-13 15:38:56 +00:00

tsconfig.json

build: improve vscode-ng-language-service release process

2025-11-06 10:53:09 -08:00

vsix_contents_goldens.mjs

test: add golden file test for VSCode extension package contents (#64991)

2025-11-07 11:36:31 -08:00