Hi,
When we are using orbs, we usually just specify the major version (e.g. orb-name@3), to decrease the amount of maintenance to keep these versions up to date. What we are missing right now, is some way to determine which version of an orb that a specific build actually resolved to. This can benefit build failure investigations.
i.e. a way to see what version of an orb a specific build used. Is this possible? It would be great for us.
Best,
Daniel
Yes, there is. I’m not in any orgs that are using CircleCI / orbs right now, so had to setup a test job to verify this, but one way is to go to the triple dots for a workflow, then click on ‘configuration file’ and toggle over from “source” to “compiled”.
There will be a comment near the top with the version it resolved to
So in my test, I had
version: 2.1
orbs:
shellcheck: circleci/shellcheck@3
workflows:
checks:
jobs:
- shellcheck/check
