I’m worried these new features like scope, layout, if I just update the phoenix version of mix.exs and install the package, don’t know whether if current app will be broken. How did you do this step?
We usually go to the press release, and look for backward compatibility mentions. Phoenix team is very attentive to user’s upgrade experience, that’s why you’d find a link to changelog there. “Note: This is a backwards compatible release with a few deprecations.”
The changelog would have told you what’s to pay attention to.
Releases, breaking backward compatibility, are usually accompanied with an instruction on painless uprage.
2 Likes
Haha. That’s my speciality 
2 Likes
Use this: PhoenixDiff · v1.7.21 to v1.8.0
Work your way through it, line by line, and mirror any relevant changes you see.
Also, check out the changelog, as already mentioned.
3 Likes
I have migrated some Phoenix applications 1.7 to 1.8 and summary a guide at post. I hope that is useful for you.
4 Likes
Thank you ! Actually I have read your article these days, but still a little hesitant : )
1 Like
Yep, I wrote that in early days of RC version (for using daisyUI). If you have any suggestion or comment, please let me know.
1 Like
The 1.7 release had an upgrade guide pinned to the top and it seems like many were expecting this again for 1.8.
Given that this is I think the fourth thread we have had about this on here, perhaps that’s a sign that future releases should include “no upgrade guide is needed for this release” at the top or something to that effect?
2 Likes
