Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
codecov/codecov-action
dependency is bumped from version 4 to 5 in thepush.yml
GitHub workflow file. The new version introduces several changes, including the use of the Codecov Wrapper to encapsulate the CLI, which enables faster updates. Breaking changes include the deprecation offile
andplugin
arguments in favor offiles
andplugins
, respectively. Additionally, several new arguments have been added, such asbinary
,gcov_args
,gcov_executable
,gcov_ignore
,gcov_include
,report_type
,skip_validation
, andswift_project
. A migration guide is provided to assist users in updating to the new version. Compatibility issues may arise due to the breaking changes, and users are advised to thoroughly review the migration guide and update their configurations accordingly.None
(#180). In this release, we've implemented a change to our open-source library that enhances the handling of dataclass fields during the marshalling process. Previously, fields were skipped if their value was falsy, which could inadvertently exclude empty lists, strings, or zeros. Now, the_marshal_dataclass
function in theinstallation.py
file has been updated to explicitly check forNone
when determining if a field should be skipped. This ensures that empty values are properly marshalled, increasing flexibility for users working with different data types. This change resolves issue #179 and demonstrates our commitment to improving the robustness and usability of our library for software engineers.Dependency updates: