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

feat(replacements): eslint-plugin-vitest to scoped #31492

Merged
merged 2 commits into from
Sep 20, 2024

Conversation

ST-DDT
Copy link
Contributor

@ST-DDT ST-DDT commented Sep 19, 2024

Changes

Created a replacement rule for the eslint-plugin-vitest with its continuation/scoped package.

Context

The package is now published as scoped package @vitest/eslint-plugin.

Proof:

Documentation (please check one with an [x])

  • I have updated the documentation, or
  • No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

  • Code inspection only, or
  • Newly added/modified unit tests, or
  • No unit tests but ran on a real repository, or
  • Both unit tests + ran on a real repository

@ST-DDT
Copy link
Contributor Author

ST-DDT commented Sep 19, 2024

@veritem / maintainers of eslint-plugin-vitest: FYI

lib/data/replacements.json Outdated Show resolved Hide resolved
@veritem
Copy link

veritem commented Sep 19, 2024

@ST-DDT We moved package under vitest npm org and released 1.0.0.

@viceice viceice added this pull request to the merge queue Sep 20, 2024
Merged via the queue into renovatebot:main with commit c5252a9 Sep 20, 2024
38 checks passed
@renovate-release
Copy link
Collaborator

🎉 This PR is included in version 38.91.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@ST-DDT ST-DDT deleted the eslint-plugin-vitest-to-scoped branch September 20, 2024 06:12
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 21, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants