# Package workflow: tag new versions
**URL:** https://discourse.julialang.org/t/package-workflow-tag-new-versions/18803
**Category:** General Usage
**Created:** [December 18, 2018, 6:04pm UTC](https://discourse.julialang.org/t/package-workflow-tag-new-versions/18803 "2018-12-18T18:04:13Z")
**Posts on this page:** 11
**Page:** 1
### Author:  [@matthieu](https://discourse.julialang.org/u/matthieu)
#### Post date: [December 18, 2018, 6:04pm UTC](https://discourse.julialang.org/t/package-workflow-tag-new-versions/18803/1 "2018-12-18T18:04:13Z")
I develop a package in a .git folder in the `dev` folder of `.julia`. When I tag a new version of my package on Github (using Attobot), Julia does not update locally the version number of the package, even after I `git pull` the new tag. This means I cannot use any other package that require this new version. How to get around this issue?
---
### Author:  [@Nosferican](https://discourse.julialang.org/u/Nosferican)
#### Post date: [December 18, 2018, 7:45pm UTC](https://discourse.julialang.org/t/package-workflow-tag-new-versions/18803/2 "2018-12-18T19:45:22Z")
Has the PR been merged yet? Pkg won’t use the new tag until the registry has been updated. You can check the status of the PR on the repository for METADATA.
---
### Author:  [@matthieu](https://discourse.julialang.org/u/matthieu)
#### Post date: [December 18, 2018, 8:21pm UTC](https://discourse.julialang.org/t/package-workflow-tag-new-versions/18803/3 "2018-12-18T20:21:53Z")
yes the PR has been merged. Oh, so you say that `] update` does what I am looking for?
---
### Author:  [@Nosferican](https://discourse.julialang.org/u/Nosferican)
#### Post date: [December 18, 2018, 8:29pm UTC](https://discourse.julialang.org/t/package-workflow-tag-new-versions/18803/4 "2018-12-18T20:29:19Z")
If the PR has been merged to METADATA, it will be available in the General registry assuming correct bounds during the next synch. Then you should `]update ` and that will get you the latest release of the package.
---
### Author:  [@matthieu](https://discourse.julialang.org/u/matthieu)
#### Post date: [December 18, 2018, 8:58pm UTC](https://discourse.julialang.org/t/package-workflow-tag-new-versions/18803/5 "2018-12-18T20:58:24Z")
And it does so without erasing or unlinking the local version of the package in dev?
---
### Author:  [@Nosferican](https://discourse.julialang.org/u/Nosferican)
#### Post date: [December 18, 2018, 9:00pm UTC](https://discourse.julialang.org/t/package-workflow-tag-new-versions/18803/6 "2018-12-18T21:00:54Z")
If it is dev it will just pull the latest from the repository directly. If it is added, it will update to use the last registered release.
---
### Author:  [@fredrikekre](https://discourse.julialang.org/u/fredrikekre)
#### Post date: [December 18, 2018, 10:41pm UTC](https://discourse.julialang.org/t/package-workflow-tag-new-versions/18803/7 "2018-12-18T22:41:21Z")
> [@Nosferican](#):
>
> If it is dev it will just pull the latest from the repository directly.
No? Pkg does not touch package that are tracking a path.
If you want to leave the checked out state of your package and get back to a released version you should `pkg> free Package`.
---
### Author:  [@Nosferican](https://discourse.julialang.org/u/Nosferican)
#### Post date: [December 18, 2018, 10:50pm UTC](https://discourse.julialang.org/t/package-workflow-tag-new-versions/18803/8 "2018-12-18T22:50:56Z")
If the package is deved, say a local directory where one is working with the package, that get’s updated to reflect the current state of the directory so it shouldn’t need anything. If it is a remote, I believe it will do the same, but needs the `]up` to connect to the remote. If one is done with the development and wants to use the latest release, then `]free` will get you these.
---
### Author:  [@fredrikekre](https://discourse.julialang.org/u/fredrikekre)
#### Post date: [December 18, 2018, 10:56pm UTC](https://discourse.julialang.org/t/package-workflow-tag-new-versions/18803/9 "2018-12-18T22:56:20Z")
No, that is not how it works. Pkg will _completely ignore_ packages that are tracking a path:
> [@fredrikekre](#):
>
> Pkg does not touch package that are tracking a path.
---
### Author:  [@matthieu](https://discourse.julialang.org/u/matthieu)
#### Post date: [December 18, 2018, 11:51pm UTC](https://discourse.julialang.org/t/package-workflow-tag-new-versions/18803/10 "2018-12-18T23:51:38Z")
But Pkg.update seems to update the version number of the package in dev somehow, so that it matches the version number on github, right?
---
### Author:  [@00vareladavid](https://discourse.julialang.org/u/00vareladavid)
#### Post date: [December 19, 2018, 2:58am UTC](https://discourse.julialang.org/t/package-workflow-tag-new-versions/18803/11 "2018-12-19T02:58:27Z")
> [@matthieu](#):
>
> I cannot use any other package that require this new version
As long as a version has been registered, it should be possible to do e.g. `pkg> add SomePackage@1.2.3`. Does this not work? If this does work, then what is the specific issue that you are having?
There appears to be some confusion with regards to how `Pkg` works. It does not really make sense to talk about “versions” when referring to `dev`ed packages.