Library Release Versioning
Versioned releases and a changelog let you tie any valuation back to a specific library build and behaviour set.
Explanation
The analytics library is packaged and released with version numbers that distinguish breaking, feature, and bugfix changes.
Tagged releases in Git and a changelog document what changed so users and auditors can match results to code versions.
Risk and trading systems depend on explicit library versions instead of floating on the current state of the main branch.
versioningreleasessemanticchangelog
Interactive visualisation
Library release versioning
Tie any result to an exact build and behaviour set.
Current version
1.4.2
Choose bump
Next release
1.4.3
Rule: production systems should depend on an explicit version, not “whatever is on main”.
Changelog (latest first)
- 1.4.2 — bugfix: daycount edge-case
- 1.4.1 — bugfix: curve interpolation guard
- 1.4.0 — feature: new bootstrapping method
- 1.3.0 — feature: additional Greeks
Interpretation
- Version tags let you reproduce valuations precisely.
- A changelog is an audit narrative: what changed, and why results might differ.
- Major bumps should be rare and explicit, because they break downstream systems.