# WARNING: 0.7.0 breaking changes

**URL:** <https://discourse.numenta.org/t/warning-0-7-0-breaking-changes/2200>\
**Category:** NuPIC\
**Tags:** release\
**Created:** [April 11, 2017, 5:01pm UTC](https://discourse.numenta.org/t/warning-0-7-0-breaking-changes/2200 "2017-04-11T17:01:10Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![rhyolight](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.numenta.org/rhyolight/32/3922_2.png) [@rhyolight](https://discourse.numenta.org/u/rhyolight)\
**Post date:** [April 14, 2017, 6:09pm UTC](https://discourse.numenta.org/t/warning-0-7-0-breaking-changes/2200/4 "2017-04-14T18:09:24Z")

</div>

You might have runtime problems caused by this code being merged into master if you are running local examples or tests from tip of master against an older version of NuPIC.

If you install nupic from binary (`pip install nupic`), that means you get the latest stable version of NuPIC, which could be days or weeks old. If you want to run unit tests or examples from the latest source code, it might cause runtime errors. In order to run tests and examples, make sure that you have checked out proper commit SHA in git to sync the tests with the stable version of NuPIC.

For example, if you installed nupic `0.5.7`, you should run this command in your git repo before running unit tests:

```
git fetch upstream

```

Where `upstream` is a remote that points to [https://github.com/numenta/nupic](https://github.com/numenta/nupic). This will fetch any tags for releases from the remote.

```
git checkout tags/0.5.7

```

This will set your local code to match the release code. Beware this could alter any changes you’ve made to your local filesystem.

Now you can run tests and local examples.

---

_[View the full topic](https://discourse.numenta.org/t/warning-0-7-0-breaking-changes/2200)._