Skip to content

fix(verify-release): the tag does not cross jobs — resolve it in each one - #60

Merged
openviewmobile merged 1 commit into
mainfrom
fix/tag-per-job
Nov 11, 2026
Merged

openviewmobile merged 1 commit into
mainfrom
fix/tag-per-job

Conversation

@openviewmobile

Copy link
Copy Markdown
Owner

The first nightly run failed with a message that blamed the wrong thing:

等了 12 分钟,站点索引仍是 0.2.8,期望 

The expected value was empty. resolve the tag writes TAG through $GITHUB_ENV, which only applies to the job that wrote it; the repositories job never had a tag, and on a schedule event there is no event-supplied tag either. So the wait loop compared 0.2.8 against "" and, after twelve minutes, reported the site as lagging — the site was fine all along (Version: 0.2.8, SHA256: 8081afcd…).

Both jobs now resolve the tag themselves, and the wait step first asserts that the expected version is non-empty, so this failure can never again masquerade as a repository problem.

Note the artifacts job passed all along (its own resolution worked), so the signature half of the nightly was already green — including rpm under 4.18 and 4.20 with the published key.

…jobs); assert the expected version is non-empty
@openviewmobile
openviewmobile merged commit 95cf0b4 into main Nov 11, 2026
2 checks passed
@openviewmobile
openviewmobile deleted the fix/tag-per-job branch November 11, 2026 12:17
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.

1 participant