Skip to content

chore: Publish packages to GitHub release corresponding to highest-versioned tag reachable from the current branch #223

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
AlexDanDuna merged 2 commits into from
Jul 24, 2026
Merged

chore: Publish packages to GitHub release corresponding to highest-versioned tag reachable from the current branch #223

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
373a535
Modify semantic-release publish to use latest GitHub release tag reac…
AlexDanDuna Jul 16, 2026
f8403e1
Improve comment
AlexDanDuna Jul 16, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 8 additions & 2 deletions .github/workflows/python-package.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -93,10 +93,16 @@ jobs:
TWINE_USERNAME: ${{secrets.REPOSITORY_USERNAME}}
TWINE_PASSWORD: ${{secrets.PYPI_PASSWORD}}
- name: Semantic release - Publish package distributions to GitHub Releases
# Only publish if Semantic release built packages under "dist/"; hashFiles returns '' when no files match the given pattern.
# Only publish if Semantic release built packages under "dist/"; hashFiles returns '' when no files match the given pattern.
if: hashFiles('dist/*') != ''
run: |
semantic-release publish
# Publish packages to the latest GitHub release reachable from the current branch.
# This is so that releases from maintenance branches (e.g. "1.6.x") don't upload
# packages to the highest-versioned release on the repo (default behavior of
# 'publish' when no tag is passed), which would likely be one that was published
# from master.
RELEASE_TAG="$(git describe --tags --abbrev=0)"
semantic-release publish --tag "$RELEASE_TAG"
env:
# To generate a new token use the following guide, providing access to the "repo" scope.
# https://docs.github.com/en/enterprise-server@3.4/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token
Expand Down
Loading