@W-22108538 publish marketplace listing via forcedotcom/b2c-dx#464
Open
clavery wants to merge 2 commits into
Open
@W-22108538 publish marketplace listing via forcedotcom/b2c-dx#464clavery wants to merge 2 commits into
clavery wants to merge 2 commits into
Conversation
The bundled Swagger UI assets are loaded by the extension at runtime, so the dependency belongs in `dependencies` rather than `devDependencies`.
The Visual Studio Marketplace requires the extension's repository URL to live under a Salesforce-controlled org. Point package.json#repository at forcedotcom/b2c-dx and route each release through a review PR there: - publish.yml now opens a release PR in forcedotcom/b2c-dx (CHANGELOG splice + releases/latest.json marker) instead of pushing a release directly. Merging the PR is the manual gate; the b2c-dx on-merge workflow then creates the GitHub release that fires the marketplace publish workflows. - Extension README and a new PUBLISHING.md describe the flow and the manual fallbacks (open PR by hand, re-run a workflow, publish locally). - Step is gated on B2C_DX_PUBLISH_TOKEN; missing token soft-skips with a warning so unrelated CI doesn't break during rollout. The extension's bugs URL still points to this monorepo so issues continue to land here.
clavery
changed the title
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
1 participant
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.
Summary
The Visual Studio Marketplace requires the extension's
repositoryURL to live under a Salesforce-controlled org (forcedotcom). This PR points the marketplace listing at the newforcedotcom/b2c-dxrepo and routes each release through a review PR there before anything reaches the marketplaces.packages/b2c-vs-extension/package.json—repository→https://github.com/forcedotcom/b2c-dx.git;homepageupdated.bugscontinues to point at this monorepo so issues stay here..github/workflows/publish.yml— new step opens a release PR inforcedotcom/b2c-dx(branchrelease/b2c-vs-extension-X.Y.Z, CHANGELOG section spliced in,releases/latest.jsonmarker rewritten). Step soft-skips with a warning ifB2C_DX_PUBLISH_TOKENis unset, so unrelated CI is unaffected during rollout.packages/b2c-vs-extension/PUBLISHING.md(new) — full runbook: automatic flow, where to watch each step, manual fallbacks for each stage, and token rotation notes.packages/b2c-vs-extension/README.md— short callout that publishing happens out of `forcedotcom/b2c-dx`.Release flow after this lands
See the new `PUBLISHING.md` for full detail and manual fallback paths.
Required setup before this is functional
The `forcedotcom/b2c-dx` repo bootstrap is staged in a separate working copy (not in this PR). Manual steps required to enable end-to-end publishing are listed in the comment that accompanies this PR.
Test plan