wallowa v0.3.0

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:

docker run -v .:/usr/wallowa:rw -p 127.0.0.1:9843:9843 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.

wallowa v0.2.0

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 pre-built binary for this version is for MacOS on ARM.

Download v0.2.0

Changes

• Fixed an incorrect https URL in the get started content and CLI. Thanks to @NoriSte for PR #14.
• Added a new chart for the count of closed GitHub Pull Requests by repo
• Added the count of closed GitHub Pull Requests by repo chart to the dashboard
• Improved messages for CLI fetch when requests are made and when errors occur on the GitHub API fail
• Show error message when a fetch fails in the sources web UI

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.

wallowa v0.1.0

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

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

See the changelog documentation for warnings about version stability and upgrades.

Changes

• CLI (command line interface) with fetch, new, serve, and help commands
• Web UI with a dashboard, GitHub Pull Request duration chart, and index of sources
• Server to host the web UI
• Documentation

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.