Skip to content

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

Closed

Description

@JonZeolla

Bug Report

Description

I have been doing a two-step process to use psr to stage changes before making a release as discussed in #1125, but 10.3.0 introduced a breaking change for this workflow

Expected behavior

It should properly stage changes without requiring a commit_sha

Actual behavior

A commit_sha is required as of 39b647b when running semantic-release version ... inside of a GitHub Actions pipeline. If I set GITHUB_OUTPUT locally then I can see the error:

$ GITHUB_OUTPUT=foo uv run --frozen semantic-release version --no-changelog --skip-build --no-commit --no-tag --no-push --no-vcs-release
WARNING:root:Found .git/ in higher parent directory rather than provided in configuration.
[10:11:06] WARNING  Token value is missing!                                                                                                              config.py:779
WARNING:semantic_release:Token value is missing!
1.5.0
The next version is: 1.5.0! 🚀
Skipping build due to --skip-build flag
::ERROR:: some required outputs were not set: commit_sha
Run semantic-release in very verbose mode (-vv) to see the full traceback.

Activity

  1. added
    bugSomething isn't working properly
    triagewaiting for initial maintainer review
    on Aug 4, 2025
  2. gbrown-lendica commented on Aug 4, 2025

    @gbrown-lendica

    My team is experiencing the same issue. We run python-semantic-release to determine the tag to use for builds generated as part of testing PRs, using the following inputs:

    uses: python-semantic-release/[email protected]
    with:
      github_token: ${{ secrets.GH_TOKEN_PYTHON_SEMANTIC_RELEASE }}
      prerelease_token: pr-${{ steps.short-sha.outputs.SHORT_SHA }}
      commit: false
      tag: false
      push: false
      changelog: false
      strict: true
      verbosity: 0
  3. codejedi365 commented on Aug 4, 2025

    @codejedi365
    Contributor

    Thanks, this was not intentional but an unexpected side effect. Will push a patch tomorrow.

  4. added
    confirmedPrevent from becoming stale
    and removed
    triagewaiting for initial maintainer review
    on Aug 5, 2025
  5. added 5 commits that reference this issue on Aug 6, 2025
    259d88e
    efac895
    e284fdb
    616e10d
    ac2f239
  6. added a commit that references this issue on Aug 6, 2025
    5385724
  7. codejedi365 commented on Aug 6, 2025

    @codejedi365
    Contributor

    🎉 This issue has been resolved in 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

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working properlyconfirmedPrevent from becoming stale

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions