Skip to content

wallowa changelog

Here are the releases for wallowa.

WARNING

The project will follow semver 2.0 once wallowa reaches v1.0.

For now there will probably be breaking changes in minor versions but we'll do what we can to minimize and mitigate them.

DANGER

The DuckDB internal storage format is not yet stable.

Follow these steps before upgrading wallowa until DuckDB storage format stability is reached.

v0.3.0 on September 21, 2023

Wallowa v0.3.0 to use a Docker image for distribution. The image is available as gunrein/wallowa on Docker Hub.

To run this version use the command:

sh
docker run -v .:/usr/wallowa:rw -p 127.0.0.1:9843:9843 --platform linux/amd64 gunrein/wallowa:0.3.0`

This version uses DuckDB v0.8.1 (the same version as Wallowa v0.2).

Changes

  • Use a Docker image for distribution
  • Use a GitHub Action to automatically build a new Docker image for the release when a new Git tag is pushed to GitHub

Known issues

  • Background data fetching in the server has a concurrency issue. During a fetch charts and other display elements that require data from the database will be slow to respond.

v0.2.0 on September 18, 2023

Wallowa v0.2.0 adds a chart for the ​count of closed GitHub Pull Requests by repo​, improves messages when fetching, and fixes a bug.

Thanks to @NoriSte for contributing PR #14!

This version uses DuckDB v0.8.1 (the same version as Wallowa v0.1).

The only prebuilt binary for this version is for MacOS on ARM.

Download v0.2.0

Changes

Known issues

  • Background data fetching in the server has a concurrency issue. During a fetch charts and other display elements that require data from the database will be slow to respond.

v0.1.0 on September 6, 2023

The initial version of wallowa. This version uses DuckDB v0.8.1.

The only prebuilt binary for this version is for MacOS on ARM.

Download v0.1.0

Changes

Known issues

  • Background data fetching in the server has a concurrency issue. During a fetch charts and other display elements that require data from the database will be slow to respond.