paulononato/backstage
1
0
Fork 0
Code Issues Pull Requests Actions 31 Packages Projects Releases Wiki Activity

chore: include the bonus release

Browse Source 
Signed-off-by: blam <ben@blam.sh>
This commit is contained in:
blam
2024-04-19 16:44:27 +02:00
parent 2c8ce00b6c
commit 5cdaf08e86
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
microsite/blog/2024-04-19-community-plugins.mdx
+2 -2
View File
@@ -22,7 +22,7 @@ With Red Hat wanting to join forces and help get this setup, this is the path th
Would also like to give a shoutout to all the Community Plugins Project area maintainers, who have been helping get us to this state! [@vinzscam](https://github.com/vinzscam) [@tudi2d](https://github.com/tudi2d) [@bethgriggs](https://github.com/BethGriggs) [@kadel](https://github.com/kadel) [@awanlin](https://github.com/awanlin) 👏
And now with the release of `1.26.2` there's a large amount of plugins from the main monorepo that have been migrated over to the new [Community Plugins Repository](https://github.com/backstage/community-plugins) :tada:
And now with the release of `1.26.3` there's a large amount of plugins from the main monorepo that have been migrated over to the new [Community Plugins Repository](https://github.com/backstage/community-plugins) :tada:
## The Migration
@@ -46,7 +46,7 @@ yarn backstage-cli versions:bump --skip-migrate
yarn backstage-cli versions:migrate
```
From this latest 1.26.2 release and onwards, the `backstage-cli versions:bump` command will automatically check for moved packages, so you shouldn't have to worry about running this every time.
From this latest `1.26.3` release and onwards, the `backstage-cli versions:bump` command will automatically check for moved packages, so you shouldn't have to worry about running this every time.
## Help! My plugin has been moved!