Skip to content

ci: unpin jiti to version ^2.5.1 #19970

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

Merged
merged 1 commit into from
Jul 25, 2025
Merged

ci: unpin jiti to version ^2.5.1 #19970

merged 1 commit into from
Jul 25, 2025

Conversation

lumirlumir
Copy link
Member

@lumirlumir lumirlumir commented Jul 25, 2025

Prerequisites checklist

What is the purpose of this pull request? (put an "X" next to an item)

[ ] Documentation update
[ ] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofix to a rule
[ ] Add a CLI option
[ ] Add something to the core
[x] Other, please explain:

What changes did you make? (Give an overview)

After #19964 was merged due to CI errors, a new version of jiti (2.5.1) was released to resolve the bug.

So, I'm unpinning the version to ^2.5.1.

Ref: https://github.com/unjs/jiti/releases/tag/v2.5.1, #19964

Is there anything you'd like reviewers to focus on?

@lumirlumir lumirlumir requested a review from a team as a code owner July 25, 2025 08:16
@github-project-automation github-project-automation bot moved this to Needs Triage in Triage Jul 25, 2025
@eslint-github-bot eslint-github-bot bot added the build This change relates to ESLint's build process label Jul 25, 2025
@mdjermanovic mdjermanovic merged commit 74f01a3 into main Jul 25, 2025
26 checks passed
@mdjermanovic mdjermanovic deleted the ci-unpin-jiti branch July 25, 2025 08:25
@github-project-automation github-project-automation bot moved this from Needs Triage to Complete in Triage Jul 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build This change relates to ESLint's build process
Projects
Status: Complete
Development

Successfully merging this pull request may close these issues.

2 participants