Skip to content

chore: release v7.0.0a1 + fix release workflow#359

Merged
isaackogan merged 1 commit into
masterfrom
release/v7.0.0a1
Apr 30, 2026
Merged

chore: release v7.0.0a1 + fix release workflow#359
isaackogan merged 1 commit into
masterfrom
release/v7.0.0a1

Conversation

@isaackogan

Copy link
Copy Markdown
Owner

Summary

  • Stamp v7.0.0a1 into pyproject.toml + TikTokLive/__version__.py. PyPI publish for this version already succeeded out of band (https://pypi.org/project/TikTokLive/7.0.0a1/); the v7.0.0a1 tag now points at this commit so the source matches the wheel.
  • Fix .github/workflows/release.yml: previous run failed because the post-publish step pushed the version-bump commit directly to master, which is rejected by the branch-protection rule (GH006). Workflow now creates the bump locally, pushes the tag (tags aren't branch-protected), and opens a PR via peter-evans/create-pull-request@v7 for the bump itself.

Test plan

  • git tag v7.0.0a1 pushed → visible on origin
  • PyPI release 7.0.0a1 reachable
  • Next release (workflow_dispatch) opens a PR cleanly without GH006

- Stamp v7.0.0a1 into pyproject.toml + TikTokLive/__version__.py
  (PyPI publish already succeeded for this version; tag below points at this commit)
- Switch the release workflow's "commit version bump" step to open a PR
  instead of pushing directly to master. Direct pushes from
  ``github-actions[bot]`` are rejected by the GH006 protected-branch
  hook. Tag is still pushed directly (tags aren't governed by the
  branch-protection rule).
@isaackogan isaackogan merged commit c014a76 into master Apr 30, 2026
1 check passed
@isaackogan isaackogan deleted the release/v7.0.0a1 branch April 30, 2026 06:00
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