[BUG] bundle creates invalid document (refs)

[black-snow]

Describe the bug.

asyncapi bundle creates invalid documents.

main.yaml

asyncapi: 3.0.0
info:
  title: demo
  version: '1'
operations:
  A:
    $ref: "./_sub.yaml#/components/operations/A"
channels:
  A:
    $ref: "./_sub.yaml#/components/channels/A"

_sub.yaml

components:
  operations:
    A:
      action: send
      channel:
        $ref: '#/components/channels/A'
      messages:
        - $ref: '#/components/channels/A/messages/A'
  channels:
    A:
      messages:
        A:
          $ref: '#/components/messages/A'
  messages:
    A:
      payload:
        type: object

asyncapi validate main.yaml
asyncapi bundle ./main.yaml --output final.yml
asyncapi validate final.yml

produced invalid output:

asyncapi: 3.0.0
info:
  title: demo
  version: '1'
channels:
  A:
    messages:
      A:
        payload:
          type: object
operations:
  A:
    action: send
    channel:
      $ref: '#/components/channels/A'
    messages:
      - $ref: '#/components/channels/A/messages/A'

Expected behavior

It should've either updated the refs to root or moved the channels/ops/messages to components (if allowed).

Screenshots

How to Reproduce

see above

🖥️ Device Information [optional]

• Operating System (OS): macOS latest
• Browser: WF
• Browser Version: latest

👀 Have you checked for similar open issues?

• I checked and didn't find similar issue

🏢 Have you read the Contributing Guidelines?

• I have read the Contributing Guidelines

Are you willing to work on this issue ?

No, someone else can work on it

[black-snow]

When I move channels and operations to root the produced doc is fine.

[Varadraj75]

Hey @Shurtu-gal @Souvikns @AayushSaini101 ,

Edit: My earlier comment was about asyncapi optimize, which is not relevant to this issue — thanks for flagging that.

For asyncapi bundle, the problem is that the bundled output keeps $refs pointing to #/components/... while the actual channels, operations, and messages are moved to the root, resulting in an invalid document.

The bundler should either rewrite $refs to the new root paths or keep the referenced definitions under components consistently.

[black-snow]

@Varadraj75 did you mean to post this here (vs. in my optimize bug ticket)? This issue is about bundling.

[Varadraj75]

@black-snow
Thanks for the clarification — you’re right, my earlier comment was about optimize, not bundle.

For bundling, the issue seems to be that $refs still point to #/components/... even though the bundled output moves channels/operations/messages to the root, making the document invalid.

The bundler should either rewrite those $refs to the new root paths or keep the definitions under components consistently.