Skip to content

fix(release): correct build fetch depth and upgrade pypi publish workflow#10

Merged
markurtz merged 1 commit into
mainfrom
feat/release-fixes
May 12, 2026
Merged

fix(release): correct build fetch depth and upgrade pypi publish workflow#10
markurtz merged 1 commit into
mainfrom
feat/release-fixes

Conversation

@markurtz
Copy link
Copy Markdown
Owner

Description

  • Build Package Fix: Added fetch-depth: 0 to the actions/checkout step within .github/workflows/_build_package.yml. This ensures the full git history is fetched during the build process, which is necessary for gitversioned to accurately compute the package version based on git tags and commit history rather than a shallow clone.
  • Publish Action Update: Updated the pypa/gh-action-pypi-publish action in .github/workflows/_publish.yml from v1.8.14 to v1.14 to utilize the latest features and bug fixes for PyPI publishing.

Type of Change

  • 🐛 Bug fix (non-breaking change which fixes an issue)
  • ✨ New feature (non-breaking change which adds functionality)
  • 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • 📝 Documentation update (changes to README.md, SUPPORT.md, docstrings, etc.)
  • 🛠️ Maintenance/Refactoring (non-breaking change that improves code structure or quality)

Test Plan

  • Verify that CI/CD package build workflows complete successfully and generate artifacts with the correct git-derived versions.
  • Ensure that the automated workflow for publishing to PyPI executes without errors using the updated action version.

Related Issues

  • N/A

Screenshots / Visuals (if applicable)

N/A

Use of AI

  • Includes AI-assisted code completion
  • Includes code generated by an AI application
  • Includes AI-generated tests (NOTE: AI written tests should have a docstring that includes ## WRITTEN BY AI ##)

Checklist

Important

Please review and complete this checklist before submitting your PR. This helps our maintainers process your contribution faster and ensures it meets the quality standards of gitversioned.

  • "I certify that all code in this PR is my own, except as noted below."
  • I have read the CONTRIBUTING.md guide.
  • My code follows the established style guidelines of gitversioned.
  • I have performed a self-review of my own code.
  • I have commented my code, particularly in hard-to-understand areas.
  • I have made corresponding changes to the documentation.
  • My changes generate no new warnings or errors.
  • I have added tests that prove my fix is effective or that my feature works.
  • New and existing unit tests pass locally with my changes.

@github-actions
Copy link
Copy Markdown
Contributor

CI Development Pipeline Status

Pipeline: Completed successfully. View Run Details

@markurtz markurtz merged commit c24223e into main May 12, 2026
15 checks passed
@markurtz markurtz deleted the feat/release-fixes branch May 12, 2026 17:40
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the CI/CD reusable workflows to ensure package versioning can be derived from full Git history during builds, and modernizes the PyPI publish action used in releases.

Changes:

  • Configure actions/checkout in the reusable build workflow to fetch full history (fetch-depth: 0) so git-derived versioning works reliably.
  • Upgrade the pinned commit for pypa/gh-action-pypi-publish used by the reusable publish workflow.

Reviewed changes

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

File Description
.github/workflows/_build_package.yml Fetch full Git history during package builds to support git-based version calculation.
.github/workflows/_publish.yml Update the pinned PyPI publish action revision to the newer v1.14 line.

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

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.

2 participants