upgrade zanadir

[tomersein]

Pull Request

Description

Please include a summary of the changes and the related issue. Please also include relevant motivation and context.

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[github-actions]

1. Review Summary: This diff updates the version of the zanadir-action used in the CI workflow. While seemingly simple, it's important to verify the changelog of the new action version for any breaking changes or security implications.

2. Critical issues: None apparent in the diff itself, but a critical issue could arise from undocumented changes in zanadir-action@v1.4. Without reviewing the release notes for zanadir-action, we cannot assess if this version change introduces new vulnerabilities or breaks existing functionality.

3. Suggestions:

   1. Critical: Review the zanadir-action@v1.4 release notes/changelog to understand what changes have been introduced and ensure they don't negatively impact the project (introduce vulnerabilities, break functionality).
   2. Important: After reviewing the release notes, consider adding a comment in the workflow file describing the changes introduced by the version update. This will improve maintainability in the future.
   3. Consider: Periodically update the zanadir-action to the latest version to benefit from bug fixes and performance improvements.
   4. Consider: Add a test case or scenario to ensure that the functionality provided by zanadir-action remains working as expected after this upgrade.
   5. Informational: Consider pinning to a specific commit SHA for zanadir-action instead of a tag. This provides more assurance that the action's behavior will remain consistent over time.

4. Quick wins or positive aspects: The update is a straightforward version bump, and using GitHub Actions contributes to a well-defined CI process.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
see 13 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.