Versions and status
Every port is at 0.1.0-beta.1, the first public pre-release. The API can still change
before 0.1.0, and each release’s changelog says what changed. MitiBar is at
0.1.0-beta.1. C# NepDate has its own versions and
is at 2.0.7.
How versions work
Section titled “How versions work”- Each port follows Semantic Versioning on its own schedule. The core and the patro of one port always share a version and are released together.
- A data change, such as a new year’s holidays, is a patch release of each port: no API change.
- Pre-releases need asking for by name in most package managers: an exact pin in Cargo and SwiftPM,
the
betatag on npm, and--prewith pip. - Python spells the version the PEP 440 way,
0.1.0b1.
Releases are checked
Section titled “Releases are checked”Each port’s release workflow publishes from CI only, after the full test run, with build provenance where the registry supports it: trusted publishing to crates.io, npm and PyPI, signed artifacts on Maven Central, and attested archives for C++ and MitiBar. Each release’s notes say how to check its files.
Where to find each release
Section titled “Where to find each release”| Language | Releases |
|---|---|
| Rust | crates.io/crates/nepdate |
| Go | pkg.go.dev |
| TypeScript | npmjs.com/package/nepdate-core |
| Python | pypi.org/project/nepdate-core |
| Swift | GitHub releases |
| Kotlin and Java | Maven Central |
| C++ | GitHub releases |
| C | not released yet |
| C# | nuget.org/packages/NepDate |
| MitiBar | GitHub releases |