patina-v11.4.1

What's Changed

This is the final patina release that will publish the patina_pi crate. Moving forward that crate will be available in the patina crate under patina::pi.

• Add safety comments for patina\_ffs module @joschock (#887)
  
  Change Details

    ## Description

  Add safety comments for patina_ffs module

  • Impacts functionality?
  • Impacts security?
  • Breaking change?
  • Includes tests?
  • Includes documentation?

  How This Was Tested

  Comments only; passes unit tests.

  Integration Instructions

  N/A
  

  
  

  ---

  
  

• Update to patina-devops v0.0.2 @makubacki (#886)
  
  Change Details

    ## Description

  Adds arguments to the CiWorkflow.yml call to preserve behavior across the update.

  • Impacts functionality?
  • Impacts security?
  • Breaking change?
  • Includes tests?
  • Includes documentation?

  How This Was Tested

  • PR CI workflows

  Integration Instructions

  • N/A
    

  
  

  ---

• Update workflows for patina-devops @makubacki (#882)
  
  Change Details

    ## Description

  Move most workflow implementations to a centralized location in:

  https://github.com/OpenDevicePartnership/patina-devops

  Call the reusable workflows from this repository. This is the first step of several steps to update Patina repos to centralize devops related collateral in a single dedicated repository.

  • Impacts functionality?
  • Impacts security?
  • Breaking change?
  • Includes tests?
  • Includes documentation?

  How This Was Tested

  • Test push and PR triggers on fork

  Integration Instructions

  • N/A
    

  
  

  ---

• chore: Release 11.4.0 @cfernald (#879)
  
  Change Details

    ## Description

  Release 11.4.0

  • Impacts functionality?
  • Impacts security?
  • Breaking change?
  • Includes tests?
  • Includes documentation?

  How This Was Tested

  N/A

  Integration Instructions

  N/A
  

  
  

  ---

  
  

🐛 Bug Fixes

• Do not set enable\_patina\_tests by default. @Javagedes (#885)
  
  Change Details

    ## Description

  When it comes to compilation and feature flags for crates, cargo attempts to find a version and feature configuration that satisfies all usage of a single crate. When even a single one of our crates specify that enable_patina_tests should be enabled, that ultimately enables the feature for the platform, even if they did not request that it be turned on.

  To prevent this this feature from always being enabled, even when the platform does not request it, we ensure that enable_patina_tests is not enabled by default in any crate. This allows the platform developer to toggle the feature in the patina crate and actually have it cascade properly.

  This commit fixes a bug that makes enable_patina_tests always enabled, even when the platform does not add the feature flag to their patina crate.

  • Impacts functionality?
  • Impacts security?
  • Breaking change?
  • Includes tests?
  • Includes documentation?

  How This Was Tested

  Validated that enabling the feature flag enable_patina_tests in the platform repository (or disabling by not specifying features = ["enable_patina_tests"]) now correctly enables or disables the feature flag. Previously the feature flag was always enabled, regardless of what the platform said, because a dependent crate had it enabled, and the cargo dependency resolver enabled it everywhere.

  Integration Instructions

  N/A
  

  
  

  ---

  
  

Full Changelog: patina-v11.4.0...v11.4.1