chore(repo): add monthly curation workflow for community plugins#35321
Draft
FrozenPandaz wants to merge 1 commit intomasterfrom
Draft
chore(repo): add monthly curation workflow for community plugins#35321FrozenPandaz wants to merge 1 commit intomasterfrom
FrozenPandaz wants to merge 1 commit intomasterfrom
Conversation
✅ Deploy Preview for nx-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for nx-dev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
|
View your CI Pipeline Execution ↗ for commit 653d8a5
☁️ Nx Cloud last updated this comment at |
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.
Current Behavior
The approved community plugins list at
astro-docs/src/content/approved-community-plugins.jsonhas no automated curation. Dead, abandoned, or Nx-incompatible plugins remain listed indefinitely, since there is no recurring process to check their maintenance status. The submission docs also only vaguely reserve "the right to remove unmaintained plugins" without spelling out what that means.Expected Behavior
Adds a monthly scheduled GitHub Actions workflow (
curate-community-plugins.yml) that runs an assessment script over every listed plugin and opens a PR to prune entries that no longer meet the bar. Also updates the publish-plugin docs to make the removal criteria explicit for submitters.Assessment signals (per plugin):
last-monthdownloads and last publish date (fromregistry.npmjs.org)@nx/devkit, falls back to@nx/workspace,nx)archivedflag, 404 detection (viagh api)Verdicts:
healthy— none of the belowstale— more than 12 months since last publish, or fewer than 100 downloads/monthincompatible— declared Nx range does not include any of the last 3 majors (current − 2)abandoned— GitHub repo is 404, archived, or last published more than 24 months agoPruning (triggered by the
--pruneflag, which the workflow passes):abandonedandincompatibleplugins fromapproved-community-plugins.jsonstaleplugins are kept but flagged in the PR descriptionSafety:
schedule(1st of every month at 09:00 UTC) andworkflow_dispatch— never onpull_request— so externals cannot invoke itLocal usage:
Docs update (
astro-docs/src/content/docs/extending-nx/publish-plugin.mdoc):Replaces the vague "we reserve the right to remove unmaintained plugins" aside with the concrete removal criteria listed above, along with rationale for the 24-month cutoff (Nx ships a major version every six months, so two years is four Nx majors behind).
Related Issue(s)
None.