You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
Release 0.9.5 (#54)
Bumps `VersionPrefix` so the Store stage can be exercised with the
upload timeout fix
from #52.
A pipeline run uses the YAML on `main` as of that run, so #52 could not
be applied to
0.9.4 after the fact, and the Release stage refuses to reuse an existing
tag — which is
what the failed run after #52 merged was showing.
## No product change
Everything on `main` since `v0.9.4` is pipeline and documentation. The
binaries are
identical to 0.9.4; this release exists to put a version through the
Store stage.
## What the run should show
Two paths get their first real test, in this order:
1. **Clearing the abandoned submission.** The failed 0.9.4 attempt left
one in
`PendingCommit`. The stage deletes exactly that state and continues; any
other status
still fails untouched.
2. **The upload.** With `--uploadTimeout` set, the blob client no longer
gets a zero
network timeout. Publish runs verbose, so a failure reports its own
exception instead
of one swallowed line.
If it fails anyway, the GitHub release is already published by then and
every download is
unaffected — the stage runs after Release for exactly that reason.
## Verified locally
`dotnet build Whiteboard.sln -c Release` clean, no warnings; Core smoke
tests pass.