# Being informed about new registered packages and releases

**URL:** <https://discourse.julialang.org/t/being-informed-about-new-registered-packages-and-releases/30070>\
**Category:** Community\
**Tags:** question\
**Created:** [October 19, 2019, 5:31am UTC](https://discourse.julialang.org/t/being-informed-about-new-registered-packages-and-releases/30070 "2019-10-19T05:31:14Z")\
**Posts on this page:** 1\
**Showing post:** 19

<div class="post-metadata">

**Author:** ![tkf](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tkf/32/17635_2.png) [@tkf](https://discourse.julialang.org/u/tkf)\
**Post date:** [October 21, 2019, 11:08pm UTC](https://discourse.julialang.org/t/being-informed-about-new-registered-packages-and-releases/30070/19 "2019-10-21T23:08:58Z")

</div>

Package registry is just a plain git repository with a bunch of TOML files. So, why not read the data directly? Here is a one-linear to list newly added packages in past 100 commits:

```nohighlight
cd ~/.julia/registries/General && \
    git diff 'HEAD~100..origin/master' -- Registry.toml \
    | grep -E '^\+[^+]' \
    | sed -E 's/.*name = "([^"]+)".*/\1/g'

```

(Of course, it would be much more robust to parse the TOML files and compare the `Dict` in Julia.)

But I guess you need to scrape github release page to get the release notes.

---

_[View the full topic](https://discourse.julialang.org/t/being-informed-about-new-registered-packages-and-releases/30070)._