Repository navigation
docs: the publish window is wider than four minutes - #57
Merged
elvogel merged 2 commits intoOct 16, 2026
Merged
Conversation
The release workflow's "Version is not already published" gate reads the flat-container index, which lags the push. The comment recorded that lag as roughly four minutes, measured once, on 0.2.5. 0.3.0 took 400 seconds. At the moment the index first listed it, `dotnet tool install --version 0.3.0` still answered "not found in NuGet feeds", because the registration and search services lag the flat container again. So the window to treat as unsafe for a re-tag is about ten minutes, not four, and a fresh install is the slower signal rather than the earlier one. Comment only. The gate is unchanged, and so is the hole it leaves: a re-tag inside the window, which is still narrower than the hole it closes. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018wZEgtuzaZPswykiGEBxbz
The first commit said only that `dotnet tool install` could not resolve 0.3.0 at the moment the flat container listed it. It resolved 160 seconds after that, which puts a usable install about ten minutes after the push and is the measurement the "ten minutes rather than four" rests on. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018wZEgtuzaZPswykiGEBxbz
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Comment only, in
.github/workflows/release.yml. Nothing executable changes.The
Version is not already publishedgate reads the flat-container index, and the commentabove it recorded the index's lag behind a push as "roughly four [minutes] for 0.2.5" -- one
measurement, from one release.
Publishing 0.3.0 gave a second one, and it is worse. Measured from the moment the
Publishstepsucceeded:
dotnet tool install --version 0.3.0resolvesBefore that last point the install answered
Version 0.3.0 of package docmd.cli is not found in NuGet feeds, so the registration and search services lag the flat container again.The comment now says to treat the window as about ten minutes rather than four, and records
which signal is the slow one. A fresh install looks like the stronger check and is actually the
later one, so it cannot be the gate either.
The gate itself is unchanged and so is the hole it leaves -- a re-tag inside the window -- which
is still much narrower than the hole it closes:
--skip-duplicatemakes a re-tag of a publishedversion go green while uploading nothing.
🤖 Generated with Claude Code
https://claude.ai/code/session_018wZEgtuzaZPswykiGEBxbz