Releases: simnaut/astrodyn
Releases · simnaut/astrodyn
v0.1.0
Add workflow_dispatch recovery path to publish workflow (#474) When a tag-triggered publish run partially succeeds and then halts (e.g. crates.io sparse-index propagation times out after the first crate uploads), there was no way to resume without re-publishing the crates the registry already accepted. Adds `workflow_dispatch` with `from_crate` and `no_wait` inputs that pass through to `cargo xtask publish`, so resuming a v0.1.0 release after a partial failure is one `gh workflow run` away. Co-authored-by: Test User <test@test.com> Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Ephemeris kernels v1
Pinned ephemeris and orientation kernels for astrodyn_ephemeris consumers. This release is decoupled from the source-crate v* releases so kernel data can be updated independently.
| Asset | Size | SHA-256 |
|---|---|---|
de421.bsp |
16,790,528 | 08b20db2ae22488650641c5a9033e5bfda4b1c4b440cfeaf20f621cfa18ecdb3 |
de440.bsp |
32,726,016 | c1c7feeab882263fc493a9d5a5b2ddd71b54826cdf65d8d17a76126b260a49f2 |
moon_pa_de421_1900-2050.bpc |
1,770,496 | 656f90616403d75a75f0cd6c8830fc5b44f8cb4facb5ccb8915e752b397520cf |
astrodyn_ephemeris::data::load() resolves kernels in this order: ASTRODYN_EPHEMERIS_KERNELS_DIR → $CARGO_MANIFEST_DIR/assets/ (workspace builds) → user cache → fetch from this release (default-on fetch feature).