fix: create single GitHub release with all VSIXs for monorepos - #181
Merged
Conversation
Previously, the workflow created one release per extension, which caused issues in monorepos where all extensions share the same version. The first extension would create the release, and all others would skip with 'release already exists', resulting in only 1 VSIX uploaded instead of all 17. Now the workflow: - Collects all VSIX files from all extensions into a single array - Creates ONE GitHub release with ALL VSIXs - Uses the first extension's version for the release tag - Lists all included extensions in the release notes This fixes the issue where nightly builds only had 1 VSIX in GitHub releases, which broke the promote-nightly-to-prerelease workflow that needs all VSIXs. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Contributor
Author
|
Nightly run from apex-language-support https://github.com/forcedotcom/apex-language-support/actions/runs/33673903963/job/100394194639 Night run from ci-testing repo: https://github.com/forcedotcom/salesforcedx-vscode-ci-testing/actions/runs/33668895766/job/100379180617 |
mshanemc
approved these changes
Sep 2, 2026
madhur310
added a commit
to forcedotcom/salesforcedx-vscode
that referenced
this pull request
Sep 2, 2026
The fix for monorepo GitHub release creation has been merged to main: salesforcecli/github-workflows#181 Updating from test branch @ms/fix-monorepo-github-release to @main. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Previously, the workflow created one release per extension, which caused issues in monorepos where all extensions share the same version. The first extension would create the release, and all others would skip with 'release already exists', resulting in only 1 VSIX uploaded instead of all 17.
Now the workflow:
This fixes the issue where nightly builds only had 1 VSIX in GitHub releases, which broke the promote-nightly-to-prerelease workflow that needs all VSIXs.
@W-23900552@