Moving packages to new vender after renaming github account #9657
-
|
Hi, I am about to rename a GitHub organization, let's say from This is the outcome I want:
This is how I want to approach it:
Expected problems:
Is there anything else that I have missed for this change? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 3 replies
-
I don't think there is a a way to avoid that if you simply rename the repository on github instead of creating a new one in which you don't push tags. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, that's what I feared. We will do as you suggest regarding a major upgrade for renamed classes and maybe a minor release under the old name where we already provide the new class names via alias. |
Beta Was this translation helpful? Give feedback.
-
|
I think we found a feasible workaround for us, so that the old vendor will not get updates for new releases anymore. We will create a new repo called It looks like having the old releases under the new vendor is ok for now. If we have to remove them, we would need to change the git history which is something we want to avoid to not mess with users depending on it. |
Beta Was this translation helpful? Give feedback.
-
|
Yup that's the only way to prevent new releases showing up. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the feedback. 👍 And actually this approach works quite well and is not hard to set up. |
Beta Was this translation helpful? Give feedback.
I don't think there is a a way to avoid that if you simply rename the repository on github instead of creating a new one in which you don't push tags.
My suggestion for that would be to bump the major version number for packages in which you rename the classes.