added 0.56 release notes

docs/manual/topo-def-file.md

@@ -156,7 +156,7 @@ topology:
 ###### Aliases
 
 The downside of using Linux interface names is that they often do not match the interface naming convention used by the Network OS. This is where Interface Aliases feature (added in Containerlab v0.56.0) comes in handy.
-
+<!-- --8<-- [start:aliases] -->
 Imagine we want to create a lab with four different Kinds: SR Linux, vEOS, CSR1000v and vSRX, cabled like this:
 
 |                A side | B side           |
@@ -197,6 +197,7 @@ Both topology definitions result in the same lab being deployed, but the latter
 Many [Kinds](../manual/kinds/index.md) (but not all) support interface aliases and the alias names are provided in the respective kind' documentation.
 
 Containerlab transparently maps from interface aliases to Linux interface names, and there's no additional syntax or configuration needed to specify either an interface alias or a Linux interface name in topologies.
+<!-- --8<-- [end:aliases] -->
 
 /// details | How do aliases work?
 Internally, interface aliases end up being deterministically mapped to Linux interface names, which conform to Linux interface naming standards: at most 15 characters, spaces and forward slashes (`/`) not permitted.

docs/rn/0.56.md

@@ -0,0 +1,46 @@
+# Release 0.56
+
+:material-calendar: 2024-07-09 · :material-list-status: [Full Changelog](https://github.com/srl-labs/containerlab/releases)
+
+## Interface aliases
+
+We know, it has been a long time coming, but thatnks to a brilliant contribution done by [@vista-](https://github.com/vista-) in #2124 we now have added support for [interface aliases](../manual/topo-def-file.md#interface-naming).
+
+What are interface aliases you ask? They are a way to use interface names as you see them in the NOS CLI, rather than the default `ethX` naming scheme. It is a convenience feature, but, oh boy, how much easier it is to define links when you don't have to keep doing this mental gymnastics of mapping `eth0` to `Gi0/1` and so on.
+
+--8<-- "docs/manual/topo-def-file.md:aliases"
+
+Interface aliases will be also displayed in the [generated graph](../cmd/graph.md#html) and even in the [edgeshark](../manual/wireshark.md#edgeshark-integration) web view.
+
+/// tab | Graph
+![pic1](https://gitlab.com/rdodin/pics/-/wikis/uploads/9ce9f8bd9ff7e4adfbe45c46712016b0/image.png){.img-shadow}
+///
+/// tab | Edgeshark
+![pic2](https://gitlab.com/rdodin/pics/-/wikis/uploads/3d4541b11a1b557967e419165aeb7ffd/image__2___1___1_.png){.img-shadow style=height:500px}
+///
+
+## Ostinato support
+
+We have added support for [Ostinato](https://ostinato.org/) traffic generator in containerlab. You can now define Ostinato nodes in your topology file and use them to generate traffic between your nodes.
+
+See the [Ostinato integration](../manual/kinds/ostinato.md) page for more details.
+
+## Sonic
+
+We have added support for the following new Sonic kinds:
+
+- [`sonic-vm`](../manual/kinds/sonic-vm.md) - is a VM-based upstream SONiC. You may want to pick sonic-vm over [sonic-vs](../manual/kinds/sonic-vs.md) if you hit some issues with the original sonic container #2120
+- [`dell_sonic`](../manual/kinds/dell_sonic.md) - is a SONiC distribution by Dell #2125
+
+## Multi-arch `clab` container build
+
+To support the imminent release of ARM64 friendly Network OSes we fine tuned the release pipeline to make sure the `clab` container is built for both `amd64` and `arm64` architectures. #2128
+
+## Cisco Catalyst 9000v
+
+Thanks to our strong community and @kaelemc in particular, we have added support for the [Cisco Catalyst 9000v](../manual/kinds/vr-cat9kv.md) router. #2133
+
+## Miscellaneous
+
+- Additions to the Developers Guide done by @pstavirs go about how to contribute to the documentation and how to build the documentation locally. #2109
+- Added more community posts in #2127

mkdocs.yml

@@ -137,6 +137,7 @@ nav:
           - 5-stage Clos topology: lab-examples/templated02.md
       - Generic VM: lab-examples/generic_vm01.md
   - Release notes:
+      - "0.56": rn/0.56.md
       - "0.55": rn/0.55.md
       - "0.54": rn/0.54.md
       - "0.53": rn/0.53.md