fix web-console artifact path in the release workflow - #72
Merged
jkandasa merged 1 commit intoSep 18, 2026
Merged
Conversation
upload-artifact v4 stores the contents of web-console/build at the zip root. Downloading into web-console left index.html one directory too high and failed the verify step.
3 tasks
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
1 participant
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.
Summary
#71’s release run failed at Verify web console. The console build succeeded and the artifact uploaded;
upload-artifactv4 stores the contents ofweb-console/buildat the zip root. Downloading intoweb-consoleproducedweb-console/index.htmlinstead ofweb-console/build/index.html.Download into
web-console/build(and keep flatten fallbacks). Same idea for archive checksums if those files land at the workspace root.Test plan
mainrelease run gets past Verify web console and Build binaries.