Cumulusci

Changes

- Added support for Lightning radiobuttons in the Robot keyword input form data. (3142)

Issues Closed

- Fixed an issue where CumulusCI was incorrectly merging task option overrides. (3145)

Changes

- CumulusCI now provides an option to verify server certificates using
root CA certs loaded from the system, instead of the default set of
CA certs bundled with the Python requests library. This is
considered experimental, so must be opted in by setting the
`CUMULUSCI_SYSTEM_CERTS` environment variable to `True` (3114)
- Improvements to the custom locator strategy used by the Robot
Framework keyword `input form data` to find form fields and
lightning components based on label text. This locator strategy
(`label:`) is now up to 10x faster at finding non-lightning form
components, and is able to find elements with more complicated
labels (eg: labels with text inside of nested spans). (3117)
- Fixed a bug that prevented the use of aliases for Robot Framework
page objects.(3120)
- The Robot Framework keyword `input form data` now does a better job
of working with non-lightning checkboxes. (3122)

Issues Closed

- Fixed an error that could occur when loading a project that uses
very old flow syntax with tasks instead of steps. (3118)
- Fixed a bug when using `sources` to access another project from a
github branch, where the branch context was not available to
branch-based dependency resolvers. (3123)
- The `drop_missing_schema` option was not respected by the
`snowfakery` task. Now it is. (3125)

Changes

- The `install_managed` and `update_dependencies` tasks:
- Now support `apex_compile_type` and `upgrade_type` options for
performing Unlocked Package installations. (3105)
- Accept the options `interactive` and `base-package-url-format`,
which pause the automation and wait for the user to confirm the
list of packages to be installed. (3093)
- The `update_package_xml` task now supports new Slack metadata types
(3103)
- We added the ability to do Upserts during Data Loading
([documentation](https://cumulusci.readthedocs.io/en/stable/data.html#upserts)).
(3099)
- Robot Framework tests can now pass a locator when calling
`Go To Page` for one of our bulit-in page objects (Listing, Detail,
Home), and the keyword will wait until that locator is visible. This
is mostly useful for custom pages where you need to wait for an
iframe or custom component to be available. (3098)
- We improved our caching mechanisms to better handle projects whose
cross-project sources themselves have cross-project sources. (3092)

Issues Closed

- Fixed a bug running the `snowfakery` task in parallel mode with orgs
connected using a Connected App. (3109)

Critical Changes

- CumulusCI now ships with Snowfakery 3.0. See the [Snowfakery release
notes](https://github.com/SFDO-Tooling/Snowfakery/releases/tag/v3.0.0).
Snowfakery 3.0 ships with opt-in features that will become the
default in June 2022; please [test your
recipes](https://snowfakery.readthedocs.io/en/latest/#snowfakery-3)
now with `snowfakery_version: 3` to ensure compatibility.

Changes

- CumulusCI now has an `update_data` task that allows updates to
existing datasets, in coordination with Snowfakery 3.0.
- Orgs connected using `cci org connect` now keep track of which
`connected_app` service was used to connect them, and will use the
same `connected_app` service when getting a fresh access token, even
if it isn't currently the default `connected_app` service. This
makes it easier to use CumulusCI with multiple `connected_app`
services. (Orgs that were connected before this update will continue
to use the default `connected_app` service.)
- When connecting a custom `connected_app` service, a default
`login_url` can be specified (to use a login URL other than
<https://login.salesforce.com> when connecting orgs using this
`connected_app` service).
- The `deploy_marketing_cloud_package` task now utilizes the new API
endpoint for deployments.
- CumulusCI commands are more resilient in the face of corrupted or
impossible to decode org config files.
- We added documentation about managing Robot Framework locators
- CumulusCI will now warn Windows users if long pathname support is
not set up correctly.

Issues Closed

- Fixed a bug in the JSON format output of cci service list --json

Changes

- Flow steps can now be replaced with the same syntax for all step
types! (Current step types are: 'task' or 'flow'). See the
\[replacing a flow
step\](<https://cumulusci.readthedocs.io/en/latest/config.html?highlight=override#replace-a-flow-step>)
docs for more details. CumulusCI is still compatible with the old
syntax which required setting the current step type to `None` when
replacing with a step of a differing type. (3043)
- Whenever possible, while running the `robot_libdoc` task libdoc
generates relative pathnames when creating CSV output (3058)
- Added a new option `--preview` to the `robot_libdoc` task. When set
to `true` it automatically opens a browser window to the generated
documentation. (3057)
- The robot keyword `Locate element by label` has been removed from
the Salesforce.py library. This wasn't designed to be a keyword but
was accidentally exported as one. If you want to find an input or
textarea element by its label you can use a locator of the form
`label:<text>` (eg: `label:First Name`) (3048)
- Updated to [Snowfakery

Issues Closed

- We fixed an issue that could cause `create_package_version` to fail
when the `version_base` option is set to `latest_github_release` and
the latest GitHub release is a 1GP package version.