# Hangfire 1.4 upgrade
**URL:** https://discuss.hangfire.io/t/hangfire-1-4-upgrade/857
**Category:** question
**Created:** [April 15, 2015, 4:09am UTC](https://discuss.hangfire.io/t/hangfire-1-4-upgrade/857 "2015-04-15T04:09:06Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@mma](https://discuss.hangfire.io/u/mma)
#### Post date: [April 15, 2015, 4:09am UTC](https://discuss.hangfire.io/t/hangfire-1-4-upgrade/857/1 "2015-04-15T04:09:07Z")
I’m running Hangfire 1.3.4 in an [asp.net](http://asp.net) mvc site with “application always running” ([http://docs.hangfire.io/en/latest/deployment-to-production/making-aspnet-app-always-running.html](http://docs.hangfire.io/en/latest/deployment-to-production/making-aspnet-app-always-running.html))
Looking through v1.4 release notes and changes ([http://hangfire.io/blog/2015/04/13/hangfire-1.4.0.html](http://hangfire.io/blog/2015/04/13/hangfire-1.4.0.html)) makes me wonder if I need to change anything in the configuration code, in the applicationHost.config, in the database (schema/object changes) or anywhere else after upgrading via NuGet.
What would be the upgrade path and would should I be especially careful about?
---
### Author:  [@odinserj](https://discuss.hangfire.io/u/odinserj)
#### Post date: [April 15, 2015, 9:27am UTC](https://discuss.hangfire.io/t/hangfire-1-4-upgrade/857/2 "2015-04-15T09:27:02Z")
You can do nothing, if you have automatic migrations enabled (true by default). This is a minor release (from version point of view), and there are no breaking changes – [http://hangfire.io/blog/2015/04/13/hangfire-1.4.0.html#upgrading](http://hangfire.io/blog/2015/04/13/hangfire-1.4.0.html#upgrading)
---
### Author:  [@odinserj](https://discuss.hangfire.io/u/odinserj)
#### Post date: [April 21, 2015, 1:15pm UTC](https://discuss.hangfire.io/t/hangfire-1-4-upgrade/857/3 "2015-04-21T13:15:19Z")