# Use orbs with version tag or latest

**URL:** <https://discuss.circleci.com/t/use-orbs-with-version-tag-or-latest/29357>\
**Category:** Orbs\
**Created:** [March 28, 2019, 4:20pm UTC](https://discuss.circleci.com/t/use-orbs-with-version-tag-or-latest/29357 "2019-03-28T16:20:48Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![JohnRoesler](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/johnroesler/32/21812_2.png) [@JohnRoesler](https://discuss.circleci.com/u/JohnRoesler)\
**Post date:** [March 28, 2019, 4:20pm UTC](https://discuss.circleci.com/t/use-orbs-with-version-tag-or-latest/29357/1 "2019-03-28T16:20:48Z")

</div>

Is it possible to use an orb based on the major or minor version pin? For example:

Existing orb versions: 1.0.0, 1.0.1, 1.0.2

Then when I use it in my .circleci/config.yml it’d be nice to be able to point to my-org/my-orb@1.0 and have it pull the latest orb with that major/minor, so 1.0.2 to avoid updating all my config files each time we push a new orb version.

Any suggestions appreciated? Should we be doing this a different or better way?

---

<div class="post-metadata">

**Author:** ![jamesbraza](https://avatars.discourse-cdn.com/v4/letter/j/b487fb/32.png) [@jamesbraza](https://discuss.circleci.com/u/jamesbraza)\
**Post date:** [July 19, 2021, 10:58pm UTC](https://discuss.circleci.com/t/use-orbs-with-version-tag-or-latest/29357/2 "2021-07-19T22:58:51Z")

</div>

You should be able to do `@1.0`

```yaml
orbs:
  foo-orb: my-org/my-orb@1.0

```

See: [Orbs FAQ - CircleCI](https://circleci.com/docs/2.0/orbs-faq/#how-to-use-the-latest-version-of-an-orb)