Update dependency google-closure-compiler to v20250915 #133

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Open

renovate-bot wants to merge 1 commit into Trash-Compiler:main from renovate-bot:renovate/google-closure-compiler-20250915.x

Contributor

renovate-bot commented Sep 18, 2025

This PR contains the following updates:

Package	Change	Age	Confidence
google-closure-compiler (source)	`^20250709.0.0` -> `^20250915.0.0`

Release Notes

google/closure-compiler-npm (google-closure-compiler)

`v20250915.0.0`: 20250915.0.0

Closure-compiler 2025091 release

Full Changelog: google/closure-compiler-npm@v20250914.0.0...v20250915.0.0

`v20250914.0.0`: 20250914.0.0

Closure-compiler 2025091 release

Full Changelog: google/closure-compiler-npm@v20250903.0.0...v20250914.0.0

`v20250903.0.0`: 20250903.0.0

Closure-compiler 2025090 release

Full Changelog: google/closure-compiler-npm@v20250901.0.0...v20250903.0.0

`v20250901.0.0`: 20250901.0.0

Closure-compiler 2025090 release

Full Changelog: google/closure-compiler-npm@v20250824.0.0...v20250901.0.0

`v20250820.0.0`: 20250820.0.0

Closure-compiler 2025082 release

Full Changelog: google/closure-compiler-npm@v20250819.0.0...v20250820.0.0

`v20250819.0.0`: 20250819.0.0

Closure-compiler 2025081 release

Full Changelog: google/closure-compiler-npm@v20250818.0.0...v20250819.0.0

`v20250818.0.0`: 20250818.0.0

Closure-compiler 2025081 release

Full Changelog: google/closure-compiler-npm@v20250817.0.0...v20250818.0.0

`v20250817.0.0`: 20250817.0.0

Closure-compiler 2025081 release

Full Changelog: google/closure-compiler-npm@v20250813.0.0...v20250817.0.0

`v20250813.0.0`: 20250813.0.0

Closure-compiler 2025081 release

Full Changelog: google/closure-compiler-npm@v20250810.0.0...v20250813.0.0

`v20250810.0.0`: 20250810.0.0

Closure-compiler 2025081 release

Full Changelog: google/closure-compiler-npm@v20250805.0.0...v20250810.0.0

`v20250805.0.0`: 20250805.0.0

Closure-compiler 2025080 release

Full Changelog: google/closure-compiler-npm@v20250803.0.0...v20250805.0.0

`v20250803.0.0`: 20250803.0.0

Closure-compiler 2025080 release

Full Changelog: google/closure-compiler-npm@v20250730.0.0...v20250803.0.0

`v20250730.0.0`: 20250730.0.0

Closure-compiler 2025073 release

Full Changelog: google/closure-compiler-npm@v20250729.0.0...v20250730.0.0

`v20250729.0.0`: 20250729.0.0

Closure-compiler 2025072 release

Full Changelog: google/closure-compiler-npm@v20250727.0.0...v20250729.0.0

`v20250727.0.0`: 20250727.0.0

Closure-compiler 2025072 release

Full Changelog: google/closure-compiler-npm@v20250723.0.0...v20250727.0.0

`v20250723.0.0`: 20250723.0.0

Closure-compiler 2025072 release

Full Changelog: google/closure-compiler-npm@v20250721.0.0...v20250723.0.0

`v20250721.0.0`: 20250721.0.0

Closure-compiler 2025072 release

Full Changelog: google/closure-compiler-npm@v20250720.0.0...v20250721.0.0

`v20250720.0.0`: 20250720.0.0

Closure-compiler 2025072 release

Full Changelog: google/closure-compiler-npm@v20250716.0.0...v20250720.0.0

`v20250716.0.0`: 20250716.0.0

Closure-compiler 2025071 release

Full Changelog: google/closure-compiler-npm@v20250715.0.0...v20250716.0.0

`v20250715.0.0`: 20250715.0.0

Closure-compiler 2025071 release

Full Changelog: google/closure-compiler-npm@v20250714.0.0...v20250715.0.0

`v20250714.0.0`: 20250714.0.0

Closure-compiler 2025071 release

Full Changelog: google/closure-compiler-npm@v20250713.0.0...v20250714.0.0

`v20250713.0.0`: 20250713.0.0

Closure-compiler 2025071 release

Full Changelog: google/closure-compiler-npm@v20250709.0.0...v20250713.0.0

`v20250709.0.0`: 20250709.0.0

Closure-compiler 2025070 release

Full Changelog: google/closure-compiler-npm@v20250708.0.0...v20250709.0.0

`v20250708.0.0`: 20250708.0.0

Closure-compiler 2025070 release

Full Changelog: google/closure-compiler-npm@v20250706.0.0...v20250708.0.0

`v20250701.0.0`: 20250701.0.0

Closure-compiler 2025070 release

Full Changelog: google/closure-compiler-npm@v20250630.0.0...v20250701.0.0

`v20250630.0.0`: 20250630.0.0

Closure-compiler 2025063 release

Full Changelog: google/closure-compiler-npm@v20250629.0.0...v20250630.0.0

`v20250629.0.0`: 20250629.0.0

Closure-compiler 2025062 release

Full Changelog: google/closure-compiler-npm@v20250625.0.0...v20250629.0.0

`v20250625.0.0`: 20250625.0.0

Closure-compiler 2025062 release

Full Changelog: google/closure-compiler-npm@v20250624.0.0...v20250625.0.0

`v20250624.0.0`: 20250624.0.0

Closure-compiler 2025062 release

Full Changelog: google/closure-compiler-npm@v20250623.0.0...v20250624.0.0

`v20250623.0.0`: 20250623.0.0

Closure-compiler 2025062 release

Full Changelog: google/closure-compiler-npm@v20250622.0.0...v20250623.0.0

`v20250619.0.0`: 20250619.0.0

Closure-compiler 2025061 release

What's Changed

Bump brace-expansion from 1.1.11 to 1.1.12 in the npm_and_yarn group across 1 directory by @dependabot in #330

Full Changelog: google/closure-compiler-npm@v20250615.0.0...v20250619.0.0

`v20250615.0.0`: 20250615.0.0

Closure-compiler 2025061 release

What's Changed

Suppress Sun unsafe memory warnings on JDK 24 by @ChadKillingsworth in #328

Full Changelog: google/closure-compiler-npm@v20250609.0.0...v20250615.0.0

`v20250609.0.0`: 20250609.0.0

Closure-compiler 2025060 release

Full Changelog: google/closure-compiler-npm@v20250608.0.0...v20250609.0.0

`v20250608.0.0`: 20250608.0.0

Closure-compiler 2025060 release

Full Changelog: google/closure-compiler-npm@v20250603.0.0...v20250608.0.0

`v20250603.0.0`: 20250603.0.0

Closure-compiler 2025060 release

What's Changed

Upgrade to yarn 4 by @ChadKillingsworth in #329

Full Changelog: google/closure-compiler-npm@v20250601.0.0...v20250603.0.0

`v20250601.0.0`: 20250601.0.0

Closure-compiler 2025060 release

What's Changed

On linux, statically link all libraries including GLIBC by @ChadKillingsworth in #326

Full Changelog: google/closure-compiler-npm@v20250528.0.0...v20250601.0.0

`v20250528.0.0`: 20250528.0.0

Closure-compiler 2025052 release

What's Changed

Avoid using require to import an ES module by @ChadKillingsworth in #325

Full Changelog: google/closure-compiler-npm@v20250526.0.0...v20250528.0.0

`v20250526.0.0`: 20250526.0.0

Closure-compiler 2025052 release

Full Changelog: google/closure-compiler-npm@v20250520.0.0...v20250526.0.0

`v20250520.0.0`: 20250520.0.0

Closure-compiler 2025052 release

Full Changelog: google/closure-compiler-npm@v20250519.0.0...v20250520.0.0

`v20250519.0.0`: 20250519.0.0

Closure-compiler 2025051 release

What's Changed

Adjust the IncludeResources flags for the native-image build by @ChadKillingsworth in #324

Full Changelog: google/closure-compiler-npm@v20250518.0.0...v20250519.0.0

`v20250518.0.0`: 20250518.0.0

Closure-compiler 2025051 release

What's Changed

Add a helper script to invoke the jasmine test runner by @ChadKillingsworth in #320
Update gulp plugin to use modern logging and errors by @ChadKillingsworth in #321
Remove support for nightly/snapshot builds by @ChadKillingsworth in #319
Add reflection protection for GRAAL to prevent runtime exceptions by @ChadKillingsworth in #317
Pin all GitHub actions to specific commit hashes by @ChadKillingsworth in #322
Use more specific patterns for matching included resources by @ChadKillingsworth in #318

Full Changelog: google/closure-compiler-npm@v20250514.0.0...v20250518.0.0

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.


          Update dependency google-closure-compiler to v20250915

2820d2e

forking-renovate bot commented Sep 18, 2025

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: krew.io-source/package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: closure-webpack-plugin@2.6.1
npm ERR! Found: webpack@5.94.0
npm ERR! node_modules/webpack
npm ERR!   webpack@"^5.94.0" from the root project
npm ERR!   peer webpack@"^5.0.0" from grunt-webpack@7.0.0
npm ERR!   node_modules/grunt-webpack
npm ERR!     grunt-webpack@"^7.0.0" from the root project
npm ERR!   1 more (terser-webpack-plugin)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer webpack@"4.x" from closure-webpack-plugin@2.6.1
npm ERR! node_modules/closure-webpack-plugin
npm ERR!   closure-webpack-plugin@"^2.5.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: webpack@4.47.0
npm ERR! node_modules/webpack
npm ERR!   peer webpack@"4.x" from closure-webpack-plugin@2.6.1
npm ERR!   node_modules/closure-webpack-plugin
npm ERR!     closure-webpack-plugin@"^2.5.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2025-09-18T04_00_10_116Z-debug-0.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet