Cache busting - Output hashing does not affect assets with new build system

[mmarczell-graphisoft]

Command

build

Is this a regression?

• Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was

No response

Description

With the new build system, images and other assets are not getting hashed filenames, even though output hashing is set to media or all. This is especially confusing as what is media if not my image assets?

Minimal Reproduction

Build any Angular app that has "assets" in angular.json, with the new build system and output hashing set to media or all.

Exception or Error

Your Environment

Angular CLI: 20.0.4
Node: 22.16.0
Package Manager: npm 11.4.2
OS: darwin x64

Angular: 20.0.5
... animations, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router

Package                      Version
------------------------------------------------------
@angular-devkit/architect    0.2000.4
@angular-devkit/core         20.0.4
@angular-devkit/schematics   20.0.4
@angular/build               20.0.4
@angular/cdk                 20.0.4
@angular/cli                 20.0.4
@schematics/angular          20.0.4
rxjs                         6.6.7
typescript                   5.8.3
zone.js                      0.15.1

Anything else relevant?

If the behaviour is by design, it should be documented at the output hashing flag.

[alan-agius4]

This is the expected behavior, which has been consistent since these options were first introduced with the webpack-based builders.

Assets are copied as-is, this is also mentioned in the docs here.

Media files are are resources such as images and fonts referenced in CSS files.

[mmarczell-graphisoft]

Thank you for clarifying the docs, that is indeed helpful.