Merge pull request #3876 from SFDO-Tooling/release-4.3.0

Release v4.3.0
SFDO-Tooling · Feb 10, 2025 · 31e7afb · 31e7afb
2 parents 1ec8347 + 0cefe4f
commit 31e7afb
Show file tree

Hide file tree

Showing 2 changed files with 67 additions and 55 deletions.
diff --git a/cumulusci/__about__.py b/cumulusci/__about__.py
@@ -1 +1 @@
-__version__ = "4.2.0"
+__version__ = "4.3.0"
diff --git a/docs/history.md b/docs/history.md
@@ -2,6 +2,20 @@
 
 <!-- latest-start -->
 
+## v4.3.0 (2025-02-07)
+
+<!-- Release notes generated using configuration in .github/release.yml at main -->
+
+## What's Changed
+
+### Changes 🎉
+
+-   Fix the check_sobjects_available task to take the api_version from Cumulusci.yml by [@lakshmi2506](https://github.com/lakshmi2506) in [#3875](https://github.com/SFDO-Tooling/CumulusCI/pull/3875)
+
+**Full Changelog**: https://github.com/SFDO-Tooling/CumulusCI/compare/v4.2.0...v4.3.0
+
+<!-- latest-stop -->
+
 ## v4.2.0 (2025-01-20)
 
 <!-- Release notes generated using configuration in .github/release.yml at main -->
@@ -20,8 +34,6 @@
 
 **Full Changelog**: https://github.com/SFDO-Tooling/CumulusCI/compare/v4.1.0...v4.2.0
 
-<!-- latest-stop -->
-
 ## v4.1.0 (2025-01-09)
 
 <!-- Release notes generated using configuration in .github/release.yml at main -->
@@ -1763,9 +1775,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
@@ -1776,12 +1788,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.
 
@@ -1950,12 +1962,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.
 
@@ -3562,33 +3574,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`.
@@ -3663,8 +3675,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.
@@ -4945,12 +4957,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
 
@@ -5665,13 +5677,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: