Skip to content

Dev release: pin one engine snapshot for both packages and record it in the wheels #304

Closed

Description

@tae898

A .devN tag cannot yet publish both packages with the same engine. release-native.yml links the release engine (DEV_ENGINE, 26.11.1) and refuses a snapshot on a release run, while release-jvm.yml takes the floating image tag latest, which is now the 26.12.1-SNAPSHOT engine with the columnar faceting. A 26.12.1.dev0 tag would publish arcadedb with 26.11.1 and arcadedb-jvm with the snapshot, and neither wheel states which snapshot it holds.

I will pin one snapshot for both packages in scripts/dev_engine_pin.json (image digest plus the sha256 of every arcadedb-*.jar), prove before and after the build that the JVM image and the Sonatype jars are exactly those jars, allow it only for A.B.C.devN of the pinned base (a final or .postN release still refuses a snapshot, with a test), and record the snapshot and the image digest in each wheel (arcadedb.ENGINE_SNAPSHOT, arcadedb.ENGINE_IMAGE_DIGEST).

Activity

  1. added
    jvmThe arcadedb-jvm package (JPype build)
    pythonPull requests that update python code
    on Nov 7, 2026
  2. added this to the 26.12.1 milestone on Nov 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    in progressThe team is actively working on this issuejvmThe arcadedb-jvm package (JPype build)pythonPull requests that update python code

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions