# Pkg/News info

**URL:** https://discourse.julialang.org/t/pkg-news-info/21318
**Category:** Internals & Design
**Created:** [February 28, 2019, 8:32pm UTC](https://discourse.julialang.org/t/pkg-news-info/21318 "2019-02-28T20:32:55Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![Paul\_Soderlind](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/paul_soderlind/32/1753_2.png) [@Paul\_Soderlind](https://discourse.julialang.org/u/Paul_Soderlind)
#### Post date: [February 28, 2019, 8:32pm UTC](https://discourse.julialang.org/t/pkg-news-info/21318/1 "2019-02-28T20:32:55Z")

</div>

I believe that the package manager should (optionally) show a short “News” for each package that is updated.

Example: package _X_ is updated, and the developer knows that this will cause issues in package _Y_ but plans to fix it tomorrow. Printing this info to the screen when _X_ is updated would save lots of troubles for many of us.

---

<div class="post-metadata">

### Author: ![chakravala](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/chakravala/32/6832_2.png) [@chakravala](https://discourse.julialang.org/u/chakravala)
#### Post date: [February 28, 2019, 9:45pm UTC](https://discourse.julialang.org/t/pkg-news-info/21318/2 "2019-02-28T21:45:31Z")

</div>

Perhaps the message could be obtained from the release description from the tags on github? This should typically contain that sort of information and would simply need to be downloaded and printed.

---

<div class="post-metadata">

### Author: ![dawbarton](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/dawbarton/32/215461_2.png) [@dawbarton](https://discourse.julialang.org/u/dawbarton)
#### Post date: [March 1, 2019, 12:58pm UTC](https://discourse.julialang.org/t/pkg-news-info/21318/3 "2019-03-01T12:58:31Z")

</div>

I’ve seen this done before in DifferentialEquations.jl. IIRC a message was put into the build script to alert people to a (potentially silent) breaking change. As such, it’s already possible and just a case of the package maintainer being alive to the issues they might be causing…
