# Github Package Registry

**URL:** https://discourse.julialang.org/t/github-package-registry/24142
**Category:** Package Announcements
**Created:** [May 12, 2019, 4:23pm UTC](https://discourse.julialang.org/t/github-package-registry/24142 "2019-05-12T16:23:34Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![essenciary](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/essenciary/32/210469_2.png) [@essenciary](https://discourse.julialang.org/u/essenciary)
#### Post date: [May 12, 2019, 4:23pm UTC](https://discourse.julialang.org/t/github-package-registry/24142/1 "2019-05-12T16:23:34Z")

</div>

Stumbled onto this - might be interesting for Pkg integration:

> **[Introducing GitHub Package Registry](https://github.blog/2019-05-10-introducing-github-package-registry/)**
>
> With GitHub Package Registry your packages are at home with their code—sign up for the limited beta to try it out.

---

<div class="post-metadata">

### Author: ![Tamas\_Papp](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tamas_papp/32/25949_2.png) [@Tamas\_Papp](https://discourse.julialang.org/u/Tamas_Papp)
#### Post date: [May 12, 2019, 5:59pm UTC](https://discourse.julialang.org/t/github-package-registry/24142/2 "2019-05-12T17:59:17Z")

</div>

The analytics one could derive from this may be interesting, OTOH I think we are already _too_ integrated with Github (the new registry setup is of course a significant improvement and allows other integrations). I would prefer to stick with open architectures for all core functionality.

---

<div class="post-metadata">

### Author: ![Nosferican](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/nosferican/32/9275_2.png) [@Nosferican](https://discourse.julialang.org/u/Nosferican)
#### Post date: [May 13, 2019, 2:41am UTC](https://discourse.julialang.org/t/github-package-registry/24142/3 "2019-05-13T02:41:55Z")

</div>

From having watch the talk, it seems like the Github registry process just hooks to the language specific tools (package manager/registry/bots). For example, having the registry give the Github repository to download could make use of the global CDN. The new bot to match releases in the registry with release/tags in the repository would be trivial through the common Github pipeline, etc. It doesn’t replace any of the tools, but rather offers a standard way to interact between them. At least, that is what I got from the 30 talk. I signed for the beta to check it out. It would be great if the package people reach out to get more specifics and a ticket for the next programming languages to implement.

[Announcement and tutorial (video)](https://www.youtube.com/watch?v=N_-Cu9_2YAA&ab_channel=GitHub)
