Knowledge base › Troubleshooting

Reading the build stamp in the changelog

Each release prints the date its binary was cut. That is the number your licence window is compared against.

Every entry in the changelog shows two dates: when the release was published, and the build stamp of the binary in it.

The build stamp is the one that matters for coverage. When the engine checks a key it compares the window in the key against that stamp. The publication date is editorial; the build stamp is what the comparison uses.

So to answer "is this release covered by what I bought", compare its build stamp against the window shown on your licence in the portal. If it is inside, download it. If it is outside, the builds you already have are unaffected and stay usable.

Last updated 2026-09-09.

Related

• Why the output has a demonstration mark Two causes, easy to tell apart: no key reached the engine, or the key does not cover this platform.