Beth Griggs
Beth Griggs
An alternative workaround might be to allow plugin maintainers to add multiple directories. That way no extra branches or new workflows should be required - they just need to create...
The previous suggestion in https://github.com/backstage/community-plugins/issues/860#issuecomment-2293528905 will not work as `yarn workspaces` detects the duplicate name and errors, so the branch option looks to be reasonable. I figure these could even...
> and if we needed another bugfix we'd have a new argocd/1.24.8 branch... rather than reusing a argocd/1.24 branch for all the updates? I figure the `workspacename/x.y.z` branch doesn't need...
> In the main backstage/backstage repo out only use of multi-track releases has been critical security fixes. Is it the same here and is that the only thing we should...
Sure, that could be our recommendation. Generally, in this project area, we’ve maintained that plugin owners have autonomy over their plugins and versioning decisions. In my view, if we can...
After a lot of discussion and iterations, we now have documented a process for doing interim releases in the [Plugin Maintainer Guide](https://github.com/backstage/community-plugins/blob/main/docs/plugin-maintainers-guide.md#maintaining-and-patching-an-older-release-line) using the recently added [`release_workspace_version.yml`](https://github.com/backstage/community-plugins/blob/main/.github/workflows/release_workspace_version.yml). The workflow ensures...
> I'll leave this open for now as a reminder that we need to document or automate the creation of the protected workspace branches with consistent rules/restrictions. As the number...
Hey @mareklibra, I managed to get a green CI on this with some follow-up commits in https://github.com/backstage/community-plugins/pull/712#commits-pushed-2e3ce93 that could be cherry-picked. I tried to give the commits meaningful titles, but...
There was a relevant discussion in todays Community Plugins SIG. A summary: * Documentation and general good practises for plugin development should live in Backstage core/framework documentation. * We should...
CI is failing here on the `tsc` step with errors such as: ``` node_modules/graphql-language-service/dist/parser/types.d.ts:116:37 - error TS2694: Namespace 'Kind' has no exported member 'LIST_NULLABILITY_OPERATOR'. 116 LIST_NULLABILITY_OPERATOR: Kind.LIST_NULLABILITY_OPERATOR; ~~~~~~~~~~~~~~~~~~~~~~~~~ ``` Help...