Skip to content

Reconcile TreeDX binding drift at an unchanged GitHub head #433

Description

@adrianwebb

SDK library binding contentRepositoryRef is bc530039 while GitHub staging and fetched refs/remotes/origin/staging are ac322d24. The existing remote-head scheduler keys operations only by project, publication ref and remote head. If a previously succeeded operation for ac322d24 exists and the library binding later drifts, createPlatformOperation returns that succeeded operation, which the scheduler does not retry; the binding remains stale indefinitely. Make idempotency include the local library binding version/state, preserve exact-head checks, and cover repeated scheduling plus later drift in a focused regression. This is a concrete hypothesis from observed drift and code; confirm via local development read-back. Platform #520 records SDK BQ evidence.

Activity

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions