Skip to content

chore(release): 1.132.15383 (vscode 1.132.1) - #44

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
release/1.132.15383
Open

chore(release): 1.132.15383 (vscode 1.132.1)#44
github-actions[bot] wants to merge 1 commit into
mainfrom
release/1.132.15383

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Auto-generated release PR — the build already succeeded and the
GitHub Release is already published with signed, notarized artifacts.
Merging this PR advances main's pinned upstream version and points
the in-app auto-updater at the new ZIP.

Artifact verification

  • DMG SHA-256: af2fd4590a4a78cc628e32e1e2a2c6c71c7573db92f369fa31564f8a4102a8f9
  • ZIP SHA-256: ec513532135fae6b5a6ed7196d02630351760f656ba2d1d10b5081c76ae8be8c

What happens on merge

  • upstream/stable.json advances to track 1.132.1.
  • versions/stable/darwin-arm64/latest.json points at the new
    ZIP; the in-app auto-updater (Squirrel.Mac) picks it up on its
    next poll.

Why the build status check is missing

The build job on this PR is skipped — the same version was just
built and notarized in run 31575033085 above. The skip is
gated by the auto-release label; see the build job if: in
.github/workflows/cron-build-and-release.yml.

@github-actions github-actions Bot added the auto-release Cron release PR; safe to merge once you've reviewed label Aug 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

auto-release Cron release PR; safe to merge once you've reviewed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants