You should not expect to see any differences in simulation results when running a project within different versions of the same branch (e.g. v4.6.x). These "maintenance patch releases", for example x.x.1, x.x.2, x.x.3, only include bug fixes. They do not include any changes to the Master Library components. Therefore, customers can upgrade software in the middle of a project and not experience any differences.
Refer to the following paragraph for more details on our release numbering system.
Release Numbering System
Software releases are identified by a numbering system, which is used to designate the release type. There are three types of releases as shown:
A “Major Release”, for example version 4.0.0, contains a significant number of new features and functionalities, such that it warrants a brand new product. These types of releases have historically occurred every several years.
A “Minor Release”, for example version 4.6.3, typically provides a handful of new and enhanced features, but not enough to justify a new product. Minor releases may be released approximately yearly.
A maintenance patch, for example, version 4.6.3, is purely a bug fix release. Maintenance patches may be released more than once per year.