-
-
Notifications
You must be signed in to change notification settings - Fork 12
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
ci: fix automated NPM release (#131)
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: 1. A `bump_oxlint.yml` workflow is dispatched with the new oxlint version (needs to be prefixed with `v`, i.e. `v0.7.0`) 2. The generate script bumps the version in the local `package.json` to match oxlint 3. Prettier now runs _after_ the generate script rather than during, as the API version was generating invalid json outputs 4. The update PR is generated, with the title `release: v0.7.0` 5. When this is merged, the `release.yml` workflow will start, and run if the latest commit contains `release: v` 6. This workflow will extract the version from the commit and create a corresponding tag 7. Everything else should work the same as before 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?
- Loading branch information
1 parent
bbd63e3
commit c0496a3
Showing
10 changed files
with
135 additions
and
106 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.