2
2
3
3
<!-- latest-start -->
4
4
5
+ ## v4.6.0 (2025-09-04)
6
+
7
+ <!-- Release notes generated using configuration in .github/release.yml at main -->
8
+
9
+ ## What's Changed
10
+
11
+ ### Changes
12
+
13
+ - fix: include --output-dir only when output_dir is provided by [ @jstvz ] ( https://github.com/jstvz ) in [ #3920 ] ( https://github.com/SFDO-Tooling/CumulusCI/pull/3920 )
14
+
15
+ ** Full Changelog** : https://github.com/SFDO-Tooling/CumulusCI/compare/v4.5.0...v4.6.0
16
+
17
+ <!-- latest-stop -->
18
+
5
19
## v4.5.0 (2025-08-06)
6
20
7
21
<!-- Release notes generated using configuration in .github/release.yml at main -->
24
38
25
39
** Full Changelog** : https://github.com/SFDO-Tooling/CumulusCI/compare/v4.4.0...v4.5.0
26
40
27
- <!-- latest-stop -->
28
-
29
41
## v4.4.0 (2025-05-05)
30
42
31
43
<!-- Release notes generated using configuration in .github/release.yml at main -->
@@ -1828,9 +1840,9 @@ Critical Changes:
1828
1840
subfolders will see a change in resolution behavior. Previously,
1829
1841
a dependency specified like this:
1830
1842
1831
- dependencies:
1832
- - github: https://github.com/SalesforceFoundation/NPSP
1833
- subfolder: unpackaged/config/trial
1843
+ dependencies:
1844
+ - github: https://github.com/SalesforceFoundation/NPSP
1845
+ subfolder: unpackaged/config/trial
1834
1846
1835
1847
would always deploy from the latest commit on the default
1836
1848
branch. Now, this dependency will be resolved to a GitHub commit
@@ -1841,12 +1853,12 @@ Critical Changes:
1841
1853
- The ` project__dependencies ` section in ` cumulusci.yml ` no longer
1842
1854
supports nested dependencies specified like this:
1843
1855
1844
- dependencies:
1845
- - namespace: "test"
1846
- version: "1.0"
1847
- dependencies:
1848
- - namespace: "parent"
1849
- version: "2.2"
1856
+ dependencies:
1857
+ - namespace: "test"
1858
+ version: "1.0"
1859
+ dependencies:
1860
+ - namespace: "parent"
1861
+ version: "2.2"
1850
1862
1851
1863
All dependencies should be listed in install order.
1852
1864
@@ -2015,12 +2027,12 @@ Critical changes:
2015
2027
- The ` project__dependencies ` section in ` cumulusci.yml ` will no
2016
2028
longer support nested dependencies specified like this :
2017
2029
2018
- dependencies:
2019
- - namespace: "test"
2020
- version: "1.0"
2021
- dependencies:
2022
- - namespace: "parent"
2023
- version: "2.2"
2030
+ dependencies:
2031
+ - namespace: "test"
2032
+ version: "1.0"
2033
+ dependencies:
2034
+ - namespace: "parent"
2035
+ version: "2.2"
2024
2036
2025
2037
All dependencies should be listed in install order.
2026
2038
@@ -3627,33 +3639,33 @@ New features:
3627
3639
3628
3640
: -
3629
3641
3630
- Added keywords for generating a collection of sObjects according to a template:
3642
+ Added keywords for generating a collection of sObjects according to a template:
3631
3643
3632
- : - `Generate Test Data`
3633
- - `Salesforce Collection Insert`
3634
- - `Salesforce Collection Update`
3644
+ : - `Generate Test Data`
3645
+ - `Salesforce Collection Insert`
3646
+ - `Salesforce Collection Update`
3635
3647
3636
- -
3648
+ -
3637
3649
3638
- Changes to Page Objects:
3650
+ Changes to Page Objects:
3639
3651
3640
- : - More than one page object can be loaded at once.
3641
- Once loaded, the keywords of a page object remain
3642
- visible in the suite. Robot will give priority to
3643
- keywords in the reverse order in which they were
3644
- imported.
3645
- - There is a new keyword, `Log Current Page Object`,
3646
- which can be useful to see information about the
3647
- most recently loaded page object.
3648
- - There is a new keyword, `Get Page Object`, which
3649
- will return the robot library for a given page
3650
- object. This can be used in other keywords to access
3651
- keywords from another page object if necessary.
3652
- - The `Go To Page` keyword will now automatically load
3653
- the page object for the given page.
3652
+ : - More than one page object can be loaded at once.
3653
+ Once loaded, the keywords of a page object remain
3654
+ visible in the suite. Robot will give priority to
3655
+ keywords in the reverse order in which they were
3656
+ imported.
3657
+ - There is a new keyword, `Log Current Page Object`,
3658
+ which can be useful to see information about the
3659
+ most recently loaded page object.
3660
+ - There is a new keyword, `Get Page Object`, which
3661
+ will return the robot library for a given page
3662
+ object. This can be used in other keywords to access
3663
+ keywords from another page object if necessary.
3664
+ - The `Go To Page` keyword will now automatically load
3665
+ the page object for the given page.
3654
3666
3655
- - Added a basic debugger for Robot tests. It can be enabled
3656
- using the `-o debug True` option to the robot task.
3667
+ - Added a basic debugger for Robot tests. It can be enabled
3668
+ using the `-o debug True` option to the robot task.
3657
3669
3658
3670
- Added support for deploying new metadata types
3659
3671
` ProfilePasswordPolicy ` and ` ProfileSessionSetting ` .
@@ -3728,8 +3740,8 @@ New features:
3728
3740
permanently set this option, add this in
3729
3741
` ~/.cumulusci/cumulusci.yml ` :
3730
3742
3731
- cli:
3732
- plain_output: True
3743
+ cli:
3744
+ plain_output: True
3733
3745
3734
3746
- Added additional info to the ` cci version ` command, including the
3735
3747
Python version, an upgrade check, and a warning on Python 2.
@@ -5009,12 +5021,12 @@ Resolving a few issues from beta77:
5009
5021
below. In flows that need to inject the actual namespace prefix,
5010
5022
override the [ unmanaged] {.title-ref} option .. :
5011
5023
5012
- custom_deploy_task:
5013
- class_path: cumulusci.tasks.salesforce.Deploy
5014
- options:
5015
- path: your/custom/metadata
5016
- namespace_inject: $project_config.project__package__namespace
5017
- unmanaged: False
5024
+ custom_deploy_task:
5025
+ class_path: cumulusci.tasks.salesforce.Deploy
5026
+ options:
5027
+ path: your/custom/metadata
5028
+ namespace_inject: $project_config.project__package__namespace
5029
+ unmanaged: False
5018
5030
5019
5031
### Enhancements
5020
5032
@@ -5729,13 +5741,13 @@ Resolving a few issues from beta77:
5729
5741
- ** IMPORANT** This release changes the yaml structure for flows. The
5730
5742
new structure now looks like this:
5731
5743
5732
- flows:
5733
- flow_name:
5734
- tasks:
5735
- 1:
5736
- task: deploy
5737
- 2:
5738
- task: run_tests
5744
+ flows:
5745
+ flow_name:
5746
+ tasks:
5747
+ 1:
5748
+ task: deploy
5749
+ 2:
5750
+ task: run_tests
5739
5751
5740
5752
- See the new flow customization examples in the cookbook for examples
5741
5753
of why this change was made and how to use it:
0 commit comments