Publish checklist

Publish checklist

Abstract

Ship hoox-pyne from GitHub hoox-sh/pyne while owning the PyPI project under the personal account jango-blockchained. A PyPI organization is not required (and is not used while org approval is pending).

0. Identity map

1. Confirm repo host (hoox-sh/pyne)

The GitHub repo already lives at hoox-sh/pyne. If a checkout still points at the old personal remote, retarget it:

git remote set-url origin https://github.com/hoox-sh/pyne.git
git remote -v
gh repo view --json nameWithOwner,url
# expect: hoox-sh/pyne

Automation secrets

gh secret set METADATA_KEY -R hoox-sh/pyne < scripts/build/.metadata.key
gh secret set CRYPTO_KEY   -R hoox-sh/pyne < scripts/build/.metadata.key
# optional marketplace:
# gh secret set VSCE_PAT -R hoox-sh/pyne

2. PyPI under personal account jango-blockchained

Preferred — API token

1. pypi.org as jango-blockchained → API tokens → add token.
2. gh secret set PYPI_API_TOKEN -R hoox-sh/pyne
3. First upload creates project hoox-pyne owned by your user.

Optional — Trusted Publishing

Log in as jango-blockchained (personal), then pending publisher:

Leave PYPI_API_TOKEN unset to force OIDC. Do not put your PyPI username in the GitHub Owner field.

Details: PyPI publish.

3. Local package smoke (no upload)

# version already 0.6.4 in src/pynescript/__about__.py
pip install build twine
rm -rf dist/
python -m build
twine check dist/*
# expect: hoox_pyne-0.6.4-py3-none-any.whl  hoox_pyne-0.6.4.tar.gz

python -m venv /tmp/pyne-smoke
/tmp/pyne-smoke/bin/pip install dist/*.whl
/tmp/pyne-smoke/bin/python -c "import pynescript; print(pynescript.__version__)"
/tmp/pyne-smoke/bin/pyne --help

4. GitHub Actions dry-run

1. Push main with publish-ready tree to hoox-sh/pyne.
2. Confirm CI green (lint, test matrix, package, docker, vscode-ext).
3. Actions → Publish → Run workflow → dry_run=true (build + twine only, no upload).

5. Cut v0.6.4

1. Move CHANGELOG.md Unreleased notes into ## [0.6.4] - YYYY-MM-DD.
2. Align VSIX version in vscode-extension/package.json (already 0.4.4) if shipping Marketplace/VSIX with this tag.
3. Tag and push:

git tag -a v0.6.4 -m "v0.6.4"
git push origin v0.6.4

4. Watch in parallel:
   • Publish → PyPI hoox-pyne
   • Build & Release → GitHub Release assets + optional Marketplace
   • GHCR → ghcr.io/hoox-sh/pyne/{api,cli,lsp}:0.6.4

6. Post-publish verify

pip index versions hoox-pyne   # or: pip install hoox-pyne==0.6.4
python -c "import pynescript; print(pynescript.__version__)"
# GitHub Release: https://github.com/hoox-sh/pyne/releases/tag/v0.6.4
# PyPI: https://pypi.org/project/hoox-pyne/0.6.4/

Hardcoded owner map (repo automation)

Workflows use relative github.* context (no hard-coded owner) except documentation/comments. Project metadata and docs must point at hoox-sh/pyne:

Intentionally not changed

See also

• PyPI publish
• Release — LSP + VSIX
• CI
• Root CONTRIBUTING.md