Skip to content

[chore] adjust registry june 2026 - #25

Merged
RogerKSI merged 1 commit into
mainfrom
adjust-registry-jun-2026
Jun 15, 2026
Merged

[chore] adjust registry june 2026#25
RogerKSI merged 1 commit into
mainfrom
adjust-registry-jun-2026

Conversation

@RogerKSI

Copy link
Copy Markdown
Member

📝 Summary

This PR [adds/modifies/deletes] the <Signal ID> signal in the registry.

🔄 Changes Introduced

  • [Added/Modified/Deleted] <Signal ID>:
    • Source ID: <source_id>, ID: <id>, Routes: <routes> (if applicable)
  • [If applicable] Added/Updated prefix configuration in prefix/<prefix>.yaml.
  • [If applicable] Removed <Signal ID> and ensured no unresolved dependencies.

📌 Band Signaling Hub Proposal

📎 Proposal Link: [Insert Forum Link Here]

✅ Checklist

  • Provided a valid Band Signaling Hub Proposal link.
  • Added/Updated the signal file in the appropriate signals/<prefix>/ directory.
  • Verified that any referenced prerequisite signals exist in the registry.
  • Ensured no circular dependencies are introduced.
  • [If applicable] Updated prefix configuration in prefix/<prefix>.yaml.
  • [If applicable] Updated documentation to reflect the new/modified signal.
  • [If applicable] For deleted signals: Verified that the deleted signal is not a dependency for other signals, or resolved any affected dependencies.

@RogerKSI
RogerKSI requested a review from Marca23 June 15, 2026 09:19
@RogerKSI
RogerKSI merged commit 095a605 into main Jun 15, 2026
1 check passed
@RogerKSI
RogerKSI deleted the adjust-registry-jun-2026 branch June 15, 2026 10:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants