Moving a package to new repository

I am trying to move my a package to a new repo. I sent a PR and after an identity confirmation step I was told that I “need to make all of the existing treehashes available in the new repo.” I have no clue what it means. I’m guessing I need to include fragments like this example in my project.toml:

[[deps.Packagename]]
deps = [ ]
git-tree-sha1 = “a07df0937c4b4c4d55a4a2b807c5addaf8d6e3bb”
uuid = “89d1cb86-bdfb-46ce-bf84-ab7f830013b1”
version = “0.x.0”

Can anyone give me a hand with this question?
Thanks!

No, it means that the “new” repository needs to contain a history that contains the previously registered versions. Ideally it’s not really a new repository at all — it should just be the same repository at a new location.

A package repository isn’t just its latest version, it also is the reference point for all previously registered versions, too.

Thank you, it makes sense. I got the “git-tree-sha / uuid / version” for all previous versions. I am guessing that is what is being required, but i I am not sure how I must include that data in PR. Is it the manifest? By the way it is about a Julia package.

No, it’s the git history in the repository itself. You can’t just plop the current state of the files in the repo with a brand new commit, you need the repository to contain the contents of all the prior registered versions, too.

Note that the process to transfer a repository to another organisation or user is documented in the README of the General registry