Fixing PyPI release #144
Merged
Fixing PyPI release #144
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR fixes the PyPI release workflow by ensuring complete Git history is available during the build process. The change adds fetch-depth: 0 to all checkout actions in the Python release workflow.
Key changes:
- Adds
fetch-depth: 0parameter to allactions/checkout@v5steps - Ensures full Git history is fetched instead of shallow clone (default depth of 1)
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
github-actions bot
pushed a commit
that referenced
this pull request
Sep 26, 2025
* style: * Checkout full history
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.