Skip to content

fix(release): sync 2.5.7 with PyPI + safer release workflows#12

Merged
abdulgeek merged 1 commit into
masterfrom
sync/pypi-2.5.7-and-release-ci
Apr 30, 2026
Merged

fix(release): sync 2.5.7 with PyPI + safer release workflows#12
abdulgeek merged 1 commit into
masterfrom
sync/pypi-2.5.7-and-release-ci

Conversation

@abdulgeek

Copy link
Copy Markdown
Contributor

Summary

  • Align master package metadata with PyPI cost-katana==2.5.7 (setup.py, __version__, User-Agent, CHANGELOG).
  • Auto Release: workflow_dispatch only; Twine runs only after commit + tag push succeed (no more PyPI-without-Git drift). Optional repo secret RELEASE_PUSH_TOKEN (PAT with contents:write + bypass on protected master) when GITHUB_TOKEN cannot push.
  • Version Bump: workflow_dispatch only (removes failing push hooks on every merge); updates client.py UA; same PAT pattern; removed redundant publish.yml API dispatch (tag push triggers publish).

After merge (you)

If v2.5.7 still does not exist on GitHub, create it on the merge commit:

git checkout master && git pull
git tag -a v2.5.7 -m "Release 2.5.7"
git push origin v2.5.7

Add RELEASE_PUSH_TOKEN in repo Settings → Secrets if you want manual Auto Release / Version Bump workflows to push master without opening PRs.

- Bump setup.py, __version__, User-Agent; CHANGELOG [2.5.7].
- Auto Release: workflow_dispatch only; PyPI after successful git push; RELEASE_PUSH_TOKEN optional for protected master.
- Version Bump: workflow_dispatch only; update client UA; PAT for push; drop redundant publish dispatch.
@abdulgeek abdulgeek merged commit f66605b into master Apr 30, 2026
8 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.

1 participant