Skip to content

chore(release): 1.136.15939 (vscode 1.136.1) - #64

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

chore(release): 1.136.15939 (vscode 1.136.1)#64
github-actions[bot] wants to merge 1 commit into
mainfrom
release/1.136.15939

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: 3b28b30430b5bb5dea89bbb8e86ec1e931caf07e5901a004e3cc36c70e034742
  • ZIP SHA-256: 3dcc6aebb4b04c73c8da64ba7cbf46966e6cb93b948f87b2dff0881df10d9c14

What happens on merge

  • upstream/stable.json advances to track 1.136.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 33865990050 above. The skip is
gated by the auto-release label; see the build job if: in
.github/workflows/cron-build-and-release.yml.

@github-actionsgithub-actionsBot added the auto-release Cron release PR; safe to merge once you've reviewed label Sep 4, 2026
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@sbs44