Skip to content

chore(release): 1.132.05311 (vscode 1.132.0) - #43

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

chore(release): 1.132.05311 (vscode 1.132.0)#43
github-actions[bot] wants to merge 1 commit into
mainfrom
release/1.132.05311

Conversation

@github-actions

@github-actions github-actions Bot commented Aug 9, 2026

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: 2ae5617104e6b045218ed0ee428aea47bbf220aa9d671dd4b036ced7705f6e35
  • ZIP SHA-256: a2890a44e4e0845ce3fabf70f540c67c54247bf5f6a39e6f307f2bddafd75903

What happens on merge

  • upstream/stable.json advances to track 1.132.0.
  • 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 31301283190 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 9, 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