Patrick Jungermann

For me, it's also rather an enhancement to handle additional events. 🙂 I can confirm that so far, only `github.push` is used by the `GithubEntityProvider`. There might be other events...

The "Microsite" check is failing with out of memory. I tried retriggering it a couple of times already.

Planned follow-ups: - [ ] add event support to modules of other EntityProvider implementations that support events already - [ ] add support to the recently released signals plugin -...

@freben I tried to make use of version-bridge. However, it is not permitted to use it at such a package. Maybe, that wasn't really what you meant, though. ``` Package...

I will remove `version-bridge` for now.

I will take care of the merge conflicts

It seems like the change from ``` "@testing-library/jest-dom@npm:^6.0.0": version: 6.3.0 resolution: "@testing-library/jest-dom@npm:6.3.0" ``` to ``` "@testing-library/jest-dom@npm:^6.0.0": version: 6.4.0 resolution: "@testing-library/jest-dom@npm:6.4.0" ``` caused the issue with the E2E tests. ``` yarn...

FYI: we were using `@roadiehq/backstage-entity-validator` for some time, without any connection to our Backstage instance (not accessible to where we run it, too)

yes, I agree. This approach has limits. It is possible to build a CLI with your customizations, too. However, connecting to an API is much easier, requires less changes over...

We have it in place with built-in resolvers on the latest release version, and it works just fine. Ingestion of users as well as sign in. I agree with @benjdlambert...