A developer working across multiple screens and a laptop

RESOURCES → DEVELOPER CENTER → RELEASE NOTES

Know What Changed Before It Changes Your Integration.

A transparent developer record of platform, API, SDK, webhook, security and documentation changes — organized around impact and required action, not around a news cycle.

What changed, why did it change, and what does the change mean for my system?

Developer honesty: no public API, SDK packages, webhook deliveries, release history or status monitoring are live yet. Every contract, payload and console below is a clearly-labeled illustrative design — no fabricated endpoints, SDK support, incidents or uptime figures.

Release Notes

One Developer Center · six connected surfacesDocumentation How do I understand/build this?API Reference What exactly is the contract?SDKs How do I build this in my stack?Webhooks How do I respond to events?Release Notes What changed and what must I do?System Status Is anything operationally wrong?

Change taxonomy & impact labels

New capabilityEnhancementBehavior changeAPI/schema changeSDK releaseWebhook changeDeprecationSecurity updatePerformance/operational changeDocumentation correctionIncident follow-up

InformationalReview RecommendedAction RequiredBreaking Change

Impact labels are change-management labels, not quality scores.

The change timeline

Review RecommendedAPI/schema changev1.2.0 · 2026-09-15 · Genome

Evidence object gains optional expiry semantics

What —: Evidence objects may now carry an expiry date; reads return expiry-aware state.
Why —: Certification-like evidence decays; consumers need the state without recomputing.
Action —: Review any consumer that treats evidence as immutable forever.

Review RecommendedWebhook changev1.2.0 · 2026-09-15 · Webhooks

genome.evidence.created schema v1.1 adds provenance array

What —: Payload now includes a provenance array next to source refs.
Why —: Consumers asked for one-step-traceable origin data.
Action —: New field is additive; older parsers keep working.

Action RequiredDeprecationv1.1.0 · 2026-08-20 · API

Legacy score-only readiness field deprecated

What —: score without disclosure panel is deprecated (sunset v2.0).
Why —: Scores without population/period/status mislead (see the Research library).
Action —: Switch to the readiness state object; see migration guide.

Action RequiredSecurity updatev1.1.0 · 2026-08-20 · Webhooks

Signature scheme requires timestamp header

What —: Unsigned or stale-timestamp deliveries are rejected with 401 web.
Why —: Replay protection tightened.
Action —: Verify signatures with the updated handler samples.

InformationalNew capabilityv1.0.0 · 2026-07-10 · Platform

Illustrative public contract design published

What —: First public design of the API/webhook contract surface.
Why —: Developer Center transparency.
Action —: None — explore the design.

InformationalDocumentation correctionv1.0.0 · 2026-07-10 · Docs

Illustrative fixtures labeled consistently

What —: All sample payloads now carry the illustrative label.
Why —: Honesty rules: no fixture may read as production data.
Action —: None.

Before / after — contract changes ship with diffs

Before (v1.1) · schema · illustrative

{ "readiness": 0.82 }

After (v1.2) · schema · illustrative

{ "readiness": {
  "state": "ready",
  "population": "engineering · site-A",
  "period": "2026-Q3",
  "data_status": "illustrative"
} }

Impact analyzer

In the live Center, you select your API/SDK/webhook version or product area — the page filters the changes that may affect that configuration and explains why, routing to evidence and migration guidance. It never asserts that everyone is affected.

Deprecation center

Score-only readiness field

Deprecated v1.1.0 (2026-08-20) · Sunset v2.0 (date TBD) · Replacement: Readiness state object

Release governance: every entry carries timestamp/version, breaking changes link to migration steps, lifecycle metadata is consistent, and security disclosures follow controlled-disclosure discipline. Entries here are illustrative design history — the real timeline starts with the public platform.

Was this page accurate?