Repository maintenance status & potential transfer to backstage/community-plugins

[dfl-aeb]

Hi @natalyapeixoto 👋,

I noticed that the last commit / release in this repository dates back to 15 Dec 2022 and that there has been no activity since then.

Could you please let us know whether the plugin is still actively maintained or if it has reached end-of-life?

If regular maintenance is no longer feasible, would you be open to transferring the code (or granting commit rights) to the backstage/community-plugins repository?
That repo was created precisely to keep useful plugins alive under community stewardship, and several plugins have already been successfully migrated there.

[yousifalraheem]

@dfl-aeb yes the plugin is still active and we are planning a new update soon for the dependencies plus a few bug fixes and improvements.

[dfl-aeb]

Hi @yousifalraheem 👋,

thanks a lot for confirming that the plugin is still being maintained and that an update is on the way — much appreciated!

Today Backstage v1.39.0 was released and the release officially deprecates React 17; the Backstage CLI now prints warnings whenever a project is still on React 17 and urges users to follow the migration guide to React 18

See --> https://github.com/backstage/backstage/releases/tag/v1.39.0

Our organisation normally upgrades Backstage very quickly, but right now we have to hold off because backstage-plugin-api-linter’s latest version (v1.0.12) still declares React 17 in its peer-/dev-dependencies

Could you share a rough ETA for a React-18 compatible release (or perhaps a migration branch we could help test)?
Even a ball-park indication (e.g. “in the next few weeks” vs. “several months”) would help us decide whether we can stay a bit behind on Backstage or need to look for a temporary workaround.

Happy to contribute PRs or testing if that speeds things up.
Thanks again for maintaining this plugin — we’d really like to keep using it! 🙌

[aputhin]

Could you share a rough ETA for a React-18 compatible release (or perhaps a migration branch we could help test)? Even a ball-park indication (e.g. “in the next few weeks” vs. “several months”) would help us decide whether we can stay a bit behind on Backstage or need to look for a temporary workaround.

Right now we're also working on other dependencies to be able to upgrade Backstage as well. We have a few internal plugins that require fixing, plus other features under development. My best ball park estimation is around August for updating this plugin. But no promises, might be later.

If you'd be willing to contribute that part of the upgrade (bumping React) it would help a lot already. There's some other smaller improvements we might want to make, but I guess that's the major blocker.

[brennoo]

hello,

we want to use the plugin but hit this issue, does the ETA of around August still accurate?

Thanks!

[dfl-aeb]

@aputhin @yousifalraheem any news from your side?

[yousifalraheem]

@dfl-aeb I'm currently working on a PR, will update you as soon as it's released

[dfl-aeb]

any news @yousifalraheem? Seems like you started working on it and it's almost ready? whats missing?

[yousifalraheem]

any news @yousifalraheem? Seems like you started working on it and it's almost ready? whats missing?

I'm no longer working with Zalando, but before I left, the upgrade was completed and merged but wasn't released due to issues in the release pipeline. Maybe @natalyapeixoto or @maslochista can provide more details about the progress.