diff --git a/microsite/blog/2024-04-19-community-plugins.mdx b/microsite/blog/2024-04-19-community-plugins.mdx index 4d3955c4e7..06d73ae5db 100644 --- a/microsite/blog/2024-04-19-community-plugins.mdx +++ b/microsite/blog/2024-04-19-community-plugins.mdx @@ -6,15 +6,15 @@ authorURL: https://github.com/benjdlambert authorImageURL: https://avatars.githubusercontent.com/u/3645856?v=4 --- -**tl;dr**: We've setup the [Community Plugins Repository](https://github.com/backstage/community-plugins), and have migrated them to their new home! +**tl;dr**: We've setup the [Community Plugins Repository](https://github.com/backstage/community-plugins), and have migrated most of the packages in the `plugins` directory of the main Backstage repository to their new home! -Migrating is as simple as `yarn backstage-cli versions:bump` then `yarn backstage-cli versions:migrate`. If you're already on `1.26.1` then be sure to run `yarn backstage-cli versions:bump --skip-migrate` then `yarn backstage-cli versions:migrate` to take advantage of the code reference replacement helpers. +For those who depended on these plugins migrating is as simple as `yarn backstage-cli versions:bump` then `yarn backstage-cli versions:migrate`. If you're already on `1.26.1` then be sure to run `yarn backstage-cli versions:bump --skip-migrate` then `yarn backstage-cli versions:migrate` to take advantage of the code reference replacement helpers. {/* truncate */} ## The Community Plugins Repo -Some of you that have been around a while, or seen some of our [Maintainer Track talks](https://www.youtube.com/watch?v=ONMBYnhxnNU) at KubeCon, might have seen [this RFC](https://github.com/backstage/backstage/issues/20266) which outlines some issues with the scale of the `backstage/backstage` monorepo, and us as maintainers being the defacto owners of all plugins without a [Project Area](https://github.com/backstage/backstage/blob/master/GOVERNANCE.md#project-area-maintainer) or [Plugin Maintainer](https://github.com/backstage/backstage/blob/master/GOVERNANCE.md#project-area-maintainer). +Some of you that have been around a while, or seen some of our [Maintainer Track talks](https://www.youtube.com/watch?v=ONMBYnhxnNU) at KubeCon, might have seen [this RFC](https://github.com/backstage/backstage/issues/20266) which outlines some issues with the scale of the `backstage/backstage` monorepo, and us as maintainers being the defacto owners of all plugins without a [Project Area](https://github.com/backstage/backstage/blob/master/GOVERNANCE.md#project-area) or [Plugin Maintainer](https://github.com/backstage/backstage/blob/master/GOVERNANCE.md#project-area-maintainer). There was some great discussion in this issue, and some great ideas. One of them being a dedicated home for Community Plugins, with all the burden of release tooling and workspace tooling already setup, which is a pretty big barrier for people wanting to create plugins for Backstage in their own organization or personal account. These plugins would then have the ability to release independently of the main monorepo, and have their own release cadence, which is something that we've been looking at exploring for a while. @@ -32,7 +32,7 @@ This makes migration a little tricky for end users, as there's going to be code We've added some tooling into the `@backstage/cli` which is going to smooth the transition here. The last versions which are published under the `@backstage/` scope from the monorepo, will have a special field in the `package.json` with a hint to the CLI as to what this package is now called. -The CLI will then be able to replace these references in side the `./src` folder of your codebase, and update your `package.json` dependencies to the new `@backstage-community` scope. +The CLI will then be able to replace these references inside the `./src` folder of your codebase, and update your `package.json` dependencies to the new `@backstage-community` scope. You can migrate today by running the following: @@ -155,12 +155,12 @@ We've taken a pretty big chunk of the plugins from the main monorepo and moved t - `@backstage/plugin-vault-node` - `@backstage/plugin-vault` - `@backstage/plugin-xcmetrics` -This is how you dropdown. ## What's next? -There's going to be a little bit of time now in this migration period where there's going to be issues and pull requests not in the right place, and we're going to do our best to transfer issues to the community plugins repository instead. +There's going to be a little bit of time now in this migration period where there's going to be issues and pull requests not in the right place, and we're going to do our best to transfer issues to the community plugins repository instead. +We will shortly be removing the code for these plugins from the main monorepo as it now has a new home in the Community Plugins Repository. We're also going to be looking at bringing in some more of the great tooling from the `backstage/backstage` monorepo into the community plugins repository to help out with more automation for dependency bumps etc.