When updating scheduled_publish but not drupal/core, the JavaScript cache-busting parameter remains the same (e.g. ?v=10.4.8). When updating drupal/core but not scheduled_publish, the JavaScript cache-busting parameter changes.
LibraryDiscoveryParser applies the Drupal version to every library that uses version: VERSION. It does not use the modules version.
See the note on Adding assets (CSS, JS) to a Drupal module via *.libraries.yml → :
Starting from Drupal 10.1.2, the version information within a library definition plays a critical role in generating a unique hash for aggregated files. Consequently, it is imperative that the "version" in a library definition is updated whenever a referenced CSS/JS file undergoes changes.
Alternatively, if the version is omitted, the prior behavior will apply, where the content of referenced CSS/JS files is utilized in the hash.
Incorrect usage of version information could lead to browser and edge cache invalidation issues.
See this update → on the related changelog → .
Remove version: VERSION from scheduled_publish.libraries.yml
Active
4.0
Code
Also tested these changes using Drupal Core 11.2.3 and Scheduled Publish 4.0.0.
No problems found during testing.