Immutability of Hash values produced by Angular outputHashing (cache-buster) option

I have been using Angular 12. I want to ask about the behavior of the hash string (for cache buster) attached to the file name when "all" is specified for "outputHashing."

In Angular 12, the same source code produced the same hash string no matter how many builds were made. This worked well for my deployment pipeline.

However, when I upgraded to Angular 18, the same source code generated different hash strings each time I built it. My deployment pipeline doesn't handle this correctly.

How can I get Angular 18 to behave like Angular 12 where "the same source code generates the same hash value" ?

I built the same source code multiple times with Angular 12 and Angular 18, but in Angular 12 the hash value was immutable. However, in Angular 18, the hash value fluctuated with each build.

Continue reading...