You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 12, 2026. It is now read-only.
Publish CDT++ v1.0.0 and verify the citable GitHub and Zenodo release.
This is the last issue in the v1.0.0 release dependency graph. It starts only
after the release-readiness approval in #90 is closed. No implementation, test
design, documentation authoring, dependency modernization, new feature work,
or repository archival belongs here. Post-release stabilization and eventual
archival are tracked separately in #155.
Closing #97 does not archive the repository. Issue #155 remains open for a
maintenance-only stabilization window of owner-determined length. A critical
defect must use a new patch release rather than moving or replacing the
v1.0.0 tag.
Summary
Publish CDT++ v1.0.0 and verify the citable GitHub and Zenodo release.
This is the last issue in the v1.0.0 release dependency graph. It starts only
after the release-readiness approval in #90 is closed. No implementation, test
design, documentation authoring, dependency modernization, new feature work,
or repository archival belongs here. Post-release stabilization and eventual
archival are tracked separately in #155.
Preconditions
and Zenodo deposition metadata are final.
Release execution sequence
evidence, and the causal-triangulations successor link.
and links.
CITATION.cff, rerun the metadataand documentation checks, and merge that focused post-release commit.
release, documentation, citation, and successor links remain usable.
eventual archival gate, then close Publish CDT++ v1.0.0 and verify the citable release #97.
Acceptance criteria before closing #97
CITATION.cffcontains the concept DOI and the version-specific record DOIin their documented roles.
Post-release handoff
Closing #97 does not archive the repository. Issue #155 remains open for a
maintenance-only stabilization window of owner-determined length. A critical
defect must use a new patch release rather than moving or replacing the
v1.0.0 tag.