chore(ci): only publish to PyPI if a new release was created#38
Merged
chore(ci): only publish to PyPI if a new release was created#38
Conversation
ctreatma
force-pushed
the
check_if_released
branch
from
8bb17f4 to
523c89c
Compare
Contributor
Author
|
Sample run demonstrating that the publish step is skipped, at least, can be found here: https://github.com/equinix/equinix-sdk-python/actions/runs/12380553183 The opposite behavior can be verified on the next release of this SDK. |
ctreatma
force-pushed
the
check_if_released
branch
from
523c89c to
e349274
Compare
displague
approved these changes
Dec 18, 2024
Contributor
|
This PR is included in version 0.7.0 🎉 |
1 similar comment
Contributor
|
This PR is included in version 0.7.0 🎉 |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The semantic release GitHub Action will skip creating a new GitHub release if there are no new releasable changes. This is expected, but the release workflow assumed that there was always a new release to publish to PyPI.
This PR updates the release workflow to move the PyPI publish steps to a separate job that will only run if the release job successfully creates a new release.