Skip to content

chore: change publish to pypi to use tag ref instead of release branch.#252

Merged
epmog merged 1 commit intoOpenJobDescription:mainlinefrom
erico-aws:change_pypi_release_tag
Jul 7, 2025
Merged

chore: change publish to pypi to use tag ref instead of release branch.#252
epmog merged 1 commit intoOpenJobDescription:mainlinefrom
erico-aws:change_pypi_release_tag

Conversation

@erico-aws
Copy link
Contributor

What was the problem/requirement? (What/Why)

The PublishToPyPI job was still pointing to the release branch. It should be looking at a tag now.

What was the solution? (How)

Change the reference to point to tag created during the PublishToPyPI job. It should be noted that the Publish job doesn't have an output anymore, so we need to use the output from TagRelease. (The other jobs in here also use the tag output from TagRelease).

What is the impact of this change?

Allow for PyPi releases./

How was this change tested?

N/A

Was this change documented?

No.

Is this a breaking change?

No.

Does this change impact security?

No.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@erico-aws erico-aws requested a review from a team as a code owner July 3, 2025 16:19
Signed-off-by: Eric Osiowy <134728121+erico-aws@users.noreply.github.com>
@epmog epmog force-pushed the change_pypi_release_tag branch from 82f4375 to 9309de7 Compare July 7, 2025 15:19
@epmog epmog enabled auto-merge (squash) July 7, 2025 15:19
@sonarqubecloud
Copy link

sonarqubecloud bot commented Jul 7, 2025

@epmog epmog merged commit 13b93f5 into OpenJobDescription:mainline Jul 7, 2025
19 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.

3 participants