A human-readable record of meaningful product, methodology and data-contract changes. Operational fixes and interpretation changes remain traceable so users can understand why a displayed result may differ from an earlier release.
Changelog records changes that matter to users and data contracts
The release timeline describes feature, UX, security, data, integration and fix changes that can affect GeoLira behavior. It is not a raw list of every internal commit. Priority goes to user-visible functions, methodology, sources, privacy, alerts and application behavior.
Release kind helps explain what changed
Entries can be classified as feature, ux, data, security, integration or fix. This distinguishes a new tool from a data-contract change or a security correction. A version identifies a concrete product state, but a larger version number does not imply every layer was rebuilt.
A changed result may come from better source handling or methodology
When a historical result differs from a current one, the changelog helps determine whether the provider, quality filter, authored-index algorithm, renderer or privacy contract changed. GeoLira should not silently redefine a value without a version trail. Detailed source and methodology views remain the canonical place for technical meaning.