1. 05 Sep, 2022 2 commits
  2. 08 Jul, 2022 1 commit
  3. 20 Jun, 2022 6 commits
  4. 12 Jun, 2022 2 commits
  5. 31 May, 2022 1 commit
  6. 16 May, 2022 2 commits
  7. 05 Apr, 2022 2 commits
    • Georges Racinet's avatar
      heptapod#658: making 0.30 the new stable · d7d8861fa34f
      Georges Racinet authored
      d7d8861fa34f
    • Georges Racinet's avatar
      hg-git: require version < 1.0 · d4d1761f95ba
      Georges Racinet authored
      The publication of the final 1.0.0 version of hg-git brings
      in a minor incompatibility, that we will address once the
      current default branch becomes the stable branch (heptapod#658).
      
      This is not a problem for shipped versions because the requirements
      specified with the Rails app (both in heptapod and in release branch)
      already pin hg-git to 0.10.x
      d4d1761f95ba
  8. 14 Mar, 2022 2 commits
  9. 05 Feb, 2022 1 commit
    • Georges Racinet's avatar
      Stop post-processing branchmap entries for obsolescence · c78aee1fe363
      Georges Racinet authored
      With the Mercurial 6.1 (core see heptapod#633) taking obsolescence
      into account while updating branchmap, it is no longer necessary
      to perform the (very slow) post-processing provided by the evolve
      extension.
      
      Because of the big jump in minimum required Mercurial version,
      we make it a major version change.
      
      Fixing heptapod#632 will thus boil down to requiring
      py-heptapod>=4.0.0dev0
      
      This post-processing was the standard if evolve is activated
      (through the single heads enforcement logic),
      but the heptapod extension was (and still is) disabling it because
      it needs to call it itself anyway.
      See 834eb9379d73 for details.
      c78aee1fe363
  10. 26 Feb, 2022 3 commits
  11. 25 Jan, 2022 1 commit
  12. 23 Jan, 2022 1 commit
  13. 03 Jan, 2022 5 commits
  14. 02 Jan, 2022 1 commit
  15. 26 Nov, 2021 1 commit
  16. 15 Nov, 2021 5 commits
  17. 13 Nov, 2021 1 commit
    • Georges Racinet's avatar
      GitLab hooks: removed annoying and misleading failure message · 0db46e66b9fd
      Georges Racinet authored
      The original wording was appropriate when the pre-receive call was
      done actually after the transaction. It was then useful to warn the
      user of a possible decrepancy. But an error in pre-receive has long
      since become a trigger for transaction abort.
      
      On the other hand, the original message was still appropriate for
      the post-receive call, expanding it a bit to include "actions" not
      triggered.
      0db46e66b9fd
  18. 11 Nov, 2021 1 commit
  19. 10 Nov, 2021 1 commit
  20. 03 Nov, 2021 1 commit