chore(deps): update rspack monorepo to v1.1.8 (main) #1240
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.1.6
->1.1.8
1.1.6
->1.1.8
Release Notes
web-infra-dev/rspack (@rspack/cli)
v1.1.8
Security Vulnerability Report
Overview
This is a re-release version of 1.1.6
On 12/19/2024, 02:01 (UTC), we discovered that our npm packages
@rspack/core
and@rspack/cli
were maliciously attacked. The attacker releasedv1.1.7
using a compromised npm token, which contained malicious code. We took immediate action upon discovering the issue.Impact
@rspack/core
and@rspack/cli
v1.1.7
package.json
runs malicious code indist/util/support.js
. We are currently analyzing the full impact of malicious code.Actions Taken
Upon discovery, we immediately deprecated the affected
v1.1.7
, redirected the npm latest tag tov1.1.6
, and reset all related tokens.Subsequently, we released a secure new version
v1.1.8
.Recommended Actions
If you installed
v1.1.7
during the affected period, please:@rspack/core
and@rspack/cli
to>= 1.1.8
Apology and Commitment
We deeply apologize for the risks caused by this incident. To prevent similar incidents from happening again, we will implement stricter token management protocols and enhance our security review processes.
If you have any questions or discover any suspicious activity, please create an issue or send an email to: [email protected]
We will continue to follow and respond to community feedback.
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 these updates again.
This PR was generated by Mend Renovate. View the repository job log.