Beth Griggs

Quick research here indicates that these updates assume/require us to adopt GraphQL 17+. It probably makes sense to do those updates in a dedicated PR.

The usage was removed from graphiql workspace in https://github.com/backstage/community-plugins/pull/4428, so this should be good to close now! 🎉

@yoramshai, it may be worth opening as new issue as a feature request for the plugin

> @RafaelGSS There's already a [git node release --security](https://github.com/nodejs/node-core-utils/blob/main/docs/git-node.md#git-node-release), which is intended for use by releasers when preparing security releases (it automatically adds "This is a security release." to the...

During the SIG today we discussed some various improvements and further prototyping needed here, I'll work on those

This is still needed, I just need to find time to update based on latest flow suggestions

Plan to pick this up again now I am back from vacation

@awanlin, it's more an alternative approach - I'd rather leave this open until we have some feedback on https://github.com/backstage/community-plugins/pull/2626

Now superseded by https://github.com/backstage/community-plugins/pull/2626, for a summary of where we are see https://github.com/backstage/community-plugins/issues/860#issuecomment-2689545426

Awaiting review from a CODEOWNER of `analytics-provider-segment` plugin