Build & Publish Package / publish (push) Successful in 58s
Package Extension / package-extension (push) Successful in 1m17s
Testing / test (3.10) (push) Successful in 1m15s
Testing / test (3.12) (push) Successful in 1m8s
Testing / test (3.15) (push) Successful in 9m38s
Testing / remote-protocol-compat (0.15.0) (push) Successful in 9m20s
Testing / remote-protocol-compat (0.16.0) (push) Successful in 8m54s
Testing / test (3.14) (push) Successful in 55s
- Move token lookup into scripts/pypi_token.sh, shared by both recipes - Resolve UV_PUBLISH_TOKEN, then .env, then pass api/packages/pypi - Fail with a clear hint instead of dropping into an interactive prompt - Never print the token, only its length - Gate publish behind version-check so version drift stops the build - Add publish-dry, same path as publish but with uv publish --dry-run - Pass --check-url so re-runs skip files already on PyPI - Hoist dist dir, token entry, and check URL into justfile variables - Add .env and .env.* to .gitignore The old recipe sourced .env for credentials, but .env was never ignored, so a token file dropped there would have been committed and shipped inside the sdist. Verified token precedence for env, .env and password-store, the missing-token exit code, the version-check gate, and a dry run against an unpublished version.
21 lines
229 B
Plaintext
21 lines
229 B
Plaintext
# TypeScript / Node
|
|
extension/background.js
|
|
extension/content-dispatch.js
|
|
extension/test-dist/
|
|
node_modules/
|
|
dist/
|
|
|
|
# Local secrets / signing keys
|
|
secrets/
|
|
*.pem
|
|
*.pem.gpg
|
|
.env
|
|
.env.*
|
|
|
|
# Python
|
|
__pycache__/
|
|
*.pyc
|
|
|
|
# IDE
|
|
.vscode/
|