CircleCI Orb @volatile Not Resolvable
The @volatile orb tag resolves to the most recent dev release, which can be missing, replaced, or never published. Production configs should pin a stable semantic version instead.
What this error means
Config processing fails resolving an orb at @volatile, stating the dev version cannot be found.
circleci
Error resolving orb acme/deploy@volatile: no dev release found.
Pin a published version (e.g. acme/deploy@1.2.3).Common causes
No dev release behind @volatile
volatile points at the latest dev publish, which may not exist.
Dev release expired or replaced
Dev releases are mutable and can disappear.
How to fix it
Pin a published version
Reference a stable semantic version of the orb.
.circleci/config.yml
orbs:
deploy: acme/deploy@1.2.3How to prevent it
- Never use @volatile in production configs.
- Pin orbs to published semantic versions.
- Bump orb versions deliberately via PRs.
Frequently asked questions
What causes ""orb @volatile""?
volatile points at the latest dev publish, which may not exist.
How do I fix "orb @volatile"?
Reference a stable semantic version of the orb.
Related guides
CircleCI "Cannot find a definition for command" ErrorFix CircleCI cannot find a definition for command X - the named reusable command is undefined, misspelled, or…
CircleCI Reusable Config "maximum recursion depth exceeded"Fix CircleCI reusable config recursion errors - a command, executor, or orb that references itself directly o…
CircleCI "Your config has been disabled" - Uncommitted ConfigFix CircleCI builds that do not run because the project config is disabled or there is no committed .circleci…