Release v4.0.0 #3844
Release v4.0.0 #3844
Conversation
[W-16566993](https://gus.lightning.force.com/a07EE00001zeux8YAA) Migrating from SFDX CLI to SF CLI --------- Co-authored-by: James Estevez <[email protected]>
jstvz
force-pushed
the
cumulusci-v4
branch
2 times, most recently
from
d9262e7 to
26fc26d
Compare
Use pyproject.toml via uv for dependency management
Freezing dependencies does so for a single platform (e.g. linux) and
Python version (3.12). Because a dependency can include environment
markers to specify transitive dependencies a requirements.txt file
generated on one platform/version can fail to install on another.
This commit modifies our feature test workflow to use pip's local project
installs to provide the correct dependency resolutions for each platform
and python version.
- Adjusted the Python version matrix in GitHub workflows to include
Python 3.11, 3.12, and 3.13, removing older versions.
- Simplified the GitHub workflows to use uv
This PR extracts the SFDX integration tests into a reusable workflow so that we can test against the SFDX CLI's release candidates. It is intended to provide early warning of breaking changes. Edited to add: - integration test fixes for v4 that were missed in #3844 - `docutils`, which is required by `rst2ansi`
| @@ -286,18 +286,6 @@ tasks: | |||
| options: | |||
| src_dir: src | |||
| group: Salesforce DX | |||
| dx_pull: | |||
There was a problem hiding this comment.
@jstvz Why was this done? These are incredibly important and useful commands all over the documentation and is the proper way to interact with scratch orgs.
There was a problem hiding this comment.
@yippie We removed the dx_pull and dx_push commands because the underlying Salesforce CLI commands they relied on—force:source:pull and force:source:push—have been deprecated by Salesforce and replaced with project retrieve start and project deploy start.
These new commands behave differently, especially in how they handle source tracking and conflict resolution. Keeping the old dx_pull and dx_push commands could mislead users into thinking everything works the same, which isn’t the case. We want to avoid confusion and ensure everyone updates their workflows to use the new commands.
We recommend updating your scripts to use project retrieve start and project deploy start directly through the dx task or a custom task. We thought it safest to encourage users to verify that these new commands work as expected in their environments.
Depends on SFDO-Tooling/Snowfakery#1092
Fixes #3621
Fixes #3815