Commit e2b5858
authored
fix(release): add non-blocking Maven Central propagation verify (#175)
Previously the workflow reported "Deploy successful" the moment Sonatype
Central validated the upload (per the v8.0.0 release at 2026-05-09 15:37Z),
then proceeded straight to creating the GitHub Release. But actual public
availability on `repo1.maven.org/maven2` lags by 10-30 minutes for
typical releases — operators were left guessing whether the release was
truly consumable.
Add a polling step between `mvn deploy` and the GitHub Release that
checks `repo1.maven.org` for the artifact .pom directly. Up to 30
minutes (60 × 30s). Non-blocking via `continue-on-error: true` so that:
- Fast propagation: workflow reports Maven Central availability in
under a minute and the GH release fires.
- Slow propagation (>30min): polling step warns and the GH release
still fires, leaving the operator with a clear pointer to the
Sonatype publish dashboard for follow-up.
Verified locally that the new polling logic returns success on first
attempt against both the prior v7.1.0 release and the just-published
v8.0.0 (which has now propagated since the v8.0.0 release ran).
Signed-off-by: Saurabh Jain <saurabhjain1592@gmail.com>1 parent 551dfbf commit e2b5858
1 file changed
Lines changed: 27 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
164 | 164 | | |
165 | 165 | | |
166 | 166 | | |
| 167 | + | |
| 168 | + | |
| 169 | + | |
| 170 | + | |
| 171 | + | |
| 172 | + | |
| 173 | + | |
| 174 | + | |
| 175 | + | |
| 176 | + | |
| 177 | + | |
| 178 | + | |
| 179 | + | |
| 180 | + | |
| 181 | + | |
| 182 | + | |
| 183 | + | |
| 184 | + | |
| 185 | + | |
| 186 | + | |
| 187 | + | |
| 188 | + | |
| 189 | + | |
| 190 | + | |
| 191 | + | |
| 192 | + | |
| 193 | + | |
167 | 194 | | |
168 | 195 | | |
169 | 196 | | |
| |||
0 commit comments