Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #130
This PR ensures that eslint-plugin-oxlint's version in package.json gets updated to match oxlint's version.
It does not automatically generate PRs for new oxlint versions, but it should automatically release (without needing to manually create a tag) once a manually generated
bump_oxlint.yml
PR is merged.I've changed the package versions to reflect oxlint v0.6.1, so this can correctly release v0.7.0. Here's how it should work:
bump_oxlint.yml
workflow is dispatched with the new oxlint version (needs to be prefixed withv
, i.e.v0.7.0
)package.json
to match oxlintrelease: v0.7.0
release.yml
workflow will start, and run if the latest commit containsrelease: v
If this gets merged, could a maintainer please delete the existing GitHub release v0.7.0 (which did not generate an NPM release), and then trigger a new
bump_oxlint.yml
workflow?