Sebastian Poxhofer

Corepack issue seems to be resolved https://github.com/nodejs/corepack/issues/379 Also consider using dependencyDashboardApprovals instead of allowedVersion as the former you have only check the box on the Dashboard to get PR instead...

Correction: My issue has not the same origin, tough I'm keeping this comment in case other people run into the same problem. I'm seeing the same error with `@backstage/plugin-catalog-backend-module-github` with...

Custom data parser have to emit already known entities, so I'm not thinking this is the right fit. If not the processor endpoint, maybe this should be a reader/parser endpoint.

Good to know! I have thought there is a more strict validation before ingestion in the processor pipelines. I feel this is an argument to put this in a `CatalogModelExtensionPoint`...

I have changed the used extension point to `CatalogModelExtensionPoint`

Looking forward to this PR as it should enable implementing MergeQueue with required checks pretty easily.

I have ran into this today too. reference: https://github.com/Azure/azure-rest-api-specs/issues/17498

No, `helm-values` is used for both. V2 & V3 `helm-requirements` is only valid for V2

> 👋🏽 I still consider this to be a need that's unmet by the JS tooling; the ability to use `@tracer.start_as_active_span` as a decorator in Python makes it much easier...

> Given the concerns, can we look into using [Kafka Raft](https://developer.confluent.io/learn/kraft/) (Kafka without zookeeper) to help minimize the footprint of this addition? I have tried initially to use Raft, but...