|
| 1 | +### 2026-05-19: RNS 1.2.9 |
| 2 | + |
| 3 | +This release completes the operational functionality of the `rngit` system, which now has full release creation, fetch and verified update support using the `rngit release` command. Additionally, two chapters have been added to the manual should cover all the things that `rngit` is currently capable of. |
| 4 | + |
| 5 | +**Changes** |
| 6 | +- Added full `rngit` documentation to the manual |
| 7 | +- Added offline `.rsm` release manifest verification |
| 8 | +- Added the ability to fetch release updates directly from `.rsm` manifests |
| 9 | +- Added canonical `.rsm` release structure validator to `rnid` for import |
| 10 | +- Added `.rsm` manifest saving when using `rngit release fetch` |
| 11 | +- Added remote `HEAD` tracking for forks and mirros to `rngit` |
| 12 | +- Improved known destinations persist reliability |
| 13 | +- Improved page node ref link handling in `rngit` |
| 14 | +- Improved logging in various locations |
| 15 | + |
| 16 | +**Verified Retrieval** |
| 17 | +You can retrieve and verify this release over Reticulum using the built-in `rngit release` utility. To download all artifacts, and the release manifest for future updates, you can use the following command: |
| 18 | + |
| 19 | +```sh |
| 20 | +rngit release rns://7649a50d84610232d1416b41d2896aff/reticulum/reticulum fetch latest:all --signer bc7291552be7a58f361522990465165c |
| 21 | +``` |
| 22 | + |
| 23 | +To retrieve only the `.whl` package for installation, you can use: |
| 24 | + |
| 25 | +```sh |
| 26 | +rngit release rns://7649a50d84610232d1416b41d2896aff/reticulum/reticulum fetch latest:rns-1.2.8-py3-none-any.whl --signer bc7291552be7a58f361522990465165c |
| 27 | +``` |
| 28 | + |
| 29 | +**Release Signatures** |
| 30 | +Release artifacts include a signed `rsm` release manifest and `rsg` signature files that can be validated against the RNS release signing identity `<bc7291552be7a58f361522990465165c>` using `rnid`. To verify files, download the `rsm` and `rsg` signatures, make sure they are in the same folder as the release artifact, and run `rnid` signature verification with the release identity as the required signer: |
| 31 | + |
| 32 | +```sh |
| 33 | +rnid -i bc7291552be7a58f361522990465165c -V manifest.rsm *.rsg |
| 34 | +``` |
| 35 | + |
| 36 | +The `rnid` utility will then verify the signatures, and display whether they are valid. If the signature cannot be verified, the release has been tampered with and should be discarded. |
| 37 | + |
1 | 38 | ### 2026-05-18: RNS 1.2.8 |
2 | 39 |
|
3 | 40 | This release improves the `rngit` system with signed release manifest generation and automatic artifact signing. It also includes several additions to `rnid` and various minor fixes and improvements to the `rngit` system. |
|
0 commit comments