Heptapod 0.13.1 released

Posted on Thu 11 June 2020 in announcements

We're happy to announce the release of Heptapod 0.13.1.

This version brings in important internal changes that solve several long standing issues, and features a new technology preview, in preparation for Heptapod 0.14.

The full changelog is available as usual with the sources

Heptapod 0.13.1 features a major refactoring of the way the main web application is notified of Mercurial changes. Not only does this solve a whole category of issues, but also it does prepare for the future fully native Mercurial support (see the roadmap page for more about this).

Heptapod 0.13.1 also sports an optional rewrite of the SSH support in the Go programming language, which is the second technology preview that was planned for the 0.13 series (see below how to activate it). This solves the main blocker to base Heptapod on the currently supported GitLab 12.10.

Heptapod 0.13.1 can be installed in Python 2 and Python 3 flavours as a Docker image and from source.

The public instances managed by Octobus and Clever Cloud, foss.heptapod.net and heptapod.host are already running Heptapod 0.13.1.

Please test with Python 3 and SSH support in Golang if you can, and don't hesitate to give us feedback on our communication channels, it would be appreciated.

SSH support: how to activate the Go language implementation

First of all, thank you for wanting to give this technology preview a try! This will help us test in advance what will become the standard in future releases.

The case of source installations is treated in the install instructions

Here is the configuration for Docker installations:

### Migration to Go feature flags
###! Docs: https://gitlab.com/gitlab-org/gitlab-shell#migration-to-go-feature-flags
gitlab_shell['migration'] = { enabled: true, features: ["hg"] }

You can put it in /etc/gitlab/gitlab.rb and run gitlab-ctl reconfigure. No service restart is required.

Alternatively, you can put it in the the GITLAB_OMNIBUS_CONFIG environment variable for the whole container. In that case, restarting the container will activate it.

This new optional feature being completely stateless, there is no problem to switch it back off if needed.