Skip to content

chore(release): 1.124.03935 (vscode 1.124.0)#18

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

chore(release): 1.124.03935 (vscode 1.124.0)#18
github-actions[bot] wants to merge 1 commit into
mainfrom
release/1.124.03935

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: a0fd3bf182c29beca37542cc0470b580e6506b88ccdbc89b6c769ef308172076
  • ZIP SHA-256: 44e29f8303bd175516cb4f48abf4ee68e390311c3d996e34dbdb4acf772a939a

What happens on merge

  • upstream/stable.json advances to track 1.124.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 27448030586 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 Jun 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