Org migration: update Python and TypeScript SDK package metadata

[zeevdr]

Description

Update repository URLs, metadata, and trusted publisher configs for the Python and TypeScript SDK packages.

Python SDK (PyPI)

Package metadata (decree-python)

• sdk/pyproject.toml — update all project.urls entries to opendecree org
• README.md — update any GitHub links

Trusted publisher (pypi.org)

• On pypi.org → opendecree package → Publishing → update trusted publisher:
  • Repository: zeevdr/decree-python → opendecree/decree-python
  • Environment: pypi (must exist in the new org repo)
  • Workflow: publish.yml
• Create pypi environment in opendecree/decree-python repo settings
• Test with a pre-release publish before removing old config

TypeScript SDK (npm)

Package metadata (decree-typescript)

• package.json — update homepage, repository.url, bugs.url
• README.md — update any GitHub links

Trusted publisher (npmjs.com)

• On npmjs.com → @opendecree/sdk → Settings → Trusted Publishers, update:
  • Repository: zeevdr/decree-typescript → opendecree/decree-typescript
  • Environment: npm (must exist in the new org repo)
• Create npm environment in opendecree/decree-typescript repo settings
• Test with a pre-release publish before removing old config

Buf Schema Registry (buf.build)

• On buf.build → opendecree/decree module settings, verify it accepts pushes from opendecree/decree GitHub repo
• Regenerate BUF_TOKEN if it's scoped to zeevdr (or create new one for org)
• Add BUF_TOKEN as org secret in opendecree org

Notes

• PyPI package name (opendecree) and npm package name (@opendecree/sdk) do NOT change
• Both use OIDC trusted publishing — no secret tokens, but the GitHub repo must match
• Test publishes before archiving old repos

[zeevdr]

Completed — migrated to opendecree org.