fix: REGISTRY_TOKEN for publish #6

Merged
john merged 2 commits from dev into main 2026-05-16 12:44:24 +00:00
Owner

Secret name fix.

Secret name fix.
fix: use REGISTRY_TOKEN secret for PyPI publish
All checks were successful
CI / Detect Changes (pull_request) Successful in 3s
CI / Lint & Format (pull_request) Successful in 5s
CI / Unit Tests (pull_request) Successful in 9s
0364896b8d
Forgejo reserves the FORGEJO_ prefix for secret names.
Use REGISTRY_TOKEN to match the org convention.
Merge pull request 'fix: use REGISTRY_TOKEN for PyPI publish' (#5) from feat/fix-publish-secret into dev
All checks were successful
CI / Detect Changes (push) Successful in 3s
CI / Unit Tests (push) Successful in 7s
CI / Lint & Format (push) Successful in 10s
5dc41f54fe
john merged commit 088d5bec16 into main 2026-05-16 12:44:24 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
haskytech/haskytech-modules-py!6
No description provided.