No, the tag v3.6.0.beta1 (commit d63a243)
إعجاب واحد (1)
Cool, thanks!
I think this should fix it:
Once merged I’ll try to manually trigger the workflow for d63a243
إعجابَين (2)
So I was targeting the beta tag, unknowingly.
Thanks!!!
إعجاب واحد (1)
The published assets are indexed by commit hash. So yeah, right now the v3.6.0.beta1 tag is attached to the same commit as beta, and also latest-release. This fix should handle all of those 
إعجاب واحد (1)
Assets for d63a2431 are now live: Release v3.6.0.beta1-d63a2431 · discourse/discourse-assets · GitHub
إعجابَين (2)