# How to properly add releases with PkgDev?

**URL:** https://discourse.julialang.org/t/how-to-properly-add-releases-with-pkgdev/961
**Category:** General Usage
**Tags:** package
**Created:** [December 15, 2016, 12:37am UTC](https://discourse.julialang.org/t/how-to-properly-add-releases-with-pkgdev/961 "2016-12-15T00:37:07Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![ChrisRackauckas](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/chrisrackauckas/32/77_2.png) [@ChrisRackauckas](https://discourse.julialang.org/u/ChrisRackauckas)
#### Post date: [December 15, 2016, 12:40am UTC](https://discourse.julialang.org/t/how-to-properly-add-releases-with-pkgdev/961/2 "2016-12-15T00:40:56Z")

</div>

This is how I do it:

> [@Problem registering a new package](https://discourse.julialang.org/t/problem-registering-a-new-package/401/2):
>
> I would just use Git directly at this point. The biggest help for me was getting GitKraken to make it easier. For packages, just go in to each directory which is having updating issues and update your master branch to the remote master branch. It may have “gotten stuck” by you updating something, or sometimes the way dependencies are done can cause this. No biggie. For METADATA, these days I just do it by hand because PkgDev.publish() never seems to work. I do the following: Go to the METADA…

You get that METADATA problem when you don’t tag from a different branch. You should always make PRs from the non-master branch (for any repo you work with). If you add to your workflow:

1. Check out a new branch on METADATA
2. Push changes to this branch
3. PR from that branch to JuliaLang/metadata-v2
4. Check out the local metadata-v2 again

you should be fine.

---

_[View the full topic](https://discourse.julialang.org/t/how-to-properly-add-releases-with-pkgdev/961)._