feat: add version bump and tag release workflows by mdesmet · Pull Request #58 · AltimateAI/datapilot-cli

mdesmet · 2025-06-12T07:23:44Z

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.}

.github/workflows/bump-version.yml

+
+    - name: Create Pull Request
+      id: create_pr
+      uses: peter-evans/create-pull-request@v5


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.}

Copilot

Pull Request Overview

This PR introduces automated version management and release workflows for the datapilot project. The workflows enable automatic version bumping via manual trigger and automated PyPI publishing when version bump PRs are merged.

Adds bump-version.yml workflow for manual version bumping (major/minor/patch) using bump2version
Adds tag-release.yml workflow to automatically tag and publish releases to PyPI when version bump PRs are merged
Implements a two-stage release process: version bump PR creation followed by automatic tagging and publishing

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
`.github/workflows/bump-version.yml`	Workflow for creating version bump PRs with bump2version integration
`.github/workflows/tag-release.yml`	Workflow for tagging releases and publishing to PyPI on merged version bump PRs

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2025-10-28T18:17:11Z

.github/workflows/tag-release.yml

+
+    - name: Get version from file
+      id: get_version
+      run: |


The version extraction assumes .bumpversion.cfg exists in the repository root, but this file may not be present if the version bump PR didn't commit it or if the file location differs. Add validation to check if the file exists before attempting to parse it, or the workflow will fail silently with an empty version.

Suggested change

run: |

run: |

if [ ! -f .bumpversion.cfg ]; then

echo "Error: .bumpversion.cfg not found in repository root." >&2

exit 1

fi

@copilot I think this is also fine.

It exists here: https://github.com/AltimateAI/datapilot-cli/blob/main/.bumpversion.cfg

Copilot · 2025-10-28T18:17:12Z

.github/workflows/tag-release.yml

+      env:
+        TWINE_USERNAME: __token__
+        TWINE_PASSWORD: ${{ secrets.PYPI_API_TOKEN }}
+      run: ./release.sh


The workflow depends on an external release.sh script without documenting what this script does or what prerequisites it requires. Consider adding a comment explaining the script's purpose or linking to documentation, especially since this is a critical step in the release process.

Nah, @copilot

But good suggestion!

suryaiyer95 · 2025-10-29T01:23:28Z

.github/workflows/tag-release.yml

+name: Tag Release
+on:
+  pull_request:
+    types: [closed]
+    branches: [main]


Won't this always release a tag? I think this should be manual right?

Something like|

on: push: tags: - "v*"

suryaiyer95

Overall workflow is not super clear to me. I think we should only release when we tag it

jontsai

LFTM -- no red flags. GitHub actions are kind of hard to test, and if it doesn't work, it's not that consequential -- I'm okay with iterating

jontsai · 2025-10-29T01:43:01Z

.github/workflows/tag-release.yml

+      env:
+        TWINE_USERNAME: __token__
+        TWINE_PASSWORD: ${{ secrets.PYPI_API_TOKEN }}
+      run: ./release.sh


Nah, @copilot

But good suggestion!

jontsai · 2025-10-29T01:43:31Z

.github/workflows/tag-release.yml

+
+    - name: Get version from file
+      id: get_version
+      run: |


@copilot I think this is also fine.

jontsai · 2025-10-29T01:45:36Z

.github/workflows/tag-release.yml

+
+    - name: Get version from file
+      id: get_version
+      run: |


It exists here: https://github.com/AltimateAI/datapilot-cli/blob/main/.bumpversion.cfg

Copilot · 2025-10-29T01:47:37Z

@jontsai I've opened a new pull request, #79, to work on those changes. Once the pull request is ready, I'll request review from you.

mdesmet · 2025-10-29T01:51:37Z

Overall workflow is not super clear to me. I think we should only release when we tag it

That is the case, we bump the version in a separate PR, add a label to it, when we merge that one to main, that triggers release process where a tag is created and released on PyPi

mdesmet added 2 commits June 12, 2025 15:21

feat: add version bump and tag release workflows

3cdd9e5

ci: add PyPI publishing to tag release workflow

0b4b182

mdesmet requested a review from suryaiyer95 June 12, 2025 07:23

ci: update GitHub workflows for version bump and release

90d6df2

ellipsis-dev bot reviewed Jun 12, 2025

View reviewed changes

github-advanced-security bot found potential problems Jun 12, 2025

View reviewed changes

ellipsis-dev bot reviewed Jun 12, 2025

View reviewed changes

Merge branch 'main' into chore/release-action

8be29be

mdesmet requested a review from anandgupta42 October 28, 2025 15:02

anandgupta42 requested a review from jontsai October 28, 2025 15:16

jontsai requested a review from Copilot October 28, 2025 18:16

Copilot AI reviewed Oct 28, 2025

View reviewed changes

suryaiyer95 reviewed Oct 29, 2025

View reviewed changes

jontsai approved these changes Oct 29, 2025

View reviewed changes

Copilot AI mentioned this pull request Oct 29, 2025

Address feedback on version bump and tag release workflows PR #79

Closed

mdesmet merged commit 2e41eeb into main Oct 29, 2025
39 checks passed

mdesmet deleted the chore/release-action branch October 29, 2025 13:24

mdesmet added a commit that referenced this pull request Oct 29, 2025

feat: add version bump and tag release workflows (#58)

481b949

-      run: |
+      run: |
+        if [ ! -f .bumpversion.cfg ]; then
+          echo "Error: .bumpversion.cfg not found in repository root." >&2
+          exit 1
+        fi

Comments

Conversation

mdesmet commented Jun 12, 2025 • edited by ellipsis-dev bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

ellipsis-dev bot left a comment

Choose a reason for hiding this comment

Uh oh!

Check warning

Uh oh!

ellipsis-dev bot left a comment

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull Request Overview

Reviewed Changes

Uh oh!

Copilot AI Oct 28, 2025

Choose a reason for hiding this comment

Uh oh!

jontsai Oct 29, 2025

Choose a reason for hiding this comment

Uh oh!

jontsai Oct 29, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Oct 28, 2025

Choose a reason for hiding this comment

Uh oh!

jontsai Oct 29, 2025

Choose a reason for hiding this comment

Uh oh!

suryaiyer95 Oct 29, 2025

Choose a reason for hiding this comment

Uh oh!

suryaiyer95 left a comment

Choose a reason for hiding this comment

Uh oh!

jontsai left a comment

Choose a reason for hiding this comment

Uh oh!

jontsai Oct 29, 2025

Choose a reason for hiding this comment

Uh oh!

jontsai Oct 29, 2025

Choose a reason for hiding this comment

Uh oh!

jontsai Oct 29, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI commented Oct 29, 2025

Uh oh!

mdesmet commented Oct 29, 2025

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

mdesmet commented Jun 12, 2025 •

edited by ellipsis-dev bot

Loading