Repository navigation
feat(canvas): make Jetstream for Salesforce self-serve for Team plans - #2294
Conversation
Turns the salesforce-canvas flag on by default so every team with the entitlement sees the Authorized Orgs card, and lists the managed package in the Team plan features. The entitlement was removed from the Professional plan in Stripe, so this is Team and Enterprise only.
The managed package page told customers to contact support to install. It now covers authorizing the org from the Team Dashboard and installing from a table of released versions. Only the installation password still comes from support. The version table is rebuilt from the Dev Hub on every package release instead of appended to, so a failed or manual release corrects itself. A failure to rebuild it does not stop the release, because the package version already exists by then.
There was a problem hiding this comment.
🟢 Ready to approve
No correctness issues found in the release script, the docs component or the flag change; the one inline comment is a wording fix in the docs.
Reviewed: 850636c — 10 files, +325/-26. Focus: the release script's new docs-regeneration step and its failure handling, what the salesforce-canvas default flip exposes, and whether the new docs match the app's actual behaviour.
Not verifiable from the code (worth a human read before publishing):
- The Salesforce install-screen steps in
managed-package.mdx(Install for Admins Only, the completion email, what an upgrade preserves) describe Salesforce UI behaviour, not anything in this repo. sfdx-release.ymlhas not run end to end with this change. A release cut from ahotfix/*branch commits the regenerated version file to that branch, somainonly catches up at the next package release frommain.
Checked and clean: the regeneration step cannot fail a release after the package version exists, and an empty Dev Hub response cannot blank the docs file; the flag is only read by the Team Dashboard and personal Settings cards, both still gated on the salesforceCanvas entitlement; the docs' claims about authorization, sandbox coverage, the one-org limit and the "This org isn't authorized" screen match canvas-entitlement.db.ts, canvas.controller.ts and SalesforceCanvasOrgs.tsx; sidebar ids resolve and no slugs changed.
🤖 Final-gate review via Claude Code /pr-gatekeeper
What
salesforce-canvasnow defaults to on, so every team with thesalesforceCanvasentitlement sees the Authorized Orgs card on the Team Dashboard.sfdx-release.ymlnow rebuildsapps/docs/src/data/managed-package-versions.jsonfrom the Dev Hub (sf package version list --released) and includes it in the release commit. A failure to rebuild it warns in the job summary and does not stop the release.Notes for review
releasebranch, so a new package version shows up in the table at the next web release.hotfix/*branch commits the version file there, somaincatches up at the next package release frommain.Testing
jetstreamtypecheck passes. Feature-flag tests intypes,shared-ui-utilsandapipass.