Skip to content

Publish falsely fails when npm latest dist-tag propagation exceeds 25 seconds #396

Description

@khaliqgant

Problem

Stable 8.6.0 publish run 34309993642 successfully published all eight immutable package artifacts, but the publish jobs for @relaycast/types and @relaycast/openclaw failed because npm still reported latest=8.5.5 after the current five 5-second verification attempts.

The independent reconciliation job later observed types correctly, but still exhausted its window before openclaw became visible. By the time the workflow completed, all eight exact versions and latest mappings resolved to 8.6.0. The workflow therefore safely withheld the Git tag/release, but reported a failed partial release that required a full resumable retry.

Evidence:

  • @relaycast/types publish completed at 04:14:17Z; tag verification failed at 04:14:39Z.
  • @relaycast/openclaw publish completed at 04:14:57Z; tag verification failed at 04:15:19Z.
  • Reconciliation observed types at 04:16:08Z and exhausted openclaw at 04:17:30Z.
  • Both packages subsequently resolved with latest=8.6.0 and matching immutable provenance.

Expected

Absorb realistic npm package/dist-tag propagation delay without turning a successful immutable publish into a failed release. Keep retries bounded and fail closed for true missing, stale, ambiguous, or integrity-mismatched artifacts. Add deterministic timing/propagation contract tests and preserve resumable exact-artifact behavior.

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