Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions AMBASSADORS_MEMBERS.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -120,6 +120,7 @@
company: "Kong"
country: "🇲🇽"
isTscMember: true
isBoardMember: true
contributions:
Comment on lines 122 to 124
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

isBoardMember violates the current ambassadors schema

No other ambassador entry exposes this flag and the CI does not validate ambassadors, so we have no evidence the schema actually supports it. Consider either
a) extending the ambassadors JSON-schema first, or
b) storing board membership in a separate, already-validated list.

Until the schema is updated this extra field is just silent technical debt that can break downstream consumers expecting a strict schema.

🤖 Prompt for AI Agents
In AMBASSADORS_MEMBERS.yaml around lines 122 to 124, the field isBoardMember is
not supported by the current ambassadors schema and is not validated by CI,
risking schema violations. To fix this, either extend the ambassadors
JSON-schema to include isBoardMember before adding this field, or remove
isBoardMember from this file and instead track board membership in a separate,
schema-validated list to maintain strict schema compliance.

- type: "presentation"
title: "Speed-Up Kafka Delivery with AsyncAPI & Microcks"
Expand Down
2 changes: 2 additions & 0 deletions MAINTAINERS.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -122,6 +122,7 @@
availableForHire: false
linkedin: fmvilas
isTscMember: true
isBoardMember: true
repos:
Comment on lines 123 to 126
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Schema-breaking field causes CI failure

GitHub Actions reports “Validation of maintainers file failed”.
The only new key is isBoardMember: true, so the maintainers schema clearly does not recognise it.

Either update the schema (preferred) or drop the key to restore the pipeline:

-  isBoardMember: true
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
linkedin: fmvilas
isTscMember: true
isBoardMember: true
repos:
linkedin: fmvilas
isTscMember: true
repos:
🤖 Prompt for AI Agents
In MAINTAINERS.yaml around lines 123 to 126, the new field `isBoardMember: true`
is causing CI validation failures because it is not recognized by the current
maintainers schema. To fix this, either update the maintainers schema to include
the `isBoardMember` field or remove the `isBoardMember` key from this file to
restore CI pipeline functionality.

- spec
- spec-json-schemas
Expand Down Expand Up @@ -560,6 +561,7 @@
availableForHire: false
company: AsyncAPI Initiative
isTscMember: true
isBoardMember: true
repos:
- website
- conference-website
Expand Down
Loading