bundle with --component-renaming-conflicts-severity ignored the reference

[BanglanfengPan]

Describe the bug
--component-renaming-conflicts-severity seems only flag file reference but not pointer reference.

To Reproduce

1. Set up openapi.yaml like following

openapi: 3.1.0
paths:
  /foo:
    put:
      parameters:
        - $ref: 'A.yaml#/components/parameters/User'
    get:
      parameters:
        - $ref: 'B.yaml#/components/parameters/User'

2. Set up A.yaml and B.yaml with slightly different specs

• A.yaml

components:
  parameters:
    User:
      name: test
      in: path
      description: test-A

• B.yaml

components:
  parameters:
    User:
      name: test
      in: query
      description: test-B

Expected behavior

When run redocly bundle index.yaml --component-renaming-conflicts-severity=error, I would expect it to fail, as both User are conflicts in naming, but it went through without errors.

Logs

bundling index.yaml...
openapi: 3.1.0
paths:
  /foo:
    put:
      parameters:
        - $ref: '#/components/parameters/parameters-User'
    get:
      parameters:
        - $ref: '#/components/parameters/User'
components:
  parameters:
    User:
      name: test
      in: query
      description: test-B
    parameters-User:
      name: test
      in: path
      description: test-A
📦 Created a bundle for index.yaml at stdout 9ms.

Redocly version(s)

2.25.1

Node.js version(s)

Node v24.3.0
NPM 11.4.2

OS, environment

Mac M1

Additional context

[kanoru3101]

Thanks for reporting this, @BanglanfengPan

Your To Reproduce steps mention that both User are identical across A.yaml and B.yaml, but the Logs section shows two different schemas (one has an address property, the other doesn't). Could you update the reproduction steps to reflect the actual files you used?
The --component-renaming-conflicts-severity option only applies when schemas have the same name but different content (docs), so identical files wouldn't trigger it.

That said, looking at the Logs section, the bug is valid — with --component-renaming-conflicts-severity=error the bundle should have failed but it didn't. We'll look into this.

[BanglanfengPan]

Thanks for reporting this, @BanglanfengPan

Your To Reproduce steps mention that both User are identical across A.yaml and B.yaml, but the Logs section shows two different schemas (one has an address property, the other doesn't). Could you update the reproduction steps to reflect the actual files you used? The --component-renaming-conflicts-severity option only applies when schemas have the same name but different content (docs), so identical files wouldn't trigger it.

That said, looking at the Logs section, the bug is valid — with --component-renaming-conflicts-severity=error the bundle should have failed but it didn't. We'll look into this.

@kanoru3101 Thanks for looking into this! I must have mixed up my test cases when reporting it—sorry for the confusion.
I’ve updated the issue with a revised code snippet and description. Please let me know if you need any additional information!

[21f3000703]

could you assign this to me ? @BanglanfengPan

[kanoru3101]

Hi @21f3000703 ,
Thanks for your interest. We already have a fix for this in progress. You’re welcome to review the PR.

[kanoru3101]

@BanglanfengPan
The fix should be available in 2.27.1. Please let us know if you continue to experience any issues.

[BanglanfengPan]

Thank you @kanoru3101 ! I tested in my app, it works great!!