Skip to content

Commit

Permalink
Merge branch 'select_rows/default_record_selection_bug' of https://gi…
Browse files Browse the repository at this point in the history
…thub.com/SFDO-Tooling/CumulusCI into select_rows/default_record_selection_bug
  • Loading branch information
mjawadtp committed Jan 6, 2025
2 parents 2d14a07 + 7e247e9 commit bb4cac4
Show file tree
Hide file tree
Showing 2 changed files with 68 additions and 55 deletions.
2 changes: 1 addition & 1 deletion cumulusci/__about__.py
Original file line number Diff line number Diff line change
@@ -1 +1 @@
__version__ = "4.0.1.dev0"
__version__ = "4.0.1.dev1"
121 changes: 67 additions & 54 deletions docs/history.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,21 @@

<!-- latest-start -->

## v4.0.1.dev1 (2025-01-01)

<!-- Release notes generated using configuration in .github/release.yml at main -->

## What's Changed

### Changes 🎉

- @W-17427085: Set ANNOY related dependencies to be optional by [@aditya-balachander](https://github.com/aditya-balachander) in [#3858](https://github.com/SFDO-Tooling/CumulusCI/pull/3858)
- Update on the documentation for SFDX_ORG_CREATE_ARGS environment variable by [@lakshmi2506](https://github.com/lakshmi2506) in [#3861](https://github.com/SFDO-Tooling/CumulusCI/pull/3861)

**Full Changelog**: https://github.com/SFDO-Tooling/CumulusCI/compare/v4.0.1.dev0...v4.0.1.dev1

<!-- latest-stop -->

## v4.0.1.dev0 (2024-12-16)

<!-- Release notes generated using configuration in .github/release.yml at main -->
Expand All @@ -19,8 +34,6 @@

**Full Changelog**: https://github.com/SFDO-Tooling/CumulusCI/compare/v4.0.1...v4.0.1.dev0

<!-- latest-stop -->

## v4.0.1 (2024-11-18)

### Issues Fixed 🩴
Expand Down Expand Up @@ -1711,9 +1724,9 @@ Critical Changes:
subfolders will see a change in resolution behavior. Previously,
a dependency specified like this:

dependencies:
- github: https://github.com/SalesforceFoundation/NPSP
subfolder: unpackaged/config/trial
dependencies:
- github: https://github.com/SalesforceFoundation/NPSP
subfolder: unpackaged/config/trial

would always deploy from the latest commit on the default
branch. Now, this dependency will be resolved to a GitHub commit
Expand All @@ -1724,12 +1737,12 @@ Critical Changes:
- The `project__dependencies` section in `cumulusci.yml` no longer
supports nested dependencies specified like this:

dependencies:
- namespace: "test"
version: "1.0"
dependencies:
- namespace: "parent"
version: "2.2"
dependencies:
- namespace: "test"
version: "1.0"
dependencies:
- namespace: "parent"
version: "2.2"

All dependencies should be listed in install order.

Expand Down Expand Up @@ -1898,12 +1911,12 @@ Critical changes:
- The `project__dependencies` section in `cumulusci.yml` will no
longer support nested dependencies specified like this :

dependencies:
- namespace: "test"
version: "1.0"
dependencies:
- namespace: "parent"
version: "2.2"
dependencies:
- namespace: "test"
version: "1.0"
dependencies:
- namespace: "parent"
version: "2.2"

All dependencies should be listed in install order.

Expand Down Expand Up @@ -3510,33 +3523,33 @@ New features:

: -

Added keywords for generating a collection of sObjects according to a template:
Added keywords for generating a collection of sObjects according to a template:

: - `Generate Test Data`
- `Salesforce Collection Insert`
- `Salesforce Collection Update`
: - `Generate Test Data`
- `Salesforce Collection Insert`
- `Salesforce Collection Update`

-
-

Changes to Page Objects:
Changes to Page Objects:

: - More than one page object can be loaded at once.
Once loaded, the keywords of a page object remain
visible in the suite. Robot will give priority to
keywords in the reverse order in which they were
imported.
- There is a new keyword, `Log Current Page Object`,
which can be useful to see information about the
most recently loaded page object.
- There is a new keyword, `Get Page Object`, which
will return the robot library for a given page
object. This can be used in other keywords to access
keywords from another page object if necessary.
- The `Go To Page` keyword will now automatically load
the page object for the given page.
: - More than one page object can be loaded at once.
Once loaded, the keywords of a page object remain
visible in the suite. Robot will give priority to
keywords in the reverse order in which they were
imported.
- There is a new keyword, `Log Current Page Object`,
which can be useful to see information about the
most recently loaded page object.
- There is a new keyword, `Get Page Object`, which
will return the robot library for a given page
object. This can be used in other keywords to access
keywords from another page object if necessary.
- The `Go To Page` keyword will now automatically load
the page object for the given page.

- Added a basic debugger for Robot tests. It can be enabled
using the `-o debug True` option to the robot task.
- Added a basic debugger for Robot tests. It can be enabled
using the `-o debug True` option to the robot task.

- Added support for deploying new metadata types
`ProfilePasswordPolicy` and `ProfileSessionSetting`.
Expand Down Expand Up @@ -3611,8 +3624,8 @@ New features:
permanently set this option, add this in
`~/.cumulusci/cumulusci.yml`:

cli:
plain_output: True
cli:
plain_output: True

- Added additional info to the `cci version` command, including the
Python version, an upgrade check, and a warning on Python 2.
Expand Down Expand Up @@ -4893,12 +4906,12 @@ Resolving a few issues from beta77:
below. In flows that need to inject the actual namespace prefix,
override the [unmanaged]{.title-ref} option .. :

custom_deploy_task:
class_path: cumulusci.tasks.salesforce.Deploy
options:
path: your/custom/metadata
namespace_inject: $project_config.project__package__namespace
unmanaged: False
custom_deploy_task:
class_path: cumulusci.tasks.salesforce.Deploy
options:
path: your/custom/metadata
namespace_inject: $project_config.project__package__namespace
unmanaged: False

### Enhancements

Expand Down Expand Up @@ -5613,13 +5626,13 @@ Resolving a few issues from beta77:
- **IMPORANT** This release changes the yaml structure for flows. The
new structure now looks like this:

flows:
flow_name:
tasks:
1:
task: deploy
2:
task: run_tests
flows:
flow_name:
tasks:
1:
task: deploy
2:
task: run_tests

- See the new flow customization examples in the cookbook for examples
of why this change was made and how to use it:
Expand Down

0 comments on commit bb4cac4

Please sign in to comment.