chore: CI improvements

[b-long]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @b-long, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on enhancing the continuous integration and delivery pipeline by refining pre-commit hook configurations and streamlining the release management setup. These changes aim to improve the consistency of commit messages and simplify the automated versioning and release process for the project's Python packages.

Highlights

• Pre-commit Hook Configuration: The configuration for the conventional-pre-commit hook in .pre-commit-config.yaml has been updated to correctly quote the list of scopes, ensuring proper parsing and validation of commit messages.
• Release Please Configuration Streamlining: The .release-please-config.json file has been refactored to consolidate the release configuration for otdf-python-proto into the main package's configuration. This simplifies the release process by managing both packages under a single release-please entry and updates the extra-files list accordingly.
• Version Bumps Across Packages: Multiple files related to package versions, including pyproject.toml files, __init__.py files, uv.lock files, and .release-please-manifest.json, have been updated to reflect a new version 0.3.2. This is a consequence of the CI improvements and release process.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in issue comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request includes improvements to the CI configuration, updating dependencies and version numbers across multiple files. The changes primarily focus on ensuring consistency in versioning and improving the reliability of the CI process. I have provided review comments addressing a potential issue with string formatting in .pre-commit-config.yaml.

[b-long]

/gemini review

[gemini-code-assist]

Code Review

This pull request primarily focuses on CI improvements and version bumps. The changes to .pre-commit-config.yaml and .release-please-config.json are good steps towards better repository management. My review focuses on improving maintainability by removing hardcoded version numbers in the source code and tests. By dynamically reading the version from pyproject.toml, future releases will require fewer manual changes and be less error-prone.

[gemini-code-assist]

Hardcoding the version number here can lead to it becoming out of sync with the version in pyproject.toml. It's better to fetch the version dynamically from the package metadata. This ensures it's always correct and reduces maintenance effort during releases.

Suggested change

	__version__ = "0.3.2"
	__version__ = __import__('importlib.metadata').version('otdf-python-proto')

[gemini-code-assist]

Hardcoding the version number here can lead to it becoming out of sync with the version in pyproject.toml. It's better to fetch the version dynamically from package metadata. This ensures it's always correct and reduces maintenance effort during releases.

Suggested change

	__version__ = "0.3.2"
	__version__ = __import__('importlib.metadata').version('otdf-python')

[b-long]

/gemini review

[gemini-code-assist]

Code Review

This pull request introduces several good CI improvements and dependency updates. Bumping the package version across multiple files and updating the lock files looks correct.

I've left a couple of suggestions for improving maintainability:

• In src/otdf_python/cli.py, I've suggested dynamically loading the version from pyproject.toml to avoid manual updates.
• In tests/test_cli.py, while making the version check dynamic is a great step, I've suggested a small refactoring to improve the code style and readability by moving the conditional imports to the top of the file.

Overall, these are solid improvements.

[gemini-code-assist]

To avoid manually updating the version string in multiple places, you can read it dynamically from the package metadata using importlib.metadata. This will ensure it's always in sync with pyproject.toml.

You'll need to add from importlib import metadata at the top of the file.

Suggested change

	__version__ = "0.3.2"
	__version__ = metadata.version("otdf-python")

[gemini-code-assist]

This is a great improvement to make the test more robust!

To further improve readability and adhere to best practices (like PEP 8, which recommends imports at the top of the file), you can move the conditional import logic to the top of the file and simplify the TOML loading.

At the top of tests/test_cli.py, add:

import sys
from pathlib import Path
if sys.version_info < (3, 11):
    import tomli as tomllib
else:
    import tomllib

Then you can simplify this part of the test.

    with open(Path(__file__).parent.parent / "pyproject.toml", "rb") as f:
        pyproject = tomllib.load(f)
    expected_version = pyproject["project"]["version"]

    assert expected_version in result.stdout