Skip to content

feat(canvas): make Jetstream for Salesforce self-serve for Team plans - #2294

Merged
paustint merged 2 commits into
mainfrom
docs/managed-package-install-and-versions
Nov 17, 2026
Merged

paustint merged 2 commits into
mainfrom
docs/managed-package-install-and-versions

Conversation

@paustint

Copy link
Copy Markdown
Contributor

What

  • Flag: salesforce-canvas now defaults to on, so every team with the salesforceCanvas entitlement sees the Authorized Orgs card on the Team Dashboard.
  • Pricing copy: the Team plan lists the Jetstream for Salesforce managed package (pricing page and in-app billing page).
  • Managed package docs: replaces "contact support to install" with self-serve steps: authorize the org from the Team Dashboard, then install from a table of released versions with production and sandbox links. The installation password still comes from support.
  • Version table: sfdx-release.yml now rebuilds apps/docs/src/data/managed-package-versions.json from 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.
  • Docs sidebar: new Platforms section (Web Application, Desktop Application, Browser Extension, Salesforce Managed Package) and a new Web Application page with a platform comparison table. No URLs changed.

Notes for review

  • The release script change has only been run in dry-run, plus a real run of the generator against the Dev Hub. The first real package release will be the first end-to-end run.
  • The docs site deploys from the release branch, so a new package version shows up in the table at the next web release.
  • A release cut from a hotfix/* branch commits the version file there, so main catches up at the next package release from main.
  • The install steps (Install for Admins Only, completion email) and the platform comparison table were written from existing docs and code, not from a fresh install. Worth a read-through.
  • Version 0.1.0 is listed because it is a released version. It predates the custom permissions.

Testing

  • Docs build passes with no broken links.
  • jetstream typecheck passes. Feature-flag tests in types, shared-ui-utils and api pass.

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.

@jetstream-bot-agent jetstream-bot-agent Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 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.yml has not run end to end with this change. A release cut from a hotfix/* branch commits the regenerated version file to that branch, so main only catches up at the next package release from main.

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

@paustint
paustint merged commit 1b81050 into main Nov 17, 2026
17 checks passed
@paustint
paustint deleted the docs/managed-package-install-and-versions branch November 17, 2026 02:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant