Releasing to PyPI from this repo #18

Releases of this repo are published to PyPI by trusted publishing (OIDC, no tokens) from this repo's own workflows. This issue tracks what is left before the first release. It started as a question (the spec of this repo lists PyPI publishing as a non-goal, so how should releases work); the answer was to port the release workflow here (#22), and the repo now has two distributions (#66).

Distributions

• arcadedb: the GraalVM native build (the default), released by release-native.yml.
• arcadedb-jvm: the JVM build with a bundled JRE (platform wheels for Linux x86_64 and ARM64, macOS ARM64 and Windows x86_64), released by release-jvm.yml.

Both are imported as arcadedb. The tag is the bare version (26.11.1, 26.11.1.dev0, 26.11.1.post1; no v), and the same tag starts both workflows; each one checks it against its own PyPI project with scripts/check_version.py and verifies the published package after the tag with scripts/after_tag_verify.sh (#43).

Checklist

• Repo rename: the repository is ArcadeData/arcadedb-python.
• Release workflows in this repo: release-jvm.yml and release-native.yml (Add release workflow publishing to PyPI by trusted publishing #22, reworked for two distributions in Build two distributions: arcadedb (native) and arcadedb-jvm (JVM) #66).
• GitHub environments in this repo: pypi (native, project arcadedb) and pypi-jvm (project arcadedb-jvm). Neither has required reviewers.
• Trusted publishers configured on PyPI: arcadedb-jvm from release-jvm.yml with environment pypi-jvm, and arcadedb from release-native.yml with environment pypi.
• First release run end to end (tag, build, publish, after-tag verification). No release has run yet. The native readiness bar is met on main (5df565c); the first release waits for upstream ArcadeDB 26.11.1.
• Decide where the PyPI projects live. They are owned by personal PyPI accounts today, and ArcadeData has no PyPI organization (the organization named arcadedb lists no projects). This does not block the first release.
• Retire the old names after the first release from here (planned): arcadedb-embedded becomes a shim that installs arcadedb, arcadedb-embedded-native is archived, and arcadedb-native stays reserved.

Until a release from this repo has worked end to end, nothing changes for users of the existing packages.