Skip to content

fix: wait for release write visibility - #21

Merged
jinxiao merged 1 commit into
mainfrom
fix/release-visibility
Oct 4, 2026
Merged

jinxiao merged 1 commit into
mainfrom
fix/release-visibility

Conversation

@jinxiao

@jinxiao jinxiao commented Oct 4, 2026

Copy link
Copy Markdown
Contributor

Issue

Closes #20
Refs #15

Summary

A hosted publication stopped immediately after GoReleaser successfully created a correctly reviewed draft because the next API lookup did not yet see it. Wait up to 30 seconds after successful creation or finalization, checking frozen content on every observation. Preserve all existing release objects and resume the original PR #16 batch.

Testing

  • 33 offline release regressions passed with pinned GoReleaser OSS v2.18.2, including delayed draft/finalization, timeout preservation, and immediate conflict/API-error propagation.
  • git diff --check passed before commit.
  • Required native PR checks will validate hosted documentation and modules.

Risks and compatibility

No module source, versions, tags, or frozen notes change. The wait occurs only after a successful publication write; API failures are not retried and GoReleaser writes are not repeated.

Release notes

  • repository | fix | Wait briefly for newly written Releases to become visible before continuing publication.

Checklist

  • The issue records the scope and acceptance criteria
  • Tests and documentation match the change, or I explained why they are not applicable
  • I kept CGO disabled and did not run cloud AWS tests without authorization
  • I excluded credentials, personal configuration, and generated build artifacts

@jinxiao
jinxiao merged commit ec3d4a3 into main Oct 4, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: Release publication reads newly created drafts before they are visible

1 participant