Skip to content

Conversation

@codejedi365
Copy link
Contributor

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/release-failure-on-no-commited-changes branch 4 times, most recently from ed4bf9e to 5ee8130 Compare November 10, 2025 18:05
@codejedi365 codejedi365 force-pushed the fix/release-failure-on-no-commited-changes branch from 5ee8130 to abcaa73 Compare November 10, 2025 18:49
@codejedi365 codejedi365 merged commit e0b3b70 into python-semantic-release:master Nov 10, 2025
9 checks passed
@codejedi365 codejedi365 deleted the fix/release-failure-on-no-commited-changes branch November 10, 2025 19:06
@codejedi365
Copy link
Contributor Author

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

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant