# מציגים נכסי JS מקומפלים מראש עבור מארחים עצמיים
**URL:** https://meta.discourse.org/t/introducing-pre-compiled-js-assets-for-self-hosters/376700
**Category:** Announcements
**Created:** [31 ביולי, 2025, 4:25pm UTC](https://meta.discourse.org/t/introducing-pre-compiled-js-assets-for-self-hosters/376700 "2025-07-31T16:25:05Z")
**Posts on this page:** 10
**Page:** 2
### Author:  [@RGJ](https://meta.discourse.org/u/RGJ)
#### Post date: [30 בספטמבר, 2025, 7:57am UTC](https://meta.discourse.org/t/introducing-pre-compiled-js-assets-for-self-hosters/376700/21 "2025-09-30T07:57:25Z")
לא, התגית `v3.6.0.beta1` (commit `d63a243`)
---
### Author:  [@david](https://meta.discourse.org/u/david)
#### Post date: [30 בספטמבר, 2025, 7:57am UTC](https://meta.discourse.org/t/introducing-pre-compiled-js-assets-for-self-hosters/376700/22 "2025-09-30T07:57:58Z")
Cool, thanks!
I think this should fix it:
[https://github.com/discourse/discourse/pull/35060](https://github.com/discourse/discourse/pull/35060)
Once merged I’ll try to manually trigger the workflow for `d63a243`
---
### Author:  [@RGJ](https://meta.discourse.org/u/RGJ)
#### Post date: [30 בספטמבר, 2025, 7:59am UTC](https://meta.discourse.org/t/introducing-pre-compiled-js-assets-for-self-hosters/376700/23 "2025-09-30T07:59:07Z")
> [@david](#):
>
> Are you targeting the `beta` tag for this install?
So I _was_ targeting the `beta` tag, unknowingly.
Thanks!!!
---
### Author:  [@david](https://meta.discourse.org/u/david)
#### Post date: [30 בספטמבר, 2025, 8:01am UTC](https://meta.discourse.org/t/introducing-pre-compiled-js-assets-for-self-hosters/376700/24 "2025-09-30T08:01:22Z")
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 👌
---
### Author:  [@david](https://meta.discourse.org/u/david)
#### Post date: [30 בספטמבר, 2025, 8:23am UTC](https://meta.discourse.org/t/introducing-pre-compiled-js-assets-for-self-hosters/376700/25 "2025-09-30T08:23:03Z")
Assets for `d63a2431` are now live: [Release v3.6.0.beta1-d63a2431 · discourse/discourse-assets · GitHub](https://github.com/discourse/discourse-assets/releases/tag/v3.6.0.beta1-d63a2431)
---
### Author:  [@RGJ](https://meta.discourse.org/u/RGJ)
#### Post date: [27 בנובמבר, 2025, 3:57pm UTC](https://meta.discourse.org/t/introducing-pre-compiled-js-assets-for-self-hosters/376700/26 "2025-11-27T15:57:45Z")
I have the same problem again 😭
Maybe I’m targeting the wrong commit?
```plaintext
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
```
---
### Author:  [@david](https://meta.discourse.org/u/david)
#### Post date: [27 בנובמבר, 2025, 4:39pm UTC](https://meta.discourse.org/t/introducing-pre-compiled-js-assets-for-self-hosters/376700/27 "2025-11-27T16:39:27Z")
Which tag are you targetting?
---
### Author:  [@RGJ](https://meta.discourse.org/u/RGJ)
#### Post date: [27 בנובמבר, 2025, 4:51pm UTC](https://meta.discourse.org/t/introducing-pre-compiled-js-assets-for-self-hosters/376700/28 "2025-11-27T16:51:38Z")
`v2025.11.0` or commit `75d61b40ee928a4620b16f5438ca886678fab00d`
```plaintext
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...
```
---
### Author:  [@david](https://meta.discourse.org/u/david)
#### Post date: [27 בנובמבר, 2025, 5:26pm UTC](https://meta.discourse.org/t/introducing-pre-compiled-js-assets-for-self-hosters/376700/29 "2025-11-27T17:26:20Z")
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](https://meta.discourse.org/t/sticky-header-gone/389835/12))
That will have the most similarity to the existing `stable` branch deploy strategy.
---
### Author:  [@david](https://meta.discourse.org/u/david)
#### Post date: [27 בנובמבר, 2025, 5:42pm UTC](https://meta.discourse.org/t/introducing-pre-compiled-js-assets-for-self-hosters/376700/30 "2025-11-27T17:42:07Z")
Assets for `v2025.11.0` are [published](https://github.com/discourse/discourse-assets/releases/tag/v2025.11.0-75d61b40), and scripts [updated](https://github.com/discourse/discourse/commit/5c5fa16789fab3a5a5e12bb2610cd20ad89f6723) to make sure it happens automatically in future.
[Previous page](https://meta.discourse.org/t/introducing-pre-compiled-js-assets-for-self-hosters/376700.md?page=1)