Conversation
Member
Author
How to use the Graphite Merge QueueAdd either label to this PR to merge it via the merge queue:
You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
4afcc32 to
46c1280
Compare
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the Oxlint apps release configuration and GitHub Actions workflow so the newly added @oxlint/plugins npm package is version-bumped with Oxlint and published as part of the release process.
Changes:
- Add
npm/oxlint-plugins/package.jsonto theoxlintrelease’sversioned_fileslist so it gets bumped during app releases. - Bump
@oxlint/pluginspackage version to1.46.0. - Update the apps release workflow to copy built plugin artifacts into
npm/oxlint-pluginsand publish@oxlint/pluginsalongsideoxlint.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
oxc_release.toml |
Includes @oxlint/plugins in the Oxlint release version bump set. |
npm/oxlint-plugins/package.json |
Aligns @oxlint/plugins version with the current Oxlint release version. |
.github/workflows/release_apps.yml |
Publishes @oxlint/plugins during the Oxlint release job and copies build outputs into the package dir. |
46c1280 to
a328e8a
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.

#18824 added a
@oxlint/pluginsNPM package, and #18903 altered the release workflow. It seems neither worked correctly - the package hasn't been getting published during the release process.It's still on version 1.43.0 on NPM: https://www.npmjs.com/package/@oxlint/plugins
This PR alters the pre-release and release workflows to (hopefully) bump version of this package and release it alongside
oxlintpackage.There have been no changes to content of
@oxlint/pluginspackage since the last published version, and it has no dependencies, so it doesn't really matter that we've skipped these releases. But this PR should get it publishing correctly from next release onwards.