Skip to content

Commit f120bdc

Browse files
committed
Update changelog. Bump version.
1 parent 1bad769 commit f120bdc

File tree

2 files changed

+30
-1
lines changed

2 files changed

+30
-1
lines changed

docs/config.toml

+1-1
Original file line numberDiff line numberDiff line change
@@ -40,4 +40,4 @@ pygmentsUseClasses = true
4040
weight = 5
4141

4242
[params]
43-
version = "2.8.0"
43+
version = "3.0.0-test.1"

docs/content/overview/changelog.md

+29
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,34 @@ description: Lists the changes per LoRa Server release, including steps how to u
99
---
1010
# Changelog
1111

12+
## v3.0.0
13+
14+
### Features
15+
16+
### Improvements
17+
18+
#### Legacy code removed
19+
20+
Legacy code related to older gateway structures have been removed. All gateway
21+
messages are now based on the [Protobuf](https://github.com/brocaar/loraserver/blob/master/api/gw/gw.proto)
22+
messages.
23+
24+
#### MQTT topic refactor
25+
26+
Previously, each topic was configured separatly. To be consistent with
27+
LoRa Gateway Bridge v3, this has been re-factored into "events" and "commands".
28+
29+
### Upgrading
30+
31+
LoRa Server v3 depends on LoRa Gateway Bridge v3! It is recommended to upgrade to
32+
the latest LoRa Server v2 release (which is forwards compatible with the
33+
LoRa Gateway Bridge v3), upgrade all LoRa Gateway Bridge installations to v3
34+
and then upgrade LoRa Server to v3.
35+
36+
It is also recommended to update your LoRa Server configuration file.
37+
See [Configuration](https://www.loraserver.io/loraserver/install/config/) for
38+
more information.
39+
1240
## v2.8.0
1341

1442
### Features
@@ -55,6 +83,7 @@ with LoRa Gateway Bridge v2, but also provides compatibility with LoRa Gateway B
5583
Once LoRa Server v3 is released, it is recommended to first upgrade all LoRa
5684
Gateway Bridge instances to v3 and then upgrade LoRa Server to v3.
5785

86+
5887
## v2.7.0
5988

6089
### Improvements

0 commit comments

Comments
 (0)