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

fix: pin glob to 10.3.4 #511

Merged
merged 1 commit into from
May 14, 2024
Merged

fix: pin glob to 10.3.4 #511

merged 1 commit into from
May 14, 2024

Conversation

Trott
Copy link
Member

@Trott Trott commented May 14, 2024

We can unpin it once the bot is running on Node.js 14.18 or newer.

Fixes: nodejs/build#3720

We can unpin it once the bot is running on Node.js 14.18 or newer.

Fixes: nodejs/build#3720
@Trott Trott requested a review from a team as a code owner May 14, 2024 19:41
@Trott Trott merged commit 9e5f92d into main May 14, 2024
14 checks passed
@Trott Trott deleted the revert branch May 14, 2024 19:57
@@ -24,7 +24,7 @@
"dotenv": "^16.4.5",
"events-async": "^1.2.1",
"express": "^4.19.2",
"glob": "^10.3.15"
"glob": "10.3.14"
Copy link
Member

Choose a reason for hiding this comment

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

Apparently I fail at reading... was this supposed to be 10.3.4 like the PR/commit title?

Copy link
Member Author

Choose a reason for hiding this comment

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

No, but we could try that. I chose 10.3.14 because 10.3.15 is the one where the "requires 14.18 or newer" commit first appears.

Copy link
Member Author

Choose a reason for hiding this comment

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

I typo'ed the commit message (and the PR title was taken from the commit message). The previous version we shipped with was 10.3.12, so maybe we can try that.

Copy link
Member Author

Choose a reason for hiding this comment

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

The require-a-newer-version-of-14.x commit was the first thing landed after the 10.3.13 release, further suggesting that 10.3.12 is the way to go.

Copy link
Member Author

Choose a reason for hiding this comment

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

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.

github-bot broken?
2 participants