Upgrading from release n-2 to release n - how can we be sure changes from n-1 are applied?

[JeremiP]

We have a test instance that's been on Washington for a longer while. We've recently upgraded to Yokohama, and want to make sure that all the changes from Xanadu were also included.

Is there any documentation that describes how that works? I'm having some trouble pinpointing where this would be stated using Google and SN doc search alone.

I figured that perhaps the zip files mentioned in the from / to fields of the System Upgrade records are full SN releases -

- meaning they can be used non-incrementally for upgrades such as ours - but I don't think there's a way for us to download them and manually compare the files they contain 🙂

[Dr Atul G- LNG]

Hi @JeremiP 

Practically, if you go to the latest release, earlier release changes are often included as well. In your case, ServiceNow provides a way to see those changes. You can check the release notes or documentation to review what updates or changes have been included.

https://www.servicenow.com/docs/bundle/yokohama-release-notes/page/release-notes/rn-combined/yokoham...

[Mark Manders]

The zipfiles will contain your release, so going through them to see what was Xanadu and what Yokohama, will only be possible if you know which is which. There is no good way to check on that.

The best way is to check the release notes. But do realize that things that are introduced/changed in Xanadu can also be changed (or deprecated) on Yokohama. Yokohama is build on top of Xanadu, so it will contain those changes, but checking will be very difficult, since you don't have anything to compare it to. 

It's a 'just trusts that it does' and 'check release notes' to make sure. 

You can personalize the release notes to see what changes when you upgrade from W to Y. That will be the release notes you can share internally for testing/information.