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

Dowgrade glob v11 to v10 #330

Merged
merged 1 commit into from
Feb 17, 2025
Merged

Dowgrade glob v11 to v10 #330

merged 1 commit into from
Feb 17, 2025

Conversation

lencioni
Copy link
Contributor

The only change listed in the v11 changelog is dropping support for node before v20. We want to support node v18 right now, so I am downgrading this back to v10.

https://github.com/isaacs/node-glob/blob/main/changelog.md#110

The only change listed in the v11 changelog is dropping support for node
before v20. We want to support node v18 right now, so I am downgrading
this back to v10.

https://github.com/isaacs/node-glob/blob/main/changelog.md#110
@lencioni lencioni requested a review from trotzig February 17, 2025 21:03
@@ -3272,7 +3272,7 @@ glob@^10.0.0:
package-json-from-dist "^1.0.0"
path-scurry "^1.11.1"

glob@^11.0.0, glob@^11.0.1:
glob@^11.0.0:
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

v11 comes in as a transitive dep of rimraf, which is just a dev dep here, so we don't need to worry about this.

lencioni added a commit that referenced this pull request Feb 17, 2025
We recently updated glob to v11, which does not support Node 18, and so
have to downgrade it and publish another release:

#330

I want to make sure we catch this in CI next time and I think this might
do the trick.
@lencioni lencioni merged commit db7cd6b into main Feb 17, 2025
4 checks passed
@lencioni lencioni deleted the glob-downgrade branch February 17, 2025 21:09
lencioni added a commit that referenced this pull request Feb 17, 2025
We recently updated glob to v11, which does not support Node 18, and so
have to downgrade it and publish another release:

#330

I want to make sure we catch this in CI next time and I think this might
do the trick.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant