Skip to content

Bring the installation status block current for 0.1 - #159

Merged
NSchatz merged 1 commit into
mainfrom
launch-ready-fixround
Oct 8, 2026
Merged

NSchatz merged 1 commit into
mainfrom
launch-ready-fixround

Conversation

@NSchatz

@NSchatz NSchatz commented Oct 7, 2026

Copy link
Copy Markdown
Contributor

Bring the installation status block current for 0.1

docs-content/installation.md said the package was "pre-alpha ... on the
0.0.x-until-first-alpha ladder" and that the surface would keep moving
until first alpha. It is on npm at 0.1.0, and npm install @cosyte/dicom
installs in a fresh directory. The block now states 0.1 and the policy of
the 0.1 launch post (https://cosyte.com/blog/cosyte-0-1, "What 0.1
means"): the exported functions, the shapes they return and the warning
codes are the surface we keep stable, and below 1.0 a breaking change moves
the minor version, with the changelog saying how to migrate.

https://claude.ai/code/session_011dC8vE9axM3hqC8rNEX3W9

docs-content/installation.md said the package was "pre-alpha ... on the
0.0.x-until-first-alpha ladder" and that the surface would keep moving
until first alpha. It is on npm at 0.1.0, and npm install @cosyte/dicom
installs in a fresh directory. The block now states 0.1 and the policy of
the 0.1 launch post (https://cosyte.com/blog/cosyte-0-1, "What 0.1
means"): the exported functions, the shapes they return and the warning
codes are the surface we keep stable, and below 1.0 a breaking change moves
the minor version, with the changelog saying how to migrate.

Claude-Session: https://claude.ai/code/session_011dC8vE9axM3hqC8rNEX3W9
@NSchatz
NSchatz merged commit 34f6db6 into main Oct 8, 2026
10 checks passed
@NSchatz
NSchatz deleted the launch-ready-fixround branch October 8, 2026 00:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant