Skip to content

Update SimSpread.jl repository URL#145696

Merged
DilumAluthge merged 1 commit intoJuliaRegistries:masterfrom
cvigilv:simspread-ownership-transfered
Jan 29, 2026
Merged

Update SimSpread.jl repository URL#145696
DilumAluthge merged 1 commit intoJuliaRegistries:masterfrom
cvigilv:simspread-ownership-transfered

Conversation

@cvigilv
Copy link
Contributor

@cvigilv cvigilv commented Jan 7, 2026

This PR updates the URL for the package SimSpread.jl because ownership was transferred to an organization.

github.com/cvigilv/SimSpread.jl to github.com/schuellerlab/SimSpread.jl

@cvigilv cvigilv changed the title Modify repo URL due to ownership transfer Update SimSpread.jl repository URL Jan 7, 2026
Copy link
Member

@DilumAluthge DilumAluthge left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. I verified that the old URL automatically redirects to the new URL in the browser.
  2. The PR preserves the trailing .git.
  3. The GitHub username of the author of this PR is the same as the GitHub username that owned the repo in the old URL.

Copy link
Member

@DilumAluthge DilumAluthge left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Uh oh. The treecheck is failing.

@cvigilv It looks like the new URL does not contain all of the same treehashes.

@DilumAluthge DilumAluthge force-pushed the simspread-ownership-transfered branch from 74c0121 to 457ced4 Compare January 14, 2026 18:21
@DilumAluthge
Copy link
Member

Specifically, it looks like treehash 28da8c8721266b5dfba926a66f609b8fb9337940 is missing, which looks like version 1.0.2.

["1.0.2"]
git-tree-sha1 = "28da8c8721266b5dfba926a66f609b8fb9337940"
["1.0.3"]
git-tree-sha1 = "9f4d8e3032e4d14e7f08ea5e18760d0b7cbcac57"
["1.1.0"]
git-tree-sha1 = "a6a836683789f73c486ed4bf9caf3fe1ae198196"

@cvigilv
Copy link
Contributor Author

cvigilv commented Jan 17, 2026

Hi! Sorry for the radio silence. I'll check it on Monday. Thanks for the heads-up.

@cvigilv
Copy link
Contributor Author

cvigilv commented Jan 17, 2026

I'm a little lost on what I should do. Could you guide me a little?
First time doing this, followed the steps found in the documentation's FAQ.

@DilumAluthge
Copy link
Member

Is there a commit in your repo that corresponds to version 1.0.2?

@cvigilv
Copy link
Contributor Author

cvigilv commented Jan 20, 2026

No, I had problem whenever I released the package and bumped the minor version 3 times until it got released, so 1.0.3 is the "first" registered version of the package

@DilumAluthge
Copy link
Member

I'm looking back at the initial registration PR (#94323), and I think I've uncovered a bug in Registrator.jl, which I think is responsible for the problem we're seeing now.

So, if I understand correctly, the problem is not anything on your end, but rather a problem in the Registrator.jl package. I'll look into this further, and I'll try to figure out: (1) how to fix your specific situation in this PR, (2) how to fix Registrator.jl to fix the underlying bug, and (3) how to teach AutoMerge to catch this kind of problem in the future.

I do apologize - it might take a little while for me to figure out how to fix things here.

@cvigilv
Copy link
Contributor Author

cvigilv commented Jan 22, 2026

Don't worry! No rush on this, getting transferred to be honest. Just let me know if you need anything from my side.

@DilumAluthge
Copy link
Member

@cvigilv With Gunnar's help, we've been able to recover the contents of version 1.0.2. That version doesn't actually seem to be useful (or even installable), but given that it is listed in the registry, we should re-add it to your repo.

Can you complete the following steps, inside a clone of your repo?

# Step 1: Fetch the commit from Dilum's fork:
git fetch https://github.com/DilumAluthge-forks/SimSpread.jl.git 71cc70f2230af9f5fcd20c6a17c424716f4a3806

# Step 2: Create a branch named `release-1.0.2` locally:
git branch release-1.0.2 71cc70f2230af9f5fcd20c6a17c424716f4a3806

# Step 3: Create a tag named `v1.0.2` locally:
git tag v1.0.2 71cc70f2230af9f5fcd20c6a17c424716f4a3806

# Step 4: Push the branch:
git push origin release-1.0.2

# Step 5: Push the tag:
git push origin v1.0.2

Those steps should restore the content of v1.0.2 in your repo. Let me know if you have any questions!

@DilumAluthge
Copy link
Member

Bump @cvigilv

@cvigilv
Copy link
Contributor Author

cvigilv commented Jan 29, 2026

Sorry for the delay; it should be done. Let me know if you need anything else from my side

@DilumAluthge DilumAluthge force-pushed the simspread-ownership-transfered branch from 457ced4 to 8731953 Compare January 29, 2026 17:00
Copy link
Member

@DilumAluthge DilumAluthge left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Treecheck CI is green now.

See #145696 (review) for other manual checks that were performed.

@DilumAluthge DilumAluthge merged commit 3e2c360 into JuliaRegistries:master Jan 29, 2026
14 checks passed
@DilumAluthge
Copy link
Member

@cvigilv Thanks for your patience.

@cvigilv
Copy link
Contributor Author

cvigilv commented Jan 29, 2026

No problem! Thanks for the help!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants