Skip to content
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.

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

Bump rimraf version to v6 for v13 #8368

Open
1 task
gonfunko opened this issue Jul 15, 2024 · 1 comment
Open
1 task

Bump rimraf version to v6 for v13 #8368

gonfunko opened this issue Jul 15, 2024 · 1 comment
Labels
issue: bug Describes why the code or behaviour is wrong

Comments

@gonfunko
Copy link
Contributor

gonfunko commented Jul 15, 2024

Check for duplicates

  • I have searched for similar issues before opening a new one.

Description

Dependabot opened #8361 to move rimraf to v6, but the release notes indicate it drops support for Node 18 which we still support. We should update the package as part of Blockly v13.

Reproduction steps

No response

Stack trace

No response

Screenshots

No response

Browsers

No response

@gonfunko gonfunko added issue: bug Describes why the code or behaviour is wrong issue: triage Issues awaiting triage by a Blockly team member labels Jul 15, 2024
@gonfunko gonfunko added this to the v12 milestone Jul 15, 2024
@rachel-fenichel rachel-fenichel changed the title Bump rimraf version for v12 Bump rimraf version to v6 for v12 Jul 22, 2024
@cpcallen
Copy link
Contributor

N.B. node.js v18 will be in maintenance mode until ~May 2025, so I don't think we even want to do this in Blockly v12 unless that release is much further in the future than I anticipate.

@cpcallen cpcallen removed the issue: triage Issues awaiting triage by a Blockly team member label Jul 22, 2024
@rachel-fenichel rachel-fenichel changed the title Bump rimraf version to v6 for v12 Bump rimraf version to v6 for v13 Nov 5, 2024
@rachel-fenichel rachel-fenichel removed this from the v12 milestone Nov 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
issue: bug Describes why the code or behaviour is wrong
Projects
None yet
Development

No branches or pull requests

3 participants