Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • heptapod heptapod
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 190
    • Issues 190
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

April 05-07 - Mercurial Paris Conference 2023 - One day of workshop dedicated to Heptapod and Mercurial usage and workflow. There are still places available for both workshops and talks!

  • heptapodheptapod
  • heptapodheptapod
  • Issues
  • #242
Closed
Open
Issue created Apr 09, 2020 by Pierre-Yves David@marmoute🐙Maintainer

upgrade to evolve 9.3.1

Evolve 9.3.1 (and topic 0.18.1) got released yesterday. They code with two server side fixes importasnt for heptapod.

  • first, change to the topic extensions so that the experimental.auto-publish=abort works properly with the publishing mode we use for heptapod. If the option is set, pushing changeset without topic will requires an explicit --publish client side. no extra configuration needed, just upgrade. I don't think you use experimental.auto-publish=abort in your test so I don't expect anything to break (but you might want to add a test for it).

  • second, the enforcement for a single head for each name now ignored obsolete section of the graph. In short, this means that obsolete heads will not longer be counter a extra heads, so we can rewrite a topic without having to also evolve topic depending on it. However the way it is currently implemented means the reste of mercurial still see the obsolete heads as a heads. So I expect your export code to possibly get confused when this situation arise. Get in touch with me if you need help to update your export code. The code use in evolve to prune the obsolete section of the graph could be reused for that.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking