Project

General

Profile

Actions

Bug #37775

closed

not all webpack assets are properly invalidated on change

Added by Evgeni Golov 9 days ago. Updated 5 days ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
JavaScript stack
Target version:
-
Fixed in Releases:
Found in Releases:

Description

Since the Webpack 5 migration, some webpack assets (vendor.js, bundle.js, reactExports.js, {plugin_id}.js) do not contain a hash in their name.
As we configure them to be cached by proxies and browsers, this means that changed assets are not properly re-loaded, resulting in broken UI until the user forces a cache drop.

Let's introduce hashes in the filenames again, solving this issue

Actions #1

Updated by The Foreman Bot 9 days ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/10125 added
Actions #2

Updated by The Foreman Bot 9 days ago

  • Fixed in Releases 3.13.0 added
Actions #3

Updated by The Foreman Bot 9 days ago

  • Pull request https://github.com/theforeman/foreman/pull/10305 added
Actions #4

Updated by Evgeni Golov 9 days ago

  • Status changed from Ready For Testing to Closed
Actions #5

Updated by The Foreman Bot 6 days ago

  • Fixed in Releases 3.12.0 added
Actions #6

Updated by The Foreman Bot 5 days ago

  • Fixed in Releases 3.11.2 added
Actions

Also available in: Atom PDF