fix(ci): resolve beta release workflow failures #107
Merged
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.
π¨ CRITICAL BUG FIX
Beta workflow was accidentally publishing STABLE releases to PyPI instead of beta releases!
Root Cause Analysis
4.2.0b3
v4.2.0b3
(Pre-release)datafog-4.2.0
(STABLE VERSION)Problem:
setup.py
had hardcodedversion = '4.2.0'
that overrode the beta version during package build.Fixes Applied
setup.py Version Management
datafog/__about__.py
Workflow Cleanup
sed
command forsetup.py
__about__.py
)Changelog Script Arguments
--beta
and--output
flag supportopen BETA_CHANGELOG.md: no such file or directory
Beta Version Auto-Increment
git fetch --tags
for complete tag historyv4.2.0b1
βv4.2.0b2
βv4.2.0b3
Impact
4.2.0
to PyPI (β)4.2.0b4
to PyPI (β )Validation
β Local testing confirms
setup.py
now reads beta versions correctlyβ Version detection logic works: finds next available beta number
β Changelog generation works with
--beta --output BETA_CHANGELOG.md
This is a critical fix to prevent accidental stable releases.