Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release v0.10.0 #182

Closed
wants to merge 1 commit into from
Closed

Release v0.10.0 #182

wants to merge 1 commit into from

Conversation

gueniai
Copy link
Collaborator

@gueniai gueniai commented Jan 13, 2025

  • Bump codecov/codecov-action from 4 to 5 (#174). In this release, the Codecov GitHub Action has been updated from version 4 to 5, featuring several new arguments and improvements to the underlying Codecov Wrapper. The new arguments include binary, gcov_args, gcov_executable, gcov_ignore, gcov_include, report_type, skip_validation, and swift_project. Additionally, the file and plugin arguments have been deprecated and replaced with files and plugins, respectively. These changes will ensure that the Action receives updates more quickly and provide developers with more flexibility in configuring their coverage reports. Furthermore, several existing arguments have been updated and improved, enhancing the overall functionality and usability of the Codecov GitHub Action.
  • Fixed incorrect script for no-pylint-disable (#178). This release introduces an upgrade to the script used for checking the disabling of linters in new code, adopting the latest version from the ucx project. Previously, the script returned false positives for stacked pull requests, particularly with pylint checks. This release resolves the issue by employing a Python script, no_cheat.py, which takes a generated diff file as an argument to accurately detect instances of linter disablement. The updated script then outputs the instances to a file called cheats.txt and fails the commit if more than one line is present, ensuring that instances of linter disablement are properly identified. This enhancement significantly improves the precision of the linter disablement check for pull requests and ensures that pylint disables are accurately tracked and reported, regardless of stacked pull requests.
  • Skip dataclassess fields only when None (#180). In this release, the behavior of skipping dataclass fields has been modified to allow skipping a field only when its value is None. This enhancement enables the writing of empty lists, strings, or zeros, addressing issue #179. The _marshal_dataclass method, responsible for marshalling dataclasses, has been updated to replace the conditional statement if not raw: with if raw is None:. By checking for explicit None values, the new logic preserves empty lists, strings, or zeros and does not treat them as None, ensuring that these specific cases are not unnecessarily skipped. This change provides more control and precision when marshalling dataclasses in the open-source library.

Dependency updates:

  • Bump codecov/codecov-action from 4 to 5 (#174).

* Bump codecov/codecov-action from 4 to 5 ([#174](#174)). In this release, the Codecov GitHub Action has been updated from version 4 to 5, featuring several new arguments and improvements to the underlying Codecov Wrapper. The new arguments include `binary`, `gcov_args`, `gcov_executable`, `gcov_ignore`, `gcov_include`, `report_type`, `skip_validation`, and `swift_project`. Additionally, the `file` and `plugin` arguments have been deprecated and replaced with `files` and `plugins`, respectively. These changes will ensure that the Action receives updates more quickly and provide developers with more flexibility in configuring their coverage reports. Furthermore, several existing arguments have been updated and improved, enhancing the overall functionality and usability of the Codecov GitHub Action.
* Fixed incorrect script for no-pylint-disable ([#178](#178)). This release introduces an upgrade to the script used for checking the disabling of linters in new code, adopting the latest version from the ucx project. Previously, the script returned false positives for stacked pull requests, particularly with pylint checks. This release resolves the issue by employing a Python script, `no_cheat.py`, which takes a generated diff file as an argument to accurately detect instances of linter disablement. The updated script then outputs the instances to a file called `cheats.txt` and fails the commit if more than one line is present, ensuring that instances of linter disablement are properly identified. This enhancement significantly improves the precision of the linter disablement check for pull requests and ensures that pylint disables are accurately tracked and reported, regardless of stacked pull requests.
* Skip dataclassess fields only when `None` ([#180](#180)). In this release, the behavior of skipping dataclass fields has been modified to allow skipping a field only when its value is `None`. This enhancement enables the writing of empty lists, strings, or zeros, addressing issue [#179](#179). The `_marshal_dataclass` method, responsible for marshalling dataclasses, has been updated to replace the conditional statement `if not raw:` with `if raw is None:`. By checking for explicit `None` values, the new logic preserves empty lists, strings, or zeros and does not treat them as `None`, ensuring that these specific cases are not unnecessarily skipped. This change provides more control and precision when marshalling dataclasses in the open-source library.

Dependency updates:

 * Bump codecov/codecov-action from 4 to 5 ([#174](#174)).
@gueniai gueniai requested a review from nfx as a code owner January 13, 2025 15:26
@gueniai gueniai requested review from JCZuurmond and removed request for nfx January 13, 2025 15:27
Copy link

✅ 40/40 passed, 2 skipped, 1m15s total

Running from acceptance #247

@gueniai gueniai closed this Jan 13, 2025
@gueniai gueniai deleted the prepare/0.10.0 branch January 13, 2025 21:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant