Changelog
Release history for the sfp CLI — what changed in each version.
The sfp CLI carries its own version line, separate from sfp server's. Releases are published to npm as @flxbl-io/sfp and in the sfp docker images; see Install sfp. Under codev the CLI runs on the server, at the server's release.
Only releases that change the CLI are listed. A version absent from this page shipped no CLI-facing change. A version marked self-hosted is published to source.flxbl.io, where self-hosted deployments and the sfp docker images take it from.
November 2026
v52.44.0 — November 14, 2026
sfp server initandsfp server update, with thecloudflareTLS mode, write a Caddyfile that serves the main domain only to connections whose peer address is in Cloudflare's IP ranges and aborts every other connection. The peer address is read from the TCP connection, not fromX-Forwarded-For.sfp server updateforce-recreates the Caddy container so the regenerated Caddyfile is loadedsfp release --quickdeploydeploys the reconciled profiles of a source package after the quick deploy commits, as a full release does, without running Apex tests. A failed profiles-only deployment is logged and does not fail the release; with--json, each package'squickDeploy.profileRedeployreportsapplied,failedwith its message, ornot-neededsfp flows statusshowsoff (default)for a flow type that is off by default and not enabled for the project.sfp flows enableandsfp flows disableprint the list they wrote: the off-by-default flows enabled for the project, or the disabled flows, withnonewhen the list is empty
v52.43.0 — November 11, 2026
sfp build, when the project's test selection for diff packages isauthor-declared, reads thetests:commit footers and.codev/tests/files added or changed in each diff package's range from its checkout and binds those classes together with the lists sfp server resolves for the same commits, leaving out classes removed with/tests. A commit whose pull request could not be looked up no longer drops the package to its own test level; a range that cannot be read still does. Classes found only in the checkout are named in the build log as declared, read at build
v52.42.0 — November 11, 2026 · self-hosted
sfp validate org --testselection author-declaredruns, for each diff package, the test classes the author named intests: <package>:<Class>commit footers and in.yamlor.ymlfiles under.codev/tests/that the pull request adds or changes, with any file name. A file maps each package to a list of test classes; for a file that already existed, only the classes the pull request adds count. The classes run asRunSpecifiedTestswith coverage checked on the changed Apex, and a diff package whose Apex changed with no tests declared fails validation. Lists declared on merged pull requests that the deployment carries until release run as wellsfp build --testselection run-relevantalso skips binding the pull requests' test lists when the project's test selection isauthor-declaredsfp validate orgleaves Apex classes and triggers a diff package deletes inpre-destructive/orpost-destructive/out of the coverage scope, so they are no longer scored at 0%sfp install,sfp release,sfp validate organd the other commands that install source or diff packages redeploy reconciled profiles without running Apex tests; the profiles-only deployment no longer repeats the tests of the main deploymentsfp install,sfp release,sfp validate org,sfp package install,sfp sync organd the other commands that deploy metadata or install unlocked packages, run with sfp server, register each deployment in the org's deployment ledger on sfp server when Salesforce issues its id, then record its final status, times and counts. An entry carries the command, repository, environment, package and version, release candidate, domain and pipeline run. A failed write logs a warning; without sfp server nothing is writtensfp server pool scratch initmarks each scratch org it requests with the run's id in the org description and, once its creates settle, deletes the active scratch orgs carrying that id that the pool does not keep, such as a create Salesforce finished after sfp gave up on it. Orgs still being created are named in the log for deletion from the Dev Hub
v52.41.2 — November 10, 2026 · self-hosted
sfp install,sfp release,sfp validate organdsfp server pool scratch initrun pre and post deployment, validation and scratch org install scripts withCI=true,SF_CI_UPDATE_FREQUENCY_MS=10000andSF_CI_HEARTBEAT_FREQUENCY_MS=60000, so the sf CLI in a script prints deploy and retrieve progress as periodic status lines. A value already set in the environment is keptsfp server pool scratch init, run by sfp server, sends the server run's id with each scratch org it registers or leases, and sfp server marks the run's orgs still inPROVISIONINGasERRORwhen the run stops or fails
v52.41.1 — November 9, 2026
sfp build,sfp install,sfp releaseandsfp pushconvert and deploy with thesourceBehaviorOptionsof the project'ssfdx-project.json; before, the options applied only when the command ran in the project directory. An artifact built withdecomposeExternalServiceRegistrationBetadeploys the ExternalServiceRegistration with its schema, and a project withdecomposePermissionSetBeta2ordecomposeExternalServiceRegistrationBetano longer fails to resolve its metadata types.sfp buildlogs the active optionssfp builddiff packages andsfp sync orginclude a component decomposed by a source behavior option whole. A deleted file of such a component that is still in the project redeploys the component instead of staging a destructive change, andsfp sync orgkeeps the options in thesfdx-project.jsonit writessfp build, after a successful build, sends sfp server the package versions it built, and sfp server finds the components dropped without destructive changes. Against a server without that endpoint, the build runs the dropped-component analysis itself, as beforesfp project gc sync --execution-id <id>finds the components dropped on a branch since its last completed gc-ledger check and settles the branch's open cleanup entries. sfp server runs it on a checkout of the branch;--branchdefaults to the current git branchsfp server startandsfp server scalewrite the sfp server Node heap size toderived.envand log it with the worker memory plan:SFP_SERVER_MAX_OLD_SPACE_MBfrom.envwhen set, otherwise 75% ofSFP_SERVER_MEM_LIMIT(3 GiB when unset)
v52.41.0 — November 9, 2026
sfp server pool monitorhas a step, Refreshing Expired Sandboxes. In a pool with theAUTO_REFRESH_EXPIREDstrategy, it asks sfp server to refresh sandboxes flagged for refresh in place from the pool's source, longest-flagged first. A sandbox still inside its refresh interval waits; refreshes count against the pool's maximum provision per run, new sandboxes get what is left, and no refresh is requested after 3 minutes, leaving the rest for the next runsfp server pool config create --refresh-strategydefaults toDELETE_EXPIRED, which deletes an expired sandbox and creates a new one.sfp server pool statusreports sandboxes Refreshing and Flagged for refreshsfp push --packageandsfp pull --packageselect apackageDirectoriesentry without apackagename by its path; a package name match wins over a path.sfp pull --domainresolves each package of the domain by namesfp analyzeandsfp validate org, run with sfp server, take the project's AI assist settings saved in codev overconfig/ai-assist.yaml: enablement, timeouts, the number of suggested fixes and, when set, context files. Without saved settings, or when sfp server does not answer within 15 seconds, the repository file and then the defaults apply, and the log names the source
v52.40.0 — November 6, 2026 · self-hosted
sfp org flow cleanupchecks whether paused, failed or running flow interviews use the versions it would delete. When they do, it deletes nothing, lists the blocked versions with the command to run next, and exits with code 3.--dry-runreports the same as a warning and exits with 0,--delete-interviewsdeletes the paused and failed interviews of the old versions first, and--keep <n>keeps the newestnversions as well as the active one. A missing Manage Flow permission exits with code 4flowVersionCleanupon a source or diff package insfdx-project.json(keepVersions, at least 1, anddeleteInterviews, defaultfalse) deletes the older versions of the package's flows before the deploy, keeping the newestkeepVersionsand the active one. Versions that flow interviews use are kept with aFLOW_VERSION_IN_USEwarning and the install continues; check-only and dry-run installs only reportsfp install,sfp releaseand the other commands that install source packages, deleting a flow inpre-destructive/orpost-destructive/, check for flow interviews first and skip a flow whose versions are in use, leaving it active, withSkipped: in use (<n> interviews)in the tablesfp build, building a diff package from the furthest-behind environment's baseline, also includes the files changed since each environment ahead of that start without changing since the start, and lists them per environment. Files an ahead environment has that the head deleted are named in a warningsfp releaseandsfp installprintMissing <n> filesin the Baseline check table when a diff package starts before the environment's baseline but lacks files changed since that baseline, and warn with the files to delete when the environment has files the package's head deletedsfp buildandsfp sync org --diff-deployinclude the whole folder of a changed Experience Cloud site (DigitalExperience) component in a diff package, and a diff package holding only such components is no longer skipped as empty on install
v52.39.0 — November 4, 2026
sfp server pool config create --max-provision-per-runandsfp server pool config update --max-provision-per-run(1–20) set the most sandboxes one monitor run of the pool requests; sfp server applies 5 when it is not set.sfp server pool monitorreports the limit in its quota analysis and logs how many sandboxes later monitor runs will requestsfp server pool config create --confirmandsfp server pool config push --confirmconfirm, by its id, a change sfp server asks to confirm, assfp server pool config update --confirmdoes. A pool change that would request more than 10 sandboxes needs--confirm largeProvision. When a change needs confirmation, the command saves nothing and prints the--confirmflags to repeat it with
v52.38.1 — November 3, 2026
sfp install,sfp releaseand the other commands that install unlocked packages apply value changes to multi-select picklist fields before the install, as they do for picklist fields. A dependent multi-select picklist is skipped with a warning, keeping its field dependencies. Picklist values are compared with the org as written in source, so a value containing%no longer stops the update, and each install logs one line counting the picklist fields checked, updated, already matching and not yet in the orgsfp releasecandidate generate --built-package <package>=<version>, repeatable, fails before publishing when the release candidate would pin a different version of that package, or none, naming the package and both versions. When the newest tag of a package is not its highest reachable version, the command logs a warning naming bothsfp publishlogs whether an existing tag for a published version is on the built commit, and warns with both commits when it is not
v52.38.0 — November 1, 2026
sfp releaseandsfp install, deploying diff packages to an environment on sfp server, print a Baseline check table comparing each diff package's Source Version From with the environment's recorded baseline: Covered, Gap, No baseline or Couldn't check. A gap is logged as a warning with the commits and files in between, which the artifact does not contain; the deployment continues. When sfp server holds the environment's baseline instead of advancing it, the baseline update logs the held commitsfp server pool monitorhas a step, Observing Installed Commits, that reads the sfp artifact records of pool sandboxes with no recorded installed commit and records them on sfp server, and reports how many sandboxes it attempted, recorded and failed. Each read times out after 2 minutes, and the step starts no read after 5 minutes. A dry run, or a run outside a server task execution, reads nothingsfp server pool drainandsfp pool delete --allprintAlready draining: run <id>. No new drain was started.when the pool is already being drained. Draining every pool marks the pools already drainingsfp server pool config update --confirmconfirms, by its id, a change sfp server asks to confirm, and can be repeated, for example--confirm devHubChangewhen a pool's sandboxes were created by another DevHub usersfp server org registersends--devhuband--defaultonly when given, so registering a username again keeps the org's settings;--no-devhuband--no-defaultclear them. An update of an existing registration is reported as "Updated existing org registration"sfp sync org --jsonreports each deployed package'sversion, andanalysis.artifactRecords, the number of sfp artifact records read from the org
October 2026
v52.37.0 — October 30, 2026
sfp server scale --pool-workers(1–10) sizes thehatchet-worker-poolpool, which runs the per-sandbox syncs of a sandbox pool sync, each worker withHATCHET_POOL_WORKER_SLOTSslots (default 2), and writesHATCHET_POOL_WORKER_COUNTto.env. A tenant that has not sized the pool runs one worker. Without a flag the command reports the pool's configured and running counts with the other poolssfp server updatepre-pulls and recreateshatchet-worker-poolwith the other app services, and the worker memory budget derived from host memory counts the pool's workerssfp validate orginthoroughmode publishes to sfp server, for each diff package it built, the commit installed in the target org, the server baseline, the commit the diff started from as full SHAs, whether the org commit or the baseline set it and why, and the component count. The pull request comment and check text add a Diff packages section listing each package whose diff started at the org commit--repository, and its defaults fromSFP_REPOSITORY,GITHUB_REPOSITORYorGITLAB_REPOSITORY, is trimmed and lowercased before the command uses it, so a repository name that differs only in casing addresses the same records and locks on sfp server
v52.36.0 — October 30, 2026
sfp build, when the project's test selection for diff packages on sfp server iscodev-suggested, binds to each diff package with Apex the test classes accepted on the pull requests merged since its baseline, next to the suites bound inconfig/sfp_testsuites.yaml. A package with a commit in range whose pull request has no decision, was rejected or cannot be found, among other cases, keeps its own test level, and the build logs why.--testselection run-relevantbinds no accepted list for that buildsfp validate org --testselection codev-suggestedruns, for each diff package, the test list accepted on the pull request for the validated revision with RunSpecifiedTests, and checks coverage on the Apex the pull request changes. A package without a list accepted for that revision keeps its own test level, and a run that skips testing binds no listsfp validate suggest-tests --basebranchlists, for each diff package, the test classes that reach the Apex a pull request changes, read from the checked-out source without an org, and the Apex no test reaches.--testselection-depthsets how many hops of dependents it follows. With--pr-number,--commit-shaand--repositoryit publishes the lists to the pull request on sfp serversfp buildstarts a diff package at the furthest-behind baseline among the registered environments that have one recorded, and logs the environments it skipped for having none.defaultBaselineapplies only when no registered environment has a recorded baseline in the checkoutsfp releaseandsfp installwarn when a diff package is installed into an environment that has no recorded baseline for it, as the artifact contains only the changes since its build startsfp buildretries reading a package's published versions for the dropped components analysis twice, and when the read still fails logs a warning and skips that package's analysis
v52.35.1 — October 29, 2026
sfp validate orginthoroughmode cuts a diff package from the commit of the artifact installed in the target org when that commit is behind the server baseline, or when the package has no server baseline. An installed commit that is not an ancestor of the baseline leaves the baseline in place, andindividualmode is unchangedsfp sync org --from-orgcuts each diff package from the commit of the artifact installed in the org instead of from the server baseline
v52.35.0 — October 29, 2026
sfp sync org --diff-deploy, and the release diff deploy of--from/--to, runs no tests on a sandbox and RunRelevantTests on a production org when neither--testlevelnor--testsuiteis given, instead of RunRelevantTests on every org. When the org type cannot be read it runs RunRelevantTests with a warning. The chosen test level and its reason are loggedsfp sync org --testsuitetakes comma-separated names of suites inconfig/sfp_testsuites.yamland, with--diff-deployor--from/--to, deploys with RunSpecifiedTests over the suites' test classes plus any--apextests. An unknown suite, or suites that select no test class, fail the command, as does--testsuitewith a--testlevelother than RunSpecifiedTestssfp sync org --diff-deployno longer appliesdeploy_withsuite bindings to the package it builds from the diff, where they failed the buildsfp sfdmu run -o csvfilewith a source org (-s) exports records to CSV files in the--pathdirectory, instead of failing to find an org namedcsvfile. CSV as both source and target fails with a message, and a CSV export skips the rejected-row checksfp analyze --code-analyzer-scopetakeschanged-linesorfile. Withchanged-lines, the default when--pr-numberis set, only code analyzer violations that start on lines changed since--base-refcan fail the check; the other violations in changed files are reported as pre-existing.file, the default otherwise, gates on every violation in a changed file. A flag takes precedence overcodeAnalyzerScopeinanalyze.yamlor the server project configuration, and when the changed lines cannot be read the check gates on whole files with a note
v52.34.0 — October 28, 2026
sfp release --artifact-override "<package>:<key>=<value>[;<key>=<value>]", repeated per package, changes how a source or diff package deploys for that run without changing its artifact. The keys aretestLevel(RunSpecifiedTests, RunLocalTests or RunRelevantTests),testClasses(replaces the bound test classes),addTestClassesandremoveTestClasses(comma-separated Apex classes), andignoreComponents(comma-separatedType:FullName).--artifact-override-reasonis required with it, and it cannot be combined with--checkonlyor--quickdeploy. The release checks every override before the first deploy and prints an Artifact Overrides group for each package; see Artifact overridessfp validate orgcuts the Test selection section of the pull request comment to the comment's row limit, together with the other sections. A package whose suggested tests were cut keeps its full count and points to the full validation run for the list and itssfp_testsuites.yamlsnippet; as a last resort the section is left out with a notice
v52.33.0 — October 28, 2026
sfp validate org --testselectiontakesrun-relevant(default) orcodev-suggested. Withcodev-suggested, each diff package's build suggests test classes for the Apex added or changed between the merge base with--baseRefand the validated commit, following dependents up to--testselection-depthhops (1–5, default 2), with the reason each test was picked. A changed class no test reaches falls back to a test named for it (XTest,X_Test,XTests,X_Tests,TestX,Test_X), and a class of static fields only gets one covering test. The suggestions, the Apex no test reaches and ansfp_testsuites.yamlsnippet are published with the validation result and shown in its pull request comment. They change no test level
v52.32.1 — October 28, 2026
sfp validate orgscopes per-class coverage of a diff package to the Apex classes and triggers it deploys, excluding test classes and interfaces, including for artifacts built by older CLIs. A diff artifact records only the diff's triggers and changed non-test classessfp validate orgat RunRelevantTests no longer fails per-class coverage for Apex that Salesforce reports as unchanged in the org, unless Salesforce names it in its own coverage warnings, and logs the classes it skips. Changed Apex that no test covers still fails at 0%
v52.32.0 — October 27, 2026 · self-hosted
sfp org login --serverandsfp sandbox loginlog that the login uses an access token that expires in about two hours, and that running the command again reconnectssfp org login --server, and the commands that connect to an org through sfp server, fail with "Only owners and application tokens can get access tokens for orgs registered in codev. Ask an owner." when the server returns no access token for the orgsfp build, reporting a build to sfp server, replaces the plan, in-progress packages, failure and completion time recorded by an earlier run of the same commit and domain, and removes the packages the new run rebuilds from the earlier completed and failed lists. A run with nothing to build leaves a Completed domain as it is, and a Skipped write, or a Failed write without package results, no longer changes a Completed domain
v52.31.1 — October 26, 2026 · self-hosted
sfp sandbox createwith--sourcesandbox, orsourceSandboxNamein the definition file, does not send the activation user group, which Salesforce rejects on a clone, and logs that the clone copies the source sandbox's userssfp sandbox updaterefreshing from a source sandbox does not send--activation-user-group, and clears an activation user group stored on the sandbox's SandboxInfo record, which Salesforce rejects next to a source. Its JSON result includesfromSource
v52.31.0 — October 26, 2026
sfp sync orgbuilds the packages it syncs at their version floor: the last known version, or the version promoted in the DevHub when that is higher, with a build number taken from the current time. An unlocked package with no usable floor fails its build with a message to deploy it as source or to establish a baseline, version tag or promoted version firstsfp sync orgdeploys the packages that built when others fail to build. A package whose build failed, or that depends on one that did, is listed as✗ Build failedwith its error, counted as failed in the summary and returned inbuildFailureswith--json.--reset-trackingresets source tracking only when the sync has no errorsfp repo workspace-tree --modetakesincrementalorfull(defaultfull).incrementalbuilds the checked-out branch head by applying the Git changes since the stored tree's commit, and falls back to a full build when the stored tree is missing, comes from another builder version or from a commit the repository does not have. Either mode publishes the tree only while its commit is still on the branch, and a failed publish fails the command instead of logging a warningsfp repo return-hotfix --return-idcreates or recovers the return pull request for a managed hotfix recorded on sfp serversfp org retrieve by-namewarns, when it retrieves a Profile, that a profile retrieved on its own carries only profile-level settings and user permissions, and namessfp org profile retrievefor the full profilesfp server scale --agentic-workers(0–10) sizes thehatchet-worker-agenticpool, which runs the workflows named inSFP_AGENTIC_WORKFLOWSwith every subprocess in a per-run container, and writesHATCHET_AGENTIC_WORKER_COUNTto.env. When the pool is sized above 0, the command warns ifSFP_RUN_LAUNCHER_REPLICASis not set above 0, as the pool needs the run launcher. Without a flag it reports the agentic pool's configured and running counts with the other poolssfp server startandsfp server updatecreate arun-workspacesvolume for the tenant.sfp server updatepre-pulls and recreateshatchet-worker-agenticandrun-launcherwith the other app services, and the code analysis concurrency derived from host memory accounts for agentic workers
v52.30.0 — October 22, 2026 · self-hosted
sfp report,sfp cherry-to runand the other commands that run an AI agent address Cloudflare AI Gateway models by their models.dev catalog id, so the approved gateway models areanthropic/claude-sonnet-5andanthropic/claude-opus-4.8. A dashed id such asanthropic/claude-opus-4-8, passed with--modelor configured on the AI integration, is rewritten to the catalog id before the run- The sfp docker image and the sfp binaries run on Node.js 22.23.4, the October 2026 Node.js security release
v52.29.3 — October 20, 2026 · self-hosted
sfp server updatechecks hatchet-db, as it already did a self-hosted supabase-db, for databases whose recorded collation version no longer matches the operating system's after a postgres image change, and rebuilds their indexes before migrations run. When hatchet-db has a mismatch,hatchet-engineandhatchet-dashboardare stopped for the reindex and started again with the other services
v52.29.2 — October 18, 2026
sfp sandbox createaccepts--license-type(Developer, Developer_Pro, Partial or Full, case-insensitive),--template-id,--history-days,--apex-class-idand--auto-activate/--no-auto-activate. A flag takes precedence over the definition file, and the license type is sent to Salesforce in its uppercase form, so a Developer_Pro, Partial or Full request is no longer created as a Developer sandbox. An unknown license type fails the commandsfp sandbox createfails before creating anything when the source sandbox is not found in the production org, instead of creating a sandbox from productionsfp sandbox reset-passwordsauthenticates to the sandbox through sfp server when a server is configured, with the new--production-username(-p) naming the production org, and through the DevHub otherwise. It reports the reset as requested for the group members rather than as sentsfp validate orgrounds each Apex class's coverage down to a whole percent before checking the 75% per-class minimum for packages without bound test suites, so a class covered at 74.5–74.99% fails validation instead of passing
v52.29.1 — October 15, 2026
sfp org drift analyzeretrieves a package with up to--large-package-thresholdcomponents in one Metadata API retrieve instead of one retrieve per component, and retrieves one package at a time:--package-concurrencydefaults to 1 instead of 10.--package-retrieve-timeout(default 45) and--retrieve-timeout(default 150) set, in minutes, the limit for one package's retrieve and for the whole retrieve phase; a package not retrieved within them is reported asretrieve-incompletesfp releasepromotes packages whenpromotePackagesBeforeDeploymentToOrgmatches the target org's username, alias or environment name, ignoring case, and requires--devhubaliasfor every release definition where it matches. When it does not match, the release logs that packages will not be promoted. Aliases that differ only by case and point to different orgs fail the release as an ambiguous promotion targetsfp releasefails a package whose promotion fails, instead of logging a warning and installing it unpromoted. A package version that is already promoted is still skippedsfp release --jsonreportsversionInOrgas the version the org held before the release, ornullwhen the org held none, instead of the version just installedsfp buildskips reporting dropped components to sfp server when its branch resolves toHEAD(a detached checkout), and logs a warning to pass--branchsfp cherry-to runuses the provider's strongest approved model,claude-opus-4-8on Anthropic, Cloudflare AI Gateway and Google Vertex. A model configured on the AI integration or in the cherry-to policy no longer replaces itsfp server start,sfp server updateandsfp server scalederive a memory budget for the Hatchet workers from the host's memory (host memory less 5.5 GiB, and at least half of it), with a PMD heap and a code analysis concurrency sized from it, and write them toderived.envin the tenant directory.SFP_WORKER_MEMORY_BUDGET,SFP_PMD_MAX_HEAPandSFP_CODE_ANALYSIS_MAX_CONCURRENTset in.envtake precedence. On Podman with systemd and cgroup v2 the workers share the budget insfpworkers.slice; elsewhere each worker is capped on its own, with a warning. The commands warn when the host has no swapsfp server pool scratch initlogs that a scratch org is no longer active in the DevHub and skips its deletion when cleaning up an org that failed preparation or registration and was already deleted, instead of logging a TypeError
v52.29.0 — October 12, 2026
- A diff package built by
sfp buildincludes the related components a changed component needs to deploy, even when git does not report them as changed: the parent object of a changed MasterDetail field, every MasterDetail field of a changed object, the objectTranslation of a changed fieldTranslation, the Bot of a changed BotVersion, the schema of an ExternalServiceRegistration, the permission set of a changed decomposed part, and theflowDefinitionsof a changed flow from each Translations file in the package. A related component in another package's directory, or outside every package directory, is left out with a warning that names it sfp validate orgpublishes each Apex test class with its methods to sfp server: duration, class path, and for each method its outcome, duration, declaration line, and the message and stack trace of a failure. A package whose test run found no tests is published as passed with an empty class listsfp server pool monitorrestores a pool sandbox that reconciliation marked ERROR when Salesforce lists it as live again, to ASSIGNED, AVAILABLE, ACTIVATING, REQUESTED or PROVISIONING according to its record. When Salesforce returns several sandbox processes for one name, the newest is used. Sandboxes in the new SYNCING status count as available capacity when the monitor computes the replenishment deficitsfp pool fetchprints the server's warning when the sandbox it assigns was taken from a branch sync still in progress.sfp server pool statusshows a Syncing row and accepts--filter-status SYNCING, andsfp pool listmarks SYNCING sandboxes
v52.28.0 — October 11, 2026
sfp apextests resume --partialreturns the method results recorded so far, without coverage, when the test run is still in progress, instead of waiting for it to finish. The--jsonsummary reportsisComplete, and for an unfinished runrunStatus,methodsEnqueuedandmethodsCompleted. The dashboard outcome of an unfinished run is Failedsfp apextests resume --coverage-max-test-methodsskips the reporting-only per-test coverage fetch when the run has more test methods than the limit, and--results-fetch-timeout-minutessets the time limit for each result fetch attempt. They fall back toSFP_APEX_COVERAGE_MAX_TESTMETHODSandSFP_APEX_RESULTS_FETCH_TIMEOUT_MINUTES, then to 5000 and 10sfp validate org --ref --baseRefandsfp impact releaseconfig --filterByChangesInBranchresolve both refs to commits before computing the merge base. A ref that is empty, starts with-, contains spaces or control characters, or is not found in the repository fails the command with "Git ref ... can't be used"sfp changelogissue and commit links and the workflow run link in thesfp validate orgreport are built from the repository's GitHub host, taken fromGITHUB_SERVER_URLwhen set, instead of alwaysgithub.comsfp server callback postsends GitHub comments and issue updates toGITHUB_API_URLwhen set, otherwise to the API of the GitHub host inGITHUB_SERVER_URL(api.<host>for GHE.com,<host>/api/v3for GitHub Enterprise Server), instead of alwaysapi.github.comsfp report --provider github-copilotuses the token inCOPILOT_TOKENorGITHUB_TOKENdirectly and accepts only an OAuth token (gho_) from OpenCode's GitHub Copilot sign-in. Any other token fails with "This token can't be used for GitHub Copilot"sfp report --provider cloudflare-ai-gatewayruns with each approved gateway model (anthropic/claude-sonnet-5,anthropic/claude-opus-4-8), including image and PDF input; previously onlyanthropic/claude-sonnet-5resolved
v52.27.0 — October 5, 2026
- A test suite in
config/sfp_testsuites.yamlcan list the source or diff packages it deploys with underdeploy_with.sfp buildexpands the suites bound to a package into a list of test classes and stores it in the artifact. A binding to a package missing fromsfdx-project.json, to a package of another type, or from a suite that selects tests by tags fails the build sfp release,sfp installandsfp validate orgdeploy a source or diff package with Apex whose artifact carries bound test suites withRunSpecifiedTestsand that list of test classes. An explicittestLevel,skipTestingandisOptimizedDeployment: falsetake precedence over the bindingsfp validate orgfails a bound package when any Apex class or trigger in its scope is covered below 75%, or below the package's coverage threshold when that is higher, by the bound suites alone. The failure names the classes below the threshold and the suites that ran- The
sfp validate orgreport lists only the packages that failed, captioned "N of M failed", and reports a coverage failure only for a package whose coverage verdict failed sfp buildandsfp quickbuildskip a package whose build commit is an ancestor of the commit that last published it on the same branch, so the package is not published again under a new version. Other packages in the run still build; skipped packages are listed under "Packages skipped as superseded" and inbuildResult.jsonwithstatus: skippedandskipReason: supersededsfp buildandsfp quickbuildacceptversionNumber: 0.0.0.LATESTon a dependency to a package of the same project whose version is0.0.0.NEXT. When the dependency is not part of the build, it resolves to the version last published on the branch as recorded by sfp server, and that exact version is written into the dependent's artifact. The build fails when the published versions cannot be read from sfp serversfp releasetreats a deployment that stops with an error before every package is attempted as failed: the packages not yet deployed are reported as failed instead of skipped, later release definitions are not deployed, and the command exits non-zero. Writes of deployment information that conflict with a concurrent release are retriedsfp repo patch --releasedefinitions <domain>/<release>refuses a release candidate that is aborted or has an artifact without a version. A reference such ascore/RC-A.jsonis fetched from sfp server unless a file exists at that path
September 2026
v52.26.0 — September 30, 2026
- A diff package with Apex that sets
isOptimizedDeployment: falsein its descriptor deploys withRunLocalTestsinsfp release,sfp installandsfp validate org, instead ofRunRelevantTests.skipTestingstill takes precedence sfp validate orgprints the deployment'sTestLevelfor each package when tests run as a separate step after the deploymentsfp insights loginscounts unique users with a single aggregate query, so the report no longer fails for orgs with more users in the 30-day window than one query batch returnssfp server pool scratch initauthenticates each scratch org leased from a snapshot pool before preparing it. An org that cannot be authenticated is reported as an error in the pool failure summary and is not deleted
v52.25.0 — September 29, 2026
sfp release --quickdeploy <deployId> --payload-fingerprint <fingerprint>commits the validation thatsfp release --checkonlyreturned instead of deploying the package again. Pre-deployment steps are skipped, post-deployment steps run as usual, and the release is recorded as a plain release is. The release is refused when the fetched artifact's fingerprint differs from--payload-fingerprintsfp release --quickdeploy-fallbackdeploys the package in full when Salesforce rejects the validated deploy id. Without it, a rejected id fails the release and leaves the org unchangedsfp sfdmu runscans the target reports sfdmu writes, prints a records summary, and fails when any row was rejected.--no-failonrowerrorsreports rejected rows as a warning without failing. The--jsonresult carries the count underrowFailuressfp sfdmu run,sfp pushandsfp installprint "Command completed, but N record(s) were rejected by the target org" in place of "Command succeeded." when sfdmu rejected rowssfp publishskips a version already in the registry only when the stored artifact was built from the same commit and package version id. A different source fails the publish withVERSION_COLLISION, an artifact whose source cannot be read fails withIDENTITY_UNVERIFIED, and neither records release metadata, the version baseline or git tags. An artifact the internal registry rejects this way is not published to the external registrysfp server environment lock --hatchet-run-idnames the Hatchet run that owns the lock; the server releases the ticket once that run ends, including while it is still queuedsfp analyzeon a pull request reuses the previous architecture and version-assist verdicts when the net diff is unchanged or the change since the last analysed commit is not significant. SetincrementalReviewEnabled: falseinanalyze.yamlor the server project configuration to always run a fresh analysis
v52.24.0 — September 27, 2026 · self-hosted
sfp release --checkonlyvalidates a single-package domain against the target org with one check-only deployment and returns the validated deploy id. Nothing is committed to the org and no release history is recorded; it cannot be combined with--dryrunsfp release --jsonreports the deployment error for a failed package instead ofnull- The CLI adds the operating system certificate store to the certificate authorities it trusts, so
sfp auth loginandsfp server updatereach an sfp server whose certificate is issued by a private CA. On Node.js earlier than 22.19, setNODE_EXTRA_CA_CERTSinstead sfp auth login --global-authcontinues when the server configuration cannot be read, using--sfp-server-urlas the sign-in callback basesfp server callback postaccepts"comment": { "key": "<key>" }in the context to keep one comment per pull request, updated in place, on GitHub and Azure DevOpssfp validate orgreports a run with nothing to deploy as "No changes to validate" instead of "Validation passed". The check still concludes as successsfp insights connected-apps --jsonreturns the org's external client apps underexternalClientApps, and underhiddenManagedAppsthe number of managed connected apps left out without--include-managed. When the org cannot list external client apps, the reason is given underexternalClientAppsSkippedsfp insights contentlists built-in list views that Salesforce reports without an object asStandard views (no object)
v52.23.1 — September 24, 2026
- Improvements to check-only validation in
sfp validate org sfp validate orgnow respectsdependencyOnDomainssfp validate org --deploywithtestsalways runs Diff packages withRunRelevantTestssfp sync org --releaseconfigaccepts multiple domains and syncs all of them
v52.23.0 — September 23, 2026 · self-hosted
sfp validate orgbuilds its validation check from the same report as every other surface, laid out for the platform configured on sfp serversfp validate orgno longer writes a second check for a run sfp server already reports- Validation results carry per-class coverage for each package
sfp server callback postkeeps one validation comment per Azure DevOps pull request, updated in place
v52.22.0 — September 23, 2026
sfp releasecandidate generateno longer fails for a source-only release configuration with no promotion target- String replacement globs match the same way on install,
sfp pushandsfp pull sfp pushreports only the replacements that changed a file, and--jsonlists the rules that matched nothing underunmatchedRules- Non-regex replacement values are applied as written, so a
$in a value is kept
v52.21.2 — September 22, 2026
- New
sfp releasecandidate sync-checklists the domains on a branch whose last release to an environment did not succeed sfp releaserecords a release attempt for each domain on sfp server- Improvements to AI credential handling in
sfp analyze
v52.21.1 — September 22, 2026
- Source packages with
isOptimizedDeployment: falsedeploy withRunLocalTestsagain - Fixes to command aliases and topic descriptions for
sfp pull,sfp push,sfp sfdmu run,sfp server review-envsandsfp server variable
v52.21.0 — September 21, 2026
sfp release --branch <branch>releases the latest published release candidate of each domain on a branch tracked by the project, in place of--releasedefinitionor--releasecandidate; the three flags are mutually exclusive.--repositoryand--sfp-server-urlare both required with it, and--domain— repeatable — restricts the release to the domains named. A candidate is eligible only when its domain build succeeded and the candidate was not aborted.sfp release --branchprints the resolved domain, release candidate and commit as a table, then the branch head commit and the domains whose candidate commit differs from it, and lists the domains skipped for want of an eligible candidate. The same resolution is carried underbranchResolutionin the--jsonoutput.sfp release --branchfails before it releases anything when the branch is not among the branches tracked in the project's server configuration, when a--domainis not one of the branch's domains, or when no selected domain has an eligible candidate.
v52.20.1 — September 20, 2026
sfp sandbox createsets a sandbox's add-on features fromfeaturesin the--definition-filedefinition — an array of strings such asSandboxStorage. When the definition also names asourceSandboxName, the features recorded on that source sandbox take precedence over the ones in the definition.sfp sandbox createfails when the lookup ofsourceSandboxNameerrors, instead of warning and creating the sandbox without a source. A source sandbox that simply returns no record is still reported as not found, and creation continues without a source.
v52.20.0 — September 20, 2026
- A source or diff package that carries a Flow in
pre-destructive/flows/orpost-destructive/flows/has that Flow deactivated and every one of its versions deleted through the Tooling API before the metadata deployment, and the Flow is dropped from that deployment. The deletion is not part of the deployment transaction, so it is not undone when the deployment fails. See Destructive changes. - A Flow that is absent from the org is recorded as already absent and installation continues. A lookup, deactivation or deletion failure is reported as a warning, that Flow's delete is skipped, and the remaining components are installed. Progress is folded into a
Destructive Flowslog group that closes with a table of each Flow, whether it was deactivated, how many versions were deleted, and the result. enableFlowDestructiveHandlingin a package'ssfdx-project.jsondescriptor turns that handling off for the package, restoring plain metadata deletion. It defaults to true and is independent ofenableFlowActivation. The handling is also skipped, and the plain Flow member retained, for a check-only deployment and for a dry-run installation.sfp repo diff --create-packagestages two synthetic source packages when the changed packages disagree onenableFlowDestructiveHandling— the metadata from the packages that keep it first, then the opted-out metadata in<name>-flow-optout— and each is deployed separately. Packages that agree still produce one synthetic package.- An installation whose components are all removed — a package whose only members were destructive Flows — completes without a metadata deployment rather than submitting an empty one.
sfp org flow activate,sfp org flow deactivateandsfp org flow cleanupescape--developernameand--namespaceprefixin the SOQL that looks the Flow definition up. An explicitly empty--namespaceprefixnow matches only flows with no namespace; it was previously ignored, matching any namespace. Each command's output is folded into a log group.sfp org flow cleanuplogs each version as it is deleted, with its position in the run, and names the attempt and the Salesforce error when a deletion is retried.
v52.19.2 — September 19, 2026
sfp server updatepauses Hatchet worker assignments in bounded cycles instead of holding one pause for the whole drain.--pause-timeoutsets the maximum seconds of a single pause, defaulting to 600; when it expires without a confirmed drain the assignments are restored for a 300-second cooldown and a new cycle starts, until the drain is confirmed or--drain-timeout— still 3600 seconds by default — is spent.--pause-timeoutmust not exceed--drain-timeout, and both flags reject a value below 1.sfp server updateupdates the tenant files and pre-pulls the new images before it pauses assignments, rather than pre-pulling in parallel with the drain, and recreates Caddy inside the pause window.sfp server updateaborts before it stops any service when no drain is confirmed within that budget. Assignments are restored first, and the error names the number of pause cycles, the running and queued workflow counts, and the names of up to 100 running tasks.sfp buildcontinues when a package it has just built is an ordering-only dependency of a package still to be built — a source, diff or data package of the same project, which dependency resolution removes from the dependent's resolved dependency list. Stamping the completed version onto a dependency that is no longer listed previously threw and failed the build.sfp buildfails on an invalidpreDeploy/replacements.ymlin a package: a missing or emptyname,globorpattern, or an environment value that is not a string, boolean or number. It previously logged a warning and built the package without its replacements.- Replacement YAML — a package's
preDeploy/replacements.yml, and the file passed tosfp push --replacementsoverride— keeps an unquoted date such as2026-09-17or timestamp such as2026-09-17T12:34:56+05:30as its original text instead of reading it as a date. A boolean or numeric value is applied as its text, and a null, array or object value is a configuration error. - A replacement whose value is an empty string is applied, removing the matched text, and an exact org alias takes precedence over
defaulteven when the alias value is empty. An empty value was previously treated as no value, leaving the pattern in place. This coverssfp pushand the source-package install path thatsfp installandsfp releaserun. sfp pushtreats a package'spreDeploy/replacements.yml, or--replacementsoverride, as authoritative for that package: thereplacementsentries insfdx-project.jsonno longer apply to it as well. A package with no package-level configuration keeps the project-level replacements, and in a push carrying both kinds those project rules are matched against project-relative paths, so a hidden directory in the checkout path no longer suppresses a match.sfp push --replacementsoverridemerges the override entries into the package configuration by replacement name, the override's environment values taking precedence, instead of applying both lists.sfp pushfails withUnable to prepare push replacements: <reason>when it cannot prepare the replacements. It previously logged a warning and pushed the source without them.sfp pushapplies package replacements to every file a component carries rather than only its top-level content path, and no longer counts a file in a sibling directory whose name starts with the package directory's name as being inside the package.sfp pushremoves the temporary conversion context it creates for replacements once the deployment is submitted, including when the conversion or the submission fails.- The header line every command prints carries
-Build:<number>once when a build number is set, and omits it otherwise. It previously repeated the-Build:label, and printed an empty one when no build number was set.
v52.19.1 — September 17, 2026
sfp analyzeprints the analysis result as JSON only when--jsonis set. It previously printed the raw result to stdout alongside the human-readable output whenever a linter named in--fail-onhad a blocking finding or could not run.- The
[AI_RESPONSE]entry carrying a prompt's full response — written by the architecture and version-assist linters ofsfp analyze— is logged at debug level rather than info, so it no longer appears in the default console output. It is dispatched straight to the run's logger, so a file or log sink attached to the run still receives it.
v52.19.0 — September 16, 2026
sfp server updatelogs the Hatchet worker-assignment commands it runs over SSH against a remote host, and their output, at debug level rather than info. A command that exits non-zero is still reported at error level.sfp server updatenames the worker-assignment pause before it runs, and on resume reports how many workers had their assignments restored and how many registrations the restart replaced. That report is printed whether the update finishes or fails.
v52.18.2 — September 15, 2026
sfp server callback post --context-idtakes the UUID of a callback context held on the server, in place of the inline JSON on--context. The two flags are mutually exclusive and exactly one is required; the command reads the context from the server with the server URL and application token before it posts.sfp server callback postfails before posting on a--context-idthat is not a UUID, a--contextthat is not valid JSON, a context that is not a JSON object, and a context whoseusername,accessLevel,targetOrg,taskId,taskTypeormessageis not a string.
v52.18.0 — September 15, 2026
- A package install that composes partial CustomObject metadata — layout assignments from
mutators/layout-assignments.yml, and the search-layouts contribution that augments them — carries the target org's object settings into that partial: the supported feature flags,description,gender,startsWith, each targeted record type'sdescription, and the name field'strackHistoryandtrackFeedHistory. A CustomObject deployment resetsallowInChatterGroups,enableActivitiesandenableReportsand clearsdescription,genderandstartsWithwhen they are omitted, so the composed partial previously reset them on install. - That composition stops before deployment when the org's CustomObject metadata is incomplete — a missing label or
nameField, an AutoNumber name field with nodisplayFormat, a value that is not a valid boolean, or anenableBulkApi/enableSharing/enableStreamingApigroup that is inconsistent — instead of composing a partial that would reset a property. - Each setting is written only when the Metadata API version supports it. The version is the one the install deploys with, falling back to the package's
apiVersionand then to the component set's. sfp validate orgruns its AI error analysis before it publishes the validation result, so the analysis reaches the published result and its markdown as well as the CI check. It previously ran only while the CI check was being created.sfp validate orgcancels the AI error analysis at its timeout — three minutes, unlesserrorAnalysis.timeoutin the AI configuration sets another, in milliseconds — and aborts the agent session rather than leaving the request in flight. A transient failure is retried up to three attempts, after 5 and 10 seconds, within that same deadline.- The validation markdown records
AI error analysis unavailable: <reason>when the analysis produces no insight, where the reason isno credentials,timed out,unparseable response,attempts exhaustedoranalysis failed. sfp validate orgreads its AI configuration from the validation worktree —config/ai-assist.yaml, then the.ymlspelling, thenconfig/ai-architecture.yamland.yml— rather than from the directory the command was started in. The analysis is skipped when the run failed because no changes were detected in the packages to be built, and runs whenever--opencode-serveris set.sfp releasecandidate unbundleremoves the file when a conflict has no copy of it on the side--conflict-strategyselects, instead of resolving markers in a file that side deleted.sfp releasecandidate unbundlefails when it cannot resolve the new SHA of a cherry-picked commit. It previously logged a warning and continued, leaving the deployment step lineage incomplete.sfp releasecandidate unbundle-analyzecounts only re-applied commits in the kept-commit total it prints and returns. A commit that turned out empty after conflict resolution, and was skipped, is no longer counted.sfp auth loginandsfp server auth loginserve branded sign-in result pages on the CLI's loopback receiver. The failure page escapes the detail returned by the authorization server and namessfp auth loginas the command to run again.sfp publishincludes the repository and an ISO 8601 timestamp in the webhook events it triggers on sfp server. The repository is read fromSFP_REPOSITORY,GITHUB_REPOSITORYorGITLAB_REPOSITORY, in that order.
v52.17.0 — September 11, 2026
sfp publish --pushgittagpushes the tags for all published packages in a singlegit push, instead of one push per package. A transient failure — a dropped connection, an unresolved host, an HTTP 5xx — is retried three times, after 2, 5 and 15 seconds. An authentication, permission, protected-tag or ruleset rejection is not retried.sfp publishcompletes when the tag push does not, instead of failing the run. It lists the tags that still need pushing and thegit push origin refs/tags/…command that pushes them, with remote URLs and credentials stripped from the reported error, and leaves the--gittaglimitand--gittagagecleanup for that retry.sfp releasecandidate unbundle --source-branchdefaults to the branch recorded on the release candidate, falling back tomainwhen the candidate records none. It previously always defaulted tomain. An explicit value still takes precedence.sfp releasecandidate unbundleremoves its temporary worktree when the run fails as well as when it succeeds, and raises a failure through the command's own error handling — so--jsonreports it — instead of exiting immediately.sfp releasecandidate unbundlereports how many manual deployment steps were re-anchored onto the rewritten branch and how many were flagged for review. The command fails when the server cannot record that anchor migration, after the branch has been pushed.
v52.16.1 — September 10, 2026
sfp server updatepauses Hatchet worker assignments before it drains, then waits only for workflows that occupy a worker slot. Queued tasks are no longer waited on; they stay pending and run once the workers return. The drain is checked again after the image pre-pull and the Caddy recreation, and the paused workers are restored when the update finishes or fails.sfp server updateaborts before it stops any service when the drain fails or the running-workflow count cannot be read. It previously logged a warning and continued with the update.--forcestill skips both the pause and the drain, and--drain-timeoutstill bounds the wait, in seconds, defaulting to 3600.sfp scratch deletecompletes without error when the Dev Hub holds no active scratch org record for the username. The lookup previously raisedNo ActiveScratchOrg found for username <username>, which the command reported as a missing org or a permissions failure.
v52.16.0 — September 8, 2026
sfp org login --server --default-devhubaccepts--repository(alias--repo) to authenticate with the DevHub selected for that project, and fails when the server resolves the DevHub from anywhere else.sfp server org get-default-devhubtakes the same flag. Both name where the DevHub came from — the project's default DevHub, a legacy project registration, or the tenant default.sfp scratch loginwithout--devhub-usernamehas the server resolve the DevHub that owns the scratch org, instead of trying the tenant default DevHub and then each registered DevHub in turn.sfp sandbox loginwithout--production-usernamehas the server resolve the production org bound to the sandbox, instead of trying each registered production org in turn. A sandbox registered without a production connection logs in, and the output omits theProduction Orgline.sfp server pool monitornames the pool it is reconciling when it reads sandbox state from Salesforce, so the state covers that pool's own instances rather than every sandbox under the Dev Hub.sfp scratch deletefails when the Dev Hub rejects the deletion, instead of reporting success. A username with no active scratch org record in the Dev Hub is left alone.--passphraseon the SSH-based server commands —sfp server init,start,stop,status,logs,scaleandupdate— is passed to the SSH connection, so an encrypted--identity-filecan be used. The key is read when the flags are parsed and is no longer written into the lifecycle configuration that debug logging serialises.- Those same commands report an SFTP error raised while checking for a directory on the remote host, instead of treating the directory as absent.
v52.15.1 — September 7, 2026
sfp server updateandsfp server initcopy the Supabase schema to a remote host through a temporary archive that is extracted and then removed. Removing it now tolerates an archive that is already gone, so a repeated or concurrent run against the same tenant directory no longer fails after the extraction has succeeded.
v52.15.0 — September 4, 2026
sfp auth loginandsfp server auth loginsign in to flxbl cloud when no server URL is given, through the global auth service over OAuth 2.1 with PKCE and a loopback receiver bound to127.0.0.1.--sfp-server-urlno longer defaults tohttp://localhost:3029.sfp auth login --sfp-server-urlreads the server's/sfp/api/configbefore signing in: a server that reports itself as self-hosted routes the sign-in to the auth service it publishes, and an unreachable URL fails before a browser opens.--global-authand--no-global-authforce either service and no longer carry a default.sfp auth loginprints the sign-in URL before it opens a browser, so a session where no browser opens can still complete the sign-in. On the self-hosted path the browser is redirected to the server's hosted/auth/callbackpage, which shows ansfp1_login code to paste into the terminal when it cannot reach the CLI's loopback.sfp installandsfp releasegroup the output of each pre- and post-deployer and of thepreDeploymentandpostDeploymentscripts, and keep the component checksum skip pre-fetch lines inside the eligibility group.
v52.14.3 — September 2, 2026
sfp analyze --output-format githubrenders code-analyzer and architecture findings as a Markdown list — severity, rule, location and gate on the first line, the message on the next — instead of an HTML table.--output-format markdownkeeps its tables.sfp analyzeandsfp project version suggestpass the architecture and version-assist instructions to the AI as its system prompt, rather than prepending them to the pull request content being analysed. The architecture instructions return the empty JSON result the parser reads when there is no architecturally significant change, in place of a plain sentence.
v52.14.2 — September 2, 2026
sfp project preflightreports a repository with nosfdx-project.json, or one that cannot be parsed, as anot-configuredstatus with the cause listed under issues. Previously the read error aborted the run.
v52.14.1 — September 2, 2026
sfp cascade merge-assistno longer stops responding when the AI agent asks to access a directory outside the working tree. The request is answered instead of left pending.
v52.14.0 — September 1, 2026
sfp validategrounds its AI analysis of a failure. Commands it suggests are checked against the CLI's own command set, and browserforce settings are reported as org-UI settings rather than as CLI flags.- A package build reports a missing Package2 registration in the Dev Hub as that, instead of as a generic creation failure.
- Repository and npm-registry calls to sfp server report the server's own error message instead of a generic substitute.
August 2026
v52.12.0 — August 30, 2026
sfp analyzeruns the version-assist AI linter only when it is asked for.--version-assistruns it,--no-version-assistkeeps it off even when the project enables it, and with neither flag it runs only when the server project settings explicitly enable it.- A package install that fails on a transport error — a dropped connection, DNS, or TLS failure — names the underlying cause instead of reporting
fetch failed. sfp server scalesizes both Hatchet worker pools.--workerssets the general pool and sizes the long-running pool proportionally;--longrunning-workerssets the long-running pool explicitly;--drain-timeoutbounds the wait for in-flight work, and--forcescales down without draining.
v52.10.2 — August 27, 2026
sfp analyzereports a linter that was skipped as skipped, instead of reporting it as a pass.
v52.10.0 — August 26, 2026
sfp validate org --waittimesets the metadata deployment wait for each package, in minutes. Defaults to 120.sfp org drift analyze --max-ai-findingsskips the AI review when the mechanical candidate count exceeds the threshold. Defaults to 50.sfp apextests resumebounds result fetching, so a large-org run stores its results instead of abandoning them on a timeout.sfp server initcreates the admin team, so a newly initialised admin can manage the organisation.
v52.9.3 — August 25, 2026
- Dependency resolution ignores source package dependencies declared inside the same project.
SFDMU
Run the bundled sfdmu (Salesforce Data Move Utility) against an org. From sfp v51 sfdmu is bundled with sfp and is no longer installed as an `sf` plugin, so use this as the drop-in replacement for `sf sfdmu run` in pre/post-deployment and custom scripts. Point --path at a directory containing an export.json (or --file at the file itself) to move records between csvfile and the target org, or pass -o csvfile with a source org to export records to CSV files in that directory. After the run, the per-row reports sfdmu writes to target/ are scanned the same way `sfp install` does: a records summary is printed and the command fails if any row was rejected, even though sfdmu itself exits successfully. Pass --no-failonrowerrors to report rejected rows as a warning without failing.
Common Errors
Next Page