Cumulusci

- `uninstall_packaged_incremental` task: Added `ignore` option to
specify components to skip trying to delete even if they are present
in the org but not in the local source.

- Fixed the `cci project init` command, which was failing because it
wanted the project to already exist! Fixes 816. In addition, other
commands will now function without an active project or keychain
when it possible to do so. (For example, try `cci version` which now
works when you're not in a project directory.)

- `update_dependencies` task:

: - Added support for installing private github repositories as
dependencies. Thanks to Anthony Backhouse (1handclapping)
for the patch. Fixes 793 - Added a `dependencies` option to override the project
dependencies.

- `execute_apex` task:

: - Print more useful error messages when there are Apex
exceptions.

- `robot` task:

: - Our logic for automatically retrying failed selenium
commands has been encapsulated into the
`cumulusci.robotframework.utils.selenium_retry` decorator
which can be applied to a robot library class for increased
stability. - There is now an option to pause and enter the Python
debugger after a keyword fails. Run with `-o pdb True`. - Revised keywords and locators to support the Winter '19
release of Salesforce and improve stability. - The `Salesforce.robot` file now includes the
`OperatingSystem` and `XML` libraries from Robot Framework
by default. These libraries are helpful in building
integration tests such as modifying and deploying a
PageLayout to include a field needed in Suite Setup of an
integration test.

- Revised installation instructions for Windows. Thanks Matthew
Blanski (Auchtor).

- Internal change: Use a thread-local variable instead of a global to
track the current running task.

- It's happening! Hot on the heels of the last release, CumulusCI is
making the jump to the modern era by adding **support for Python
3**! (Specifically, Python 3.6 and 3.7.) Don't worry, we'll also
continue to support Python 2 for the time being. Because this is a
bit more wide-reaching change than normal, we're releasing a beta
first. To install the beta you'll need to explicitly request its
version: `pip install cumulusci==2.1.0b1`. If you already have
CumulusCI, after the update it will continue to run under your
Python 2 interpreter. If you want to switch to the Python 3
interpreter (which is not yet required), we recommend deleting your
Python virtualenv and starting over with the instructions in the
[tutorial](https://cumulusci.readthedocs.io/en/latest/tutorial.html).
If you want to keep your Python 2-based virtualenv around just in
case, follow those instructions but name the new virtualenv
`cci-py3` instead of `cci`.
- There are also some big changes to the **bulk data** tasks. Did you
know CumulusCI has bulk data tasks? They are not configured by
default, because we need to finish documenting them. But we'll list
the changes in case someone is already relying on them:
- Fixed connection resets by downloading an entire result file
before processing.
- Improved performance by processing batches in parallel, avoiding
the SQLAlchemy ORM, storing inserted Ids in separate tables, and
doing lookups using SQL joins rather than a separate query for
each row.
- If you're using a postgres database for local storage,
performance gets even better by taking advantage of postgres'
`COPY` command to load CSV directly.
- Added a `hardDelete` option for bulk deletes.
- Added a `start_step` option for bulk loads which can be used to
resume loading after an error.
- The `push_failure_report` task will now by default hide failures
that occurred due to the "Package Uninstalled" or "Salesforce
Subscription Expired" errors, which are generally benign.
- Fixed the check for newer CumulusCI versions to work around an issue
with old `setuptools`.
- Contributor change: We switched CumulusCI's own tests to run using
`pytest`.
- Internal change: We switched to the `cryptography` library for
handling keychain encryption.

- Happy Spooky October! It's unlucky release 2.0.13, with some
scary-cool improvements. Just to show you how ramped up our RelEng
team is now, this release had TWENTY THREE pull requests in 12 days!
From all four of your friendly SFDO Release Engineering committers.
Thanks so much for continuing to use CCI for all your Salesforce
automation needs.
- NEW FLOW: ci_beta_dependencies installs the latest beta of project
dependencies and run tests. Includes task error when running against
non-scratch orgs.
- NEW TASK: ReportPushFailures pulls a list of Package Push Upgrade
Request failures after a push attempt, including grouping by
important factors.
- Issue a terminal "Bell" sound and attempt to display a macOS
notification when a commandline task or flow completes.
- Cleaned up python exception and error handling across the board, so
that we can provide you, the user, with only the most relevant
information. Try using CCI without setting your CUMULUSCI_KEY and
see a simplified error message.
- Fixed the utils for processing namespaces in package zip files to
handle non-ASCII characters
- The CONTRIBUTING.rst docs and Makefile have been updated to show how
we release updates of CCI.
- Skip beta releases when checking for a newer cumulusci version
- When using the strip_namespace option on deployments, we now log
which files had changes made before deploying.
- Going Out: the SFDXDeploy and SFDXJsonPollingTasks have been
removed, as they didn't work.
- Going Out: Use the safe_load() method when loading YAML instead of
the naive load(). If you relied on executing code in your CCI YAML
file parsing, that will no longer work.

- Fixed apexdoc URL
- Fixed [](update-admin-profile) to set any existing record
type defaults to false before setting new defaults.
- Fixed deployment of -meta.xml files containing non-ASCII characters.
- Updated the robot selector for "Click Modal Button" to work for
modals opened by a Quick Action.

- [](update-admin-profile) now uses xml parsing instead of
string replacement for more targeted editing of Admin.profile to fix
issues with deploying record types via dependencies
- Projects can declare a dependency on a minimum version of cumulusci
by specifying [minimum_cumulusci_version]{.title-ref} in
cumulusci.yml