Florian Preinstorfer 44456497b0 Add versioned documentation ...

Setup mike to provide versioned builds of the documentation.

The goal is to have versioned docs for stable releases (0.23.0, 0.24.0)
and development docs that can progress along with the code. This allows
us to tailor docs to the next upcoming version as we no longer need to
care about diversion between rendered docs and the latest release.

Versions:
* development (alias: unstable) on each push to the main branch
* MAJOR.MINOR.PATCH (alias: stable, latest for the newest version)
  * for each "final" release tag
  * for each push to doc maintenance branches: doc/MAJOR.MINOR.PATCH

The default version should the current stable version. The doc
maintenance branches may be used to update the version specific
documentation when issues arise after a release.

2024-12-02 16:51:50 +01:00

..

build.yml

update gh workflow actions (#1809)

2024-03-13 13:43:06 +01:00

check-tests.yaml

update gh workflow actions (#1809)

2024-03-13 13:43:06 +01:00

docs-deploy.yml

Add versioned documentation

2024-12-02 16:51:50 +01:00

docs-test.yml

Bump deprecated github actions

2024-11-27 09:52:08 +01:00

gh-actions-updater.yaml

update gh workflow actions (#1809)

2024-03-13 13:43:06 +01:00

lint.yml

actually lint file on CI (#2018)

2024-09-05 13:37:05 +02:00

release.yml

update gh workflow actions (#1809)

2024-03-13 13:43:06 +01:00

stale.yml

add no stalebot exception (#2107)

2024-09-05 14:00:36 +02:00

test-integration.yaml

wrap policy in policy manager interface (#2255)

2024-11-26 15:16:06 +01:00

test.yml

fix route table migration wiping routes 0.22 -> 0.23 (#2076)

2024-08-27 18:54:28 +02:00

update-flake.yml

update gh workflow actions (#1809)

2024-03-13 13:43:06 +01:00