fix(github-actions): refactor the action output error checking for non-release executions by codejedi365 · Pull Request #1308 · python-semantic-release/python-semantic-release

Skip to content

Navigation Menu

Sign in

Appearance settings

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up

Appearance settings

Conversation

@codejedi365

Copy link

Contributor

@codejedi365 codejedi365 commented

Aug 6, 2025

edited

Loading

Purpose

Rationale

How did you test?

How to Verify


PR Completion Checklist

  • Reviewed & followed the Contributor Guidelines

  • Changes Implemented & Validation pipeline succeeds

  • Commits follow the Conventional Commits standard
    and are separated into the proper commit type and scope (recommended order: test, build, feat/fix, docs)

  • Appropriate Unit tests added/updated

  • Appropriate End-to-End tests added/updated

  • Appropriate Documentation added/updated and syntax validated for sphinx build (see Contributor Guidelines)

@codejedi365 codejedi365 force-pushed the fix/github-actions-outputs branch 4 times, most recently from 728a58e to 7b4c02e Compare

August 6, 2025 03:30

@codejedi365 codejedi365 force-pushed the fix/github-actions-outputs branch from 7b4c02e to ac2f239 Compare

August 6, 2025 03:33

@codejedi365 codejedi365 changed the title ci: test broken v10.3.0 fix(github-actions): refactor the action output error checking for non-release executions

Aug 6, 2025

@codejedi365 codejedi365 merged commit 5385724 into python-semantic-release:master

Aug 6, 2025

13 checks passed

@codejedi365 codejedi365 deleted the fix/github-actions-outputs branch

August 6, 2025 04:22

@codejedi365

Copy link

Contributor Author

🎉 This PR has been published as part of v10.3.1 🎉

You can find more information about this release on the GitHub Releases page.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

10.3.0 doesn't support a stage-then-release approach in GitHub Actions

1 participant

@codejedi365