Skip to content

Commit 422dc05

Browse files
author
Mark Qvist
committed
Updated changelog
1 parent 50c0a35 commit 422dc05

1 file changed

Lines changed: 14 additions & 173 deletions

File tree

‎Changelog.md‎

Lines changed: 14 additions & 173 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,10 @@
1-
### 2026-05-29: RNS 1.3.4
1+
### 2026-06-01: RNS 1.3.5
22

3-
This release fixes a regression that could cause sub-optimal path selection under conditions where the same announce was received within a very short timespan on different interfaces, as well as a few other bugs and inefficiencies.
3+
This maintenance release contains an important fix for `AutoInterface` reliability when roaming between different physical networks.
44

55
**Changes**
6-
- Fixed regression in inbound announce de-duplication
7-
- Fixed missing check for shared instance type configuration conflict
8-
- Fixed superfluous path state configuration on new announce from new destinations
9-
- Improved cleanup of stale known destinations
10-
- Improved shared instance RPC handling
6+
- Fixed UDP listener replacement deadlocking inbound AutoInterface traffic when fast-roaming between physical interfaces or WiFi APs
7+
- Fixed some paths never resolving when using other interfaces at the same time as a deadlocked AutoInterface
118

129
**Verified Retrieval**
1310
You can retrieve and verify this release over Reticulum using the built-in `rngit release` utility. To retrieve only the installation `.whl` package, and the release manifest for future updates, you can use:
@@ -37,6 +34,16 @@ rnid -i bc7291552be7a58f361522990465165c -V rns_*.rsm *.rsg
3734

3835
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.
3936

37+
### 2026-05-29: RNS 1.3.4
38+
39+
This release fixes a regression that could cause sub-optimal path selection under conditions where the same announce was received within a very short timespan on different interfaces, as well as a few other bugs and inefficiencies.
40+
41+
**Changes**
42+
- Fixed regression in inbound announce de-duplication
43+
- Fixed missing check for shared instance type configuration conflict
44+
- Fixed superfluous path state configuration on new announce from new destinations
45+
- Improved cleanup of stale known destinations
46+
- Improved shared instance RPC handling
4047

4148
### 2026-05-28: RNS 1.3.3
4249

@@ -45,35 +52,6 @@ This release fixes a regression in persistence of known destination on Windows.
4552
**Changes**
4653
- Fixed regression in known destinations persist on Windows
4754

48-
**Verified Retrieval**
49-
You can retrieve and verify this release over Reticulum using the built-in `rngit release` utility. To retrieve only the installation `.whl` package, and the release manifest for future updates, you can use:
50-
51-
```sh
52-
rngit release rns://7649a50d84610232d1416b41d2896aff/reticulum/reticulum fetch "latest:rns-*.whl" --signer bc7291552be7a58f361522990465165c
53-
```
54-
55-
To download all artifacts, including the documentation and source archive, you can use the following command:
56-
57-
```sh
58-
rngit release rns://7649a50d84610232d1416b41d2896aff/reticulum/reticulum fetch latest:all --signer bc7291552be7a58f361522990465165c
59-
```
60-
61-
**Release Signatures**
62-
Release artifacts include a signed `rsm` release manifest and `rsg` signature files that can be validated against the RNS release signing identity `<bc7291552be7a58f361522990465165c>` using `rngit` or `rnid`. To perform an offline verification of all release artifacts using a manifest:
63-
64-
```sh
65-
rngit release rns_*.rsm verify --signer bc7291552be7a58f361522990465165c
66-
```
67-
68-
To verify release artifacts using individual `rsg` files, while also verifying the manifest itself, 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:
69-
70-
```sh
71-
rnid -i bc7291552be7a58f361522990465165c -V rns_*.rsm *.rsg
72-
```
73-
74-
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.
75-
76-
7755
### 2026-05-28: RNS 1.3.2
7856

7957
This release adds commit signing and validation support to the `rngit` system, as well as improvements to the blackhole functionality.
@@ -86,70 +64,13 @@ This release adds commit signing and validation support to the `rngit` system, a
8664
- Added option to configure blackhole update interval
8765
- Added configuration option to log without timestamps
8866

89-
**Verified Retrieval**
90-
You can retrieve and verify this release over Reticulum using the built-in `rngit release` utility. To retrieve only the installation `.whl` package, and the release manifest for future updates, you can use:
91-
92-
```sh
93-
rngit release rns://7649a50d84610232d1416b41d2896aff/reticulum/reticulum fetch "latest:rns-*.whl" --signer bc7291552be7a58f361522990465165c
94-
```
95-
96-
To download all artifacts, including the documentation and source archive, you can use the following command:
97-
98-
```sh
99-
rngit release rns://7649a50d84610232d1416b41d2896aff/reticulum/reticulum fetch latest:all --signer bc7291552be7a58f361522990465165c
100-
```
101-
102-
**Release Signatures**
103-
Release artifacts include a signed `rsm` release manifest and `rsg` signature files that can be validated against the RNS release signing identity `<bc7291552be7a58f361522990465165c>` using `rngit` or `rnid`. To perform an offline verification of all release artifacts using a manifest:
104-
105-
```sh
106-
rngit release rns_*.rsm verify --signer bc7291552be7a58f361522990465165c
107-
```
108-
109-
To verify release artifacts using individual `rsg` files, while also verifying the manifest itself, 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:
110-
111-
```sh
112-
rnid -i bc7291552be7a58f361522990465165c -V rns_*.rsm *.rsg
113-
```
114-
115-
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.
116-
117-
11867
### 2026-05-22: RNS 1.3.1
11968

12069
This maintenance release fixes a single bug.
12170

12271
**Changes**
12372
- Fixed regression in request response transfer size accumulator
12473

125-
**Verified Retrieval**
126-
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:
127-
128-
```sh
129-
rngit release rns://7649a50d84610232d1416b41d2896aff/reticulum/reticulum fetch latest:all --signer bc7291552be7a58f361522990465165c
130-
```
131-
132-
To retrieve only the `.whl` package for installation, and the release manifest, you can use:
133-
134-
```sh
135-
rngit release rns://7649a50d84610232d1416b41d2896aff/reticulum/reticulum fetch "latest:rns-*-py3-none-any.whl" --signer bc7291552be7a58f361522990465165c
136-
```
137-
138-
**Release Signatures**
139-
Release artifacts include a signed `rsm` release manifest and `rsg` signature files that can be validated against the RNS release signing identity `<bc7291552be7a58f361522990465165c>` using `rngit` or `rnid`. To perform an offline verification of all release artifacts using a manifest:
140-
141-
```sh
142-
rngit release rns_*.rsm fetch latest:all --offline --signer bc7291552be7a58f361522990465165c
143-
```
144-
145-
To verify releases using individual `rsg` files, while also verifying the manifest itself, 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:
146-
147-
```sh
148-
rnid -i bc7291552be7a58f361522990465165c -V rns_*.rsm *.rsg
149-
```
150-
151-
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.
152-
15374
### 2026-05-21: RNS 1.3.0
15475

15576
This maintenance release fixes a number of bugs.
@@ -164,28 +85,6 @@ This maintenance release fixes a number of bugs.
16485
- Adjusted timeouts for remote operations in `rngit`
16586
- Updated documentation
16687

167-
**Verified Retrieval**
168-
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:
169-
170-
```sh
171-
rngit release rns://7649a50d84610232d1416b41d2896aff/reticulum/reticulum fetch latest:all --signer bc7291552be7a58f361522990465165c
172-
```
173-
174-
To retrieve only the `.whl` package for installation, you can use:
175-
176-
```sh
177-
rngit release rns://7649a50d84610232d1416b41d2896aff/reticulum/reticulum fetch latest:rns-1.3.0-py3-none-any.whl --signer bc7291552be7a58f361522990465165c
178-
```
179-
180-
**Release Signatures**
181-
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:
182-
183-
```sh
184-
rnid -i bc7291552be7a58f361522990465165c -V manifest.rsm *.rsg
185-
```
186-
187-
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.
188-
18988
### 2026-05-19: RNS 1.2.9
19089

19190
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.
@@ -201,28 +100,6 @@ This release completes the operational functionality of the `rngit` system, whic
201100
- Improved page node ref link handling in `rngit`
202101
- Improved logging in various locations
203102

204-
**Verified Retrieval**
205-
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:
206-
207-
```sh
208-
rngit release rns://7649a50d84610232d1416b41d2896aff/reticulum/reticulum fetch latest:all --signer bc7291552be7a58f361522990465165c
209-
```
210-
211-
To retrieve only the `.whl` package for installation, you can use:
212-
213-
```sh
214-
rngit release rns://7649a50d84610232d1416b41d2896aff/reticulum/reticulum fetch latest:rns-1.2.8-py3-none-any.whl --signer bc7291552be7a58f361522990465165c
215-
```
216-
217-
**Release Signatures**
218-
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:
219-
220-
```sh
221-
rnid -i bc7291552be7a58f361522990465165c -V manifest.rsm *.rsg
222-
```
223-
224-
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.
225-
226103
### 2026-05-18: RNS 1.2.8
227104

228105
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.
@@ -243,15 +120,6 @@ This release improves the `rngit` system with signed release manifest generation
243120
- Fixed various minor bugs and inconsistencies in `rngit`
244121
- Dropped `note` metadata field requirement from `rsg` structure
245122

246-
**Release Signatures**
247-
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:
248-
249-
```sh
250-
rnid -i bc7291552be7a58f361522990465165c -V manifest.rsm *.rsg
251-
```
252-
253-
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.
254-
255123
### 2026-05-17: RNS 1.2.7
256124

257125
This release significantly improves the `rngit` system with fork, mirroring and empty repository creation functionality, a new work document proposals feature, improvements to the transport core reliability and efficiency and various other tweaks and improvements.
@@ -269,15 +137,6 @@ This release significantly improves the `rngit` system with fork, mirroring and
269137
- Improved transfer completed feedback in `rncp`, thanks to **neutral**
270138
- Improved interface transport insertion and removal
271139

272-
**Release Signatures**
273-
Release artifacts include `rsg` signature files that can be validated against the RNS release signing identity `<bc7291552be7a58f361522990465165c>` using `rnid`. To verify files, download the `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:
274-
275-
```sh
276-
rnid -i bc7291552be7a58f361522990465165c -V rns*.whl
277-
```
278-
279-
The `rnid` utility will then verify the signatures, and display whether it is valid. If the signature cannot be verified, the file has been tampered with and should be thrown very far away in a jiffy.
280-
281140
### 2026-05-14: RNS 1.2.6
282141

283142
This release adds further improvements to the `rnid` and `rngit` utilities, and includes several bugfixes and other improvements.
@@ -299,15 +158,6 @@ This release adds further improvements to the `rnid` and `rngit` utilities, and
299158
- Fixed potential race condition in interface discovery
300159
- Fixed `rngit` remote helper hanging on startup if no client config had been created previously, and RNS loglevel was configured at debug or higher
301160

302-
**Release Signatures**
303-
Release artifacts include `rsg` signature files that can be validated against the RNS release signing identity `<bc7291552be7a58f361522990465165c>` using `rnid`. To verify files, download the `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:
304-
305-
```sh
306-
rnid -i bc7291552be7a58f361522990465165c -V rns*.whl
307-
```
308-
309-
The `rnid` utility will then verify the signatures, and display whether it is valid. If the signature cannot be verified, the file has been tampered with and should be thrown very far away in a jiffy.
310-
311161
### 2026-05-09: RNS 1.2.5
312162

313163
This release brings substantial improvements to path request handling, and should significantly reduce overall network and local transport node processing loads. Path requests are now automatically ingress and egress limited per interface and sub-interface. Although the defaults are effective and sane, and should work right out of the box bring an end to practically all the PR and announce spam going on lately, the backend is fully configurable for both defaults and per interface, if you want to fiddle with the settings.
@@ -336,15 +186,6 @@ For all node ops out there, I'd recomment updating to this at some sort of semi-
336186
- Ensured canonical validation functions in `rngit`
337187
- Lots of other small fixes and stability improvements to `rngit`
338188

339-
**Release Signatures**
340-
Release artifacts include `rsg` signature files that can be validated against the RNS release signing identity `<bc7291552be7a58f361522990465165c>` using `rnid`. To verify files, download the `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:
341-
342-
```sh
343-
rnid -i bc7291552be7a58f361522990465165c -V rns-1.2.5-py3-none-any.whl
344-
```
345-
346-
The `rnid` utility will then verify the signatures, and display whether it is valid. If the signature cannot be verified, the file has been tampered with and should be thrown very far away in a jiffy.
347-
348189
### 2026-05-07: RNS 1.2.4
349190

350191
This release brings a complete rewrite and update to the `rnid` utility, which is now a lot more useful, and better at finding and saving identities. It also includes a bunch of other improvements, such as expanded `rngit` functionality, better transport performance and a few bugfixes. Enjoy!

0 commit comments

Comments
 (0)