Questions about dependency management & community-plugin alignment for scaffolder-backend-module-hcl

[mathieugallant]

Hi! 👋
First, thank you for maintaining this plugin — it’s been very helpful for our Backstage setup.

I’m opening this issue to clarify two points related to how the repository is structured, as our organization is evaluating using (and hopefully contributing to) this module:

Repository location (outside the Backstage community-plugins repo):
Our internal governance rules currently only allow contributions to the official Backstage community-plugins repository. Since this plugin is hosted in a standalone repository, we’re temporarily maintaining an internal fork.
Do you have any plans or interest in moving this plugin into the Backstage community-plugins monorepo, or otherwise aligning with their contribution model?

Dependency/version management:
This is more or less a sub item of the fist point. The repository currently uses manual dependency pinning rather than the backstage-provided version policy tooling .
Are there plans to adopt the Backstage version policy approach (e.g., using backstage-cli versions:bump), or to otherwise align with the tooling recommended for plugin development?

This will help us understand whether our internal fork is likely to be a short-term workaround or something we’ll need to maintain longer-term.

Thanks again for your work on this project! Happy to provide any context that might help.

[zhammer]

hey! definitely interested in moving this into backstage community plugins. we haven't been as heavy backstage users recently (still have our backstage instance but less dedicated maintenance / improvement.)

do you know the process of getting something promoted to that repo?

[mathieugallant]

Hi! Thanks for the follow-up.

The highlights from the contributing document relate to how the workspace is setup, pipeline alignment and the codeowner setup.

Here's an example recent PR which moved a plugin there : backstage/community-plugins#4844

From a code perspective, the main workspace structure change would be the move towards the "dev/index pattern", meaning workspaces no longer include an actual Backstage app unless required for development. The tooling (yarn new) does that by default.

I'd be happy to provide more details or any other form of help you feel is appropriate.

Thanks again,

[zhammer]

hey @mathieugallant , sorry for the delay here, i've put this on our roadmap for early 2026

[komapa]

Early 2026 reporting for duty :)