Skip to content

v0.42.0

Compare
Choose a tag to compare
@actions-helper actions-helper released this 27 Jun 16:40
· 2 commits to main since this release

v0.42.0 (2024-06-27)

Chore

  • chore: updatehooks skips updated repos that aren't out of date by default (#575)

This PR adds a new argument to the updatehooks function named
force_update which is set to False by default. if force_update is false,
then we won't download/install the repo unless it is out of date. If
force_update is True, then we'd download and install the latest repo
version irrespective of the currently installed version.

There is currently no code (outside of unit tests) that's passing True
for the force_update argument.

Changes

<!-- A detailed list of changes -->
*

Testing

<!--
Mention updated tests and any manual testing performed.
Are aspects not yet tested or not easily testable?
Feel free to include screenshots if appropriate.
-->
*

Clean Code Checklist

<!-- This is here to support you. Some/most checkboxes may not apply to
your change -->

  • Meets acceptance criteria for issue
  • New logic is covered with automated tests
  • Appropriate exception handling added
  • Thoughtful logging included
  • Documentation is updated
  • Follow-up work is documented in TODOs
  • TODOs have a ticket associated with them
  • No commented-out code included

<!--
Github-flavored markdown reference:
https://docs.github.com/en/get-started/writing-on-github
-->


Co-authored-by: Ian Bowden <ian.bowden@slalom> (88b3d99)

Feature

  • feat: Added Exit codes and updated unit tests #547 (#548)

secureli-375
#375

<!-- Include general description here -->
Added Additional Exit Codes based on error types as discussed. Passing
exitCode to the ScanFailure class

Changes

<!-- A detailed list of changes -->

  • Added Exit Codes
  • Updated ScanFailure
  • Updated Unit Tests
  • Verified no additional errors

Testing

<!--
Mention updated tests and any manual testing performed.
Are aspects not yet tested or not easily testable?
Feel free to include screenshots if appropriate.
-->
*

Clean Code Checklist

<!-- This is here to support you. Some/most checkboxes may not apply to
your change -->

  • Meets acceptance criteria for issue
  • New logic is covered with automated tests
  • Appropriate exception handling added
  • Thoughtful logging included
  • Documentation is updated
  • Follow-up work is documented in TODOs
  • TODOs have a ticket associated with them
  • No commented-out code included

<!--
Github-flavored markdown reference:
https://docs.github.com/en/get-started/writing-on-github
-->


Co-authored-by: Ian Bowden <ian.bowden@slalom> (c1b55b3)