Skip to content

v2 transition trackingΒ #102

Description

@lorisleiva

Tracking issue for the Codama IDL v2 major transition, following RELEASING.md.

Status: πŸ”΅ Candidacy β€” release candidates shipping, no candidate declared yet.

Event Date
Cut 2026-08-27
First rc –
Candidate declared –
Promote –

v2 scope

Ten design issues, in three tiers. Tier A is settled design; Tier B is committed direction with open design points; Tier C has an explicit go/no-go before the candidate is declared and slips to v3 without blocking. Ticked when the change lands in src/v2/.

Scope checklist

Tier A β€” settled

Tier B β€” committed, design open

Tier C β€” go/no-go gate

Candidate declaration

Declared on the announcement thread (body edit + comment). Not declared yet.

Release train
  • codama: freeze v1 node types, add upgradeV1ToV2, living spec pin β†’ rc
  • codama-rs: promote the workspace to 1.0.0 on main (freeze the v1-era API), then cut the 1.x maintenance branch and mirror the codama steps in Rust
  • renderers + CLI: cut their own majors to consume the new codama major
Phase checklists

Cut (docs)

Candidacy (docs)

Promote (docs)

  • Dispatch promote (commits --tag release-1.x on 1.x, pre exit on main, flips default branch)
  • Merge the release PR β€” 2.0.0 publishes and takes latest
  • Audit git log --oneline main..1.x for unported commits (superset guarantee)
  • Closing announcement; close this issue
Ecosystem adoption checklist

Integrators (explorers, wallets, indexers, program repos) and their validation status against the candidate. Gates the promote. To be filled during candidacy.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions