22
33<!-- latest-start -->
44
5+ ## v4.8.0 (2026-01-06)
6+
7+ <!-- Release notes generated using configuration in .github/release.yml at main -->
8+
9+ ## What's Changed
10+
11+ ### Changes
12+
13+ - Update simple-salesforce to greater than 1.12.6 by [ @aditya-balachander ] ( https://github.com/aditya-balachander ) in [ #3943 ] ( https://github.com/SFDO-Tooling/CumulusCI/pull/3943 )
14+
15+ ** Full Changelog** : https://github.com/SFDO-Tooling/CumulusCI/compare/v4.7.0...v4.8.0
16+
17+ <!-- latest-stop -->
18+
519## v4.7.0 (2025-12-19)
620
721<!-- Release notes generated using configuration in .github/release.yml at main -->
1428
1529** Full Changelog** : https://github.com/SFDO-Tooling/CumulusCI/compare/v4.6.0.dev1...v4.7.0
1630
17- <!-- latest-stop -->
18-
1931## v4.6.0.dev1 (2025-10-21)
2032
2133<!-- Release notes generated using configuration in .github/release.yml at main -->
@@ -1876,9 +1888,9 @@ Critical Changes:
18761888 subfolders will see a change in resolution behavior. Previously,
18771889 a dependency specified like this:
18781890
1879- dependencies:
1880- - github: https://github.com/SalesforceFoundation/NPSP
1881- subfolder: unpackaged/config/trial
1891+ dependencies:
1892+ - github: https://github.com/SalesforceFoundation/NPSP
1893+ subfolder: unpackaged/config/trial
18821894
18831895 would always deploy from the latest commit on the default
18841896 branch. Now, this dependency will be resolved to a GitHub commit
@@ -1889,12 +1901,12 @@ Critical Changes:
18891901 - The ` project__dependencies ` section in ` cumulusci.yml ` no longer
18901902 supports nested dependencies specified like this:
18911903
1892- dependencies:
1893- - namespace: "test"
1894- version: "1.0"
1895- dependencies:
1896- - namespace: "parent"
1897- version: "2.2"
1904+ dependencies:
1905+ - namespace: "test"
1906+ version: "1.0"
1907+ dependencies:
1908+ - namespace: "parent"
1909+ version: "2.2"
18981910
18991911 All dependencies should be listed in install order.
19001912
@@ -2063,12 +2075,12 @@ Critical changes:
20632075 - The ` project__dependencies ` section in ` cumulusci.yml ` will no
20642076 longer support nested dependencies specified like this :
20652077
2066- dependencies:
2067- - namespace: "test"
2068- version: "1.0"
2069- dependencies:
2070- - namespace: "parent"
2071- version: "2.2"
2078+ dependencies:
2079+ - namespace: "test"
2080+ version: "1.0"
2081+ dependencies:
2082+ - namespace: "parent"
2083+ version: "2.2"
20722084
20732085 All dependencies should be listed in install order.
20742086
@@ -3675,33 +3687,33 @@ New features:
36753687
36763688 : -
36773689
3678- Added keywords for generating a collection of sObjects according to a template:
3690+ Added keywords for generating a collection of sObjects according to a template:
36793691
3680- : - `Generate Test Data`
3681- - `Salesforce Collection Insert`
3682- - `Salesforce Collection Update`
3692+ : - `Generate Test Data`
3693+ - `Salesforce Collection Insert`
3694+ - `Salesforce Collection Update`
36833695
3684- -
3696+ -
36853697
3686- Changes to Page Objects:
3698+ Changes to Page Objects:
36873699
3688- : - More than one page object can be loaded at once.
3689- Once loaded, the keywords of a page object remain
3690- visible in the suite. Robot will give priority to
3691- keywords in the reverse order in which they were
3692- imported.
3693- - There is a new keyword, `Log Current Page Object`,
3694- which can be useful to see information about the
3695- most recently loaded page object.
3696- - There is a new keyword, `Get Page Object`, which
3697- will return the robot library for a given page
3698- object. This can be used in other keywords to access
3699- keywords from another page object if necessary.
3700- - The `Go To Page` keyword will now automatically load
3701- the page object for the given page.
3700+ : - More than one page object can be loaded at once.
3701+ Once loaded, the keywords of a page object remain
3702+ visible in the suite. Robot will give priority to
3703+ keywords in the reverse order in which they were
3704+ imported.
3705+ - There is a new keyword, `Log Current Page Object`,
3706+ which can be useful to see information about the
3707+ most recently loaded page object.
3708+ - There is a new keyword, `Get Page Object`, which
3709+ will return the robot library for a given page
3710+ object. This can be used in other keywords to access
3711+ keywords from another page object if necessary.
3712+ - The `Go To Page` keyword will now automatically load
3713+ the page object for the given page.
37023714
3703- - Added a basic debugger for Robot tests. It can be enabled
3704- using the `-o debug True` option to the robot task.
3715+ - Added a basic debugger for Robot tests. It can be enabled
3716+ using the `-o debug True` option to the robot task.
37053717
37063718- Added support for deploying new metadata types
37073719 ` ProfilePasswordPolicy ` and ` ProfileSessionSetting ` .
@@ -3776,8 +3788,8 @@ New features:
37763788 permanently set this option, add this in
37773789 ` ~/.cumulusci/cumulusci.yml ` :
37783790
3779- cli:
3780- plain_output: True
3791+ cli:
3792+ plain_output: True
37813793
37823794- Added additional info to the ` cci version ` command, including the
37833795 Python version, an upgrade check, and a warning on Python 2.
@@ -5057,12 +5069,12 @@ Resolving a few issues from beta77:
50575069 below. In flows that need to inject the actual namespace prefix,
50585070 override the [ unmanaged] {.title-ref} option .. :
50595071
5060- custom_deploy_task:
5061- class_path: cumulusci.tasks.salesforce.Deploy
5062- options:
5063- path: your/custom/metadata
5064- namespace_inject: $project_config.project__package__namespace
5065- unmanaged: False
5072+ custom_deploy_task:
5073+ class_path: cumulusci.tasks.salesforce.Deploy
5074+ options:
5075+ path: your/custom/metadata
5076+ namespace_inject: $project_config.project__package__namespace
5077+ unmanaged: False
50665078
50675079### Enhancements
50685080
@@ -5777,13 +5789,13 @@ Resolving a few issues from beta77:
57775789- ** IMPORANT** This release changes the yaml structure for flows. The
57785790 new structure now looks like this:
57795791
5780- flows:
5781- flow_name:
5782- tasks:
5783- 1:
5784- task: deploy
5785- 2:
5786- task: run_tests
5792+ flows:
5793+ flow_name:
5794+ tasks:
5795+ 1:
5796+ task: deploy
5797+ 2:
5798+ task: run_tests
57875799
57885800- See the new flow customization examples in the cookbook for examples
57895801 of why this change was made and how to use it:
0 commit comments