- Jul 05, 2024
-
-
Georges Racinet authored
It is far more intrusive than I thought, breaking some features in HGitaly for all repositories, which would force us to disable it entirely in HGitaly startup, with a result that is actually worse since *that* breaks all operation on repos with the `largefiles` requirement. Policy should be to activate it on a per-project basis, where *some* broken features are acceptable.
-
- Jul 04, 2024
-
-
Georges Racinet authored
-
Georges Racinet authored
-
Georges Racinet authored
With the upcoming minimal fix for heptapod#1224, there will be no reason that repositories using `largfiles` should not be pushed to Heptapod.
-
- Jun 09, 2024
-
-
Georges Racinet authored
-
Georges Racinet authored
-
Georges Racinet authored
-
- May 28, 2024
-
-
Georges Racinet authored
Does not affect main code at all.
-
- May 24, 2024
-
-
Georges Racinet authored
-
Georges Racinet authored
-
Georges Racinet authored
-
- May 23, 2024
-
-
Georges Racinet authored
Version 2.32.0 is not compatible with requests-unixsocket (invalid scheme 'unix+http'). We will investigate, yet not in this branch.
-
- May 20, 2024
-
-
Georges Racinet authored
-
- May 08, 2024
-
-
Georges Racinet authored
-
Georges Racinet authored
-
Georges Racinet authored
-
- May 07, 2024
-
-
Georges Racinet authored
GitLab default branch: new logs to investigate problems See merge request !101
-
Georges Racinet authored
We keep getting reports that on some projects the default GitLab branch gets overwritten to point to a topic (heptapod#714), which is obviously very wrong. It is not clear how this really happens, perhaps these new logs will help. The case of `None` creeping in was reported by Alphare in the matrix channel. He stumbled upon it while releasing Mercurial 6.7.3
-
Georges Racinet authored
Long ago, we had to restrict to `coverage<6`. However, these days, on Python 3.11, the converse is happening: we have to update it manually to get significant results (should have been done earlier).
-
- May 01, 2024
-
-
Georges Racinet authored
-
Georges Racinet authored
-
Georges Racinet authored
Support for Mercurial 6.7 is well worth a new minor version
-
Georges Racinet authored
-
- Apr 19, 2024
-
-
Georges Racinet authored
Part of heptapod#1494. Merging the default branch was not enough, since the restriction of Mercurial to `<6.7` was done in the stable branch only. Removing it is necessary in CI because the `hg-current` image now has 6.7.2. Of course 6.7 will become the standard version in Heptapod 1.5 anyway.
-
- Apr 03, 2024
-
-
Georges Racinet authored
-
- Apr 02, 2024
-
-
Georges Racinet authored
This is a version officially supporting Mercurial 6.7, even though our tests were already passing on hg-git 1.0.x
-
- Feb 29, 2024
-
-
Georges Racinet authored
This solves a problem on our side. We can't see much more because everything is masked by the `topic` extension not being compatible anyway (phases internal API)
-
- Mar 26, 2024
-
-
Georges Racinet authored
-
- Mar 20, 2024
-
-
Georges Racinet authored
-
Georges Racinet authored
-
Georges Racinet authored
The fact that the server will now accept pulls for obsolete changesets is worth a minor version bump
-
Georges Racinet authored
The diff is empty, but now Mercurial knows it's fully merged.
-
Georges Racinet authored
-
- Mar 19, 2024
-
-
Georges Racinet authored
See heptapod#705
-
- Mar 14, 2024
-
-
Georges Racinet authored
-
- Mar 12, 2024
-
-
Georges Racinet authored
-
- Feb 14, 2024
-
-
Georges Racinet authored
-
- Feb 13, 2024
-
-
Georges Racinet authored
-
Georges Racinet authored
-
Georges Racinet authored
-