# Prevent Juno startup from triggering package updates

**URL:** <https://discourse.julialang.org/t/prevent-juno-startup-from-triggering-package-updates/38465>\
**Category:** Juno\
**Created:** [April 30, 2020, 4:46am UTC](https://discourse.julialang.org/t/prevent-juno-startup-from-triggering-package-updates/38465 "2020-04-30T04:46:32Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jaynick](https://avatars.discourse-cdn.com/v4/letter/j/71c47a/32.png) [@jaynick](https://discourse.julialang.org/u/jaynick)\
**Post date:** [April 30, 2020, 4:46am UTC](https://discourse.julialang.org/t/prevent-juno-startup-from-triggering-package-updates/38465/1 "2020-04-30T04:46:33Z")

</div>

I noticed that after staring atom and initially attaching to a (remote) Julia,  
some package upgrades are triggered.

Before printing the julia logo we see

```nohighlight
Updating registry at ~/.julia/registries/General
Resolving package versions...
...
Downloading artifacts
     # OpenBLAS, ZeroMQ, others
Updating ~/.julia/environments/v1.4/Project.toml
+Atom v0.12.10
Updating ~/.julia/environments/v1.4/Manifest.toml
OpenBLAS_jll v0.3.9+1 -> v0.3.9+2

```

In particular, note that OpenBLAS has been updated (among a couple others)

Updating to the latest version is a good thing in general,  
however **my program needs to be exactly reproducable,**  
so I want to be in control of when packages change versions.

_How can I prevent these version upgrades_ when launching julia from juno?

---

<div class="post-metadata">

**Author:** ![pfitzseb](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/pfitzseb/32/45566_2.png) [@pfitzseb](https://discourse.julialang.org/u/pfitzseb)\
**Post date:** [April 30, 2020, 7:45am UTC](https://discourse.julialang.org/t/prevent-juno-startup-from-triggering-package-updates/38465/2 "2020-04-30T07:45:47Z")

</div>

Juno only does Pkg operations when it can’t find it’s dependencies (Atom.jl and Juno.jl, specifically). If you manually install those then we won’t do anything to your global env.

Note that you should probably be using a local environment if you need exact reproducability.