feat: add version bump and tag release workflows

[mdesmet]

Important

Adds GitHub Actions workflows for version bumping and tagging releases, automating version management and PyPI publishing.

• Workflows:
  • Adds bump-version.yml to automate version bumping via bump2version and create a pull request with updated version files.
  • Adds tag-release.yml to tag releases on merged pull requests labeled with version-bump and publish to PyPI.
• Version Management:
  • bump-version.yml allows bumping major, minor, or patch versions and updates setup.py, docs/conf.py, src/datapilot/__init__.py, and .bumpversion.cfg.
  • tag-release.yml creates a Git tag and pushes it to the repository, then executes release.sh to publish to PyPI.

^{This description was created by for 90d6df2. You can customize this summary. It will automatically update as commits are pushed.}

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to 0b4b182 in 1 minute and 11 seconds. Click for details.

• Reviewed 145 lines of code in 2 files
• Skipped 0 files when reviewing.
• Skipped posting 5 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. .github/workflows/bump-version.yml:47

• Draft comment:
  Consider anchoring the grep pattern (e.g. using '^current_version') to ensure you extract the correct version.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

2. .github/workflows/bump-version.yml:55

• Draft comment:
  Similarly, anchor the grep pattern (e.g. '^current_version') when retrieving the new version for consistency.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

3. .github/workflows/bump-version.yml:36

• Draft comment:
  Consider pinning the bump2version package version (e.g. bump2version==x.y.z) in the pip install command for build reproducibility.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

4. .github/workflows/tag-release.yml:33

• Draft comment:
  Use an anchored grep pattern (e.g. '^current_version') here as well to ensure precise extraction of the version.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

5. .github/workflows/tag-release.yml:27

• Draft comment:
  Consider pinning versions for dependencies (tox, twine, wheel, setuptools) to ensure reproducible builds.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

Workflow ID: wflow_FC6lEK6htjcPAKn8

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed 90d6df2 in 48 seconds. Click for details.

• Reviewed 135 lines of code in 2 files
• Skipped 0 files when reviewing.
• Skipped posting 5 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. .github/workflows/bump-version.yml:47

• Draft comment:
  Consider adding error handling in case grep fails to find a valid version in .bumpversion.cfg.
• Reason this comment was not posted:
  Confidence changes required: 50% <= threshold 50% None

2. .github/workflows/bump-version.yml:54

• Draft comment:
  Good use of a choice input for version_part. No additional sanitization needed since allowed values are enforced.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

3. .github/workflows/tag-release.yml:9

• Draft comment:
  Ensure the label check (contains with github.event.pull_request.labels.*.name) behaves correctly when multiple labels are present.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

4. .github/workflows/tag-release.yml:42

• Draft comment:
  Consider verifying that release.sh exists before applying chmod, to avoid potential job failures.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

5. .github/workflows/tag-release.yml:45

• Draft comment:
  Consider capturing and logging output from release.sh to aid debugging if the PyPI publish step fails.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

Workflow ID: wflow_0kKNvkeRTi5cwjxT

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}