Under specific scenario, single outdated deps.edn deps can be reported twice

[lread]

Problem

On Etaoin, I noticed that outdated deps in deps.edn are being reported twice by antq.

Minimal Reproduction

I narrowed it down to this minimal reproduction.

deps.edn

{:deps {babashka/fs {:mvn/version "0.5.22"}}}

bb.edn

{:tasks
 {foo {:doc "testing 123"
       :extra-deps {etaoin/etaoin {:local/root "."}}
       :task (println "foo")}}}

Run antq via:

clojure -Sdeps '{:deps {com.github.liquidz/antq {:mvn/version "2.11.1276"}}}' -M -m antq.core

Actual Behaviour

[##################################################] 1/1
| :file    | :name       | :current | :latest |
|----------|-------------|----------|---------|
| deps.edn | babashka/fs | 0.5.22   | 0.5.24  |
|          | babashka/fs | 0.5.22   | 0.5.24  |

Available changes:
- https://github.com/babashka/fs/blob/v0.5.24/CHANGELOG.md

Expected Behaviour

I would expect the outdated babashka/fs only be reported once.

Exploration

What if I skip the babashka analysis?

clojure -Sdeps '{:deps {com.github.liquidz/antq {:mvn/version "2.11.1276"}}}' -M -m antq.core --skip babashka
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
[##################################################] 1/1
| :file    | :name       | :current | :latest |
|----------|-------------|----------|---------|
| deps.edn | babashka/fs | 0.5.22   | 0.5.24  |

Available changes:
- https://github.com/babashka/fs/blob/v0.5.24/CHANGELOG.md

This gives the expected behaviour.

Next Steps

If you agree this is unexpected behaviour, I'm happy to take a peek.

[liquidz]

@lread Thanks! I could reproduce the problem.
This is unexpected behavior!