Skip to content

Bump version to 0.3.8 and check release tag matches version - #129

Merged
marcovarrone merged 1 commit into
mainfrom
fix-release-version-0.3.8
Oct 19, 2026
Merged

marcovarrone merged 1 commit into
mainfrom
fix-release-version-0.3.8

Conversation

@marcovarrone

@marcovarrone marcovarrone commented Oct 19, 2026 •

Copy link
Copy Markdown
Collaborator

The v0.3.8 release run (job) failed with `400 File already exists ('cellcharter-0.3.7-py3-none-any.whl')`. The v0.3.8 tag points at a commit where `pyproject.toml` still had `version = "0.3.7"`, so the build produced 0.3.7 artifacts, which PyPI already has.

Changes:

  • Set `version = "0.3.8"` in `pyproject.toml`.
  • Add a step to the release workflow that fails before the build if the release tag isn't `v`.

After merging, the v0.3.8 tag must point at the merge commit before publishing again. Re-running the failed job would check out the old tag and fail the same way. Either delete the v0.3.8 release and tag and recreate them on the new commit, or move the tag and publish the release again.

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Release
    • Updated the package to version 0.3.8.
    • Release publishing now checks that the release tag matches the package version before publication, helping prevent mismatched releases.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Oct 19, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration
  • Configuration used: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 7f6c31ec-d4cf-499f-b61b-328eb9e75f9a
📥 Commits

Reviewing files that changed from the base of the PR and between 210ac53 and 0610b84.

📒 Files selected for processing: 2
  • .github/workflows/release.yaml
  • pyproject.toml

Included review availability: This review used your included allowance. Your plan provides up to 2 included reviews per hour; 1 remain after this review.

📝 Walkthrough

The project version changes from 0.3.7 to 0.3.8. The release workflow checks that the release tag matches the project version before package build and PyPI publication.

Changes: Release version validation

Layer / File(s) Summary
Version bump and release-tag validation
pyproject.toml, .github/workflows/release.yaml
The project version changes to 0.3.8. The release workflow compares the v-prefixed version with the release tag and exits with an error if they differ.

Priority: ➖ Normal

Estimated code review effort: 2 (Simple) | ~8 minutes

Change: Bug fix

Suggested reviewers: scverse-bot

Merge Risk: ⚪ Minimal · up to 0610b

Published releases with a tag that does not match the declared version now stop before packaging or publication. The check uses the release tag correctly, and no actionable merge risk remains.

Pre-merge checks: Passed 5
Check name Status Explanation
Description Check Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check Passed The title clearly and concisely describes both main changes: the version bump to 0.3.8 and the release-tag validation.
Docstring Coverage Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (2 skipped: 2 unsupported.)

✨ Finishing Touches: 💡 1
🛠️ Fix failing CI checks: 💡
  • Commit to this branch
  • Create a new PR
🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@codecov

codecov Bot commented Oct 19, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 70.61%. Comparing base (210ac53) to head (0610b84).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #129   +/-   ##
=======================================
  Coverage   70.61%   70.61%           
=======================================
  Files          23       23           
  Lines        1698     1698           
=======================================
  Hits         1199     1199           
  Misses        499      499           
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@marcovarrone
marcovarrone merged commit 20ea3f7 into main Oct 19, 2026
8 of 9 checks passed
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