* feat: implement plugin archiving process
This commit introduces a process for archiving plugins and workspaces in
the project:
- `.github/archived-plugins.json` is added to track archived packages,
alongside `ARCHIVED_WORKSPACES.md` as a human-readable reference.
- `.github/workflows/deprecate-archived-plugins.yml` automates npm
deprecation using the new script `scripts/ci/deprecate-archived-plugins.sh`,
which runs `npm deprecate` for archived plugins.
- `scripts/archive.js` is added to automate the archiving of a plugin
or entire workspace, updating both tracking files.
- The plugin maintainer guide is updated with clear instructions on when
and how to archive plugins.
Refs: https://github.com/backstage/community-plugins/issues/4619
Signed-off-by: Beth Griggs <bethanyngriggs@gmail.com>
* fixup!
Signed-off-by: Beth Griggs <bethanyngriggs@gmail.com>
---------
Signed-off-by: Beth Griggs <bethanyngriggs@gmail.com>
Added `.auto-version-bump` files to all `@backstage/community-plugin-maintainers`
owned workspaces to opt them in to the automatic version bump process.
Also updated the Plugin Maintainer Guide with instructions for opting in
and clarifying that maintainers remain responsible for reviewing, updating,
and merging the resulting PRs.
Signed-off-by: Beth Griggs <bethanyngriggs@gmail.com>
Adds a collapsible section to the steps with the GitHub settings. This
is to ensure that when maintainers create `workspace/${workspace}`
branches they have the appropriate permissions set.
Signed-off-by: Beth Griggs <bethanyngriggs@gmail.com>
The release workflow was `needs`-ing the incorrect job. This commit also
improves the documentation for the release workflow.
Signed-off-by: Beth Griggs <bethanyngriggs@gmail.com>