No, the tag v3.6.0.beta1 (commit d63a243)
Cool, thanks!
I think this should fix it:
Once merged I’ll try to manually trigger the workflow for d63a243
So I was targeting the beta tag, unknowingly.
Thanks!!!
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 ![]()
Assets for d63a2431 are now live: Release v3.6.0.beta1-d63a2431 · discourse/discourse-assets · GitHub
I have the same problem again ![]()
Maybe I’m targeting the wrong commit?
Fetching and extracting https://get.discourse.org/discourse-assets/2025.11.0-75d61b40/production.tar.gz...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
100 9 100 9 0 0 25 0 --:--:-- --:--:-- --:--:-- 25
curl: (22) The requested URL returned error: 404
[assemble_ember_build] Failed to download prebuilt assets: Command failed with exit 22: curl
Which tag are you targetting?
v2025.11.0 or commit 75d61b40ee928a4620b16f5438ca886678fab00d
discourse@testbeta:/var/www/discourse$ git checkout v2025.11.0
HEAD is now at 75d61b40ee DEV: Bump version on `release/2025.11` to `v2025.11.0` (#36251)
discourse@testbeta:/var/www/discourse$ RAILS_ENV=production bundle exec rake assets:precompile
[assemble_ember_build] Existing build is not reusable.
- Existing: {"ember_env"=>"production", "core_tree_hash"=>"deca4dcdbe7b705aac0d05212bbbe4b1b949d003"}
- Current: {"ember_env"=>"production", "core_tree_hash"=>"063db9253029db5919e776f30e6b3dada4d38958"}
Fetching and extracting https://get.discourse.org/discourse-assets/2025.11.0-75d61b40/production.tar.gz...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
100 9 100 9 0 0 23 0 --:--:-- --:--:-- --:--:-- 23
curl: (22) The requested URL returned error: 404
[assemble_ember_build] Failed to download prebuilt assets: Command failed with exit 22: curl
[assemble_ember_build] Running full core build...
Ok, I’ll see if I can get assets published for that tag. But I’d recommend you use the release/2025.11 branch (or the release tag), so that you get any small patches even if we haven’t bumped the patch version yet. (e.g. this one)
That will have the most similarity to the existing stable branch deploy strategy.