epicweb-dev/cachified

move into epicweb-dev?

Xiphe opened this issue ยท 10 comments

Hi @kentcdodds,

Long term I'm looking to step down from maintaining open source projects for various personal reaons.

So I wanted to ask what you think about moving this into the @epicweb-dev org?

For now I'd happily continue maintaining this in either space but I'd appreciate if there would be some more potential maintainers.

I completely understand and I'll be happy to move it into the epic web org and publish it under the epic web npm namespace as well. If that sounds ok to you then I'll get things ready to go for that transition.

sounds great! Let's do this ๐Ÿ‘

Could you give me admin rights so I can transfer this into the Epic Web org and update the actions?

Wasn't able to grand you admin rights while this was on my personal account. Also wasn't able to move it into @epicweb-dev because I'm not allowed to create public repos in there. Therefore moved into @kalispera for now and you have admin rights now.
Let me know if this works :)

Alright! We're almost finished. All you need to do now is publish a major version to cachified and then deprecate it. This way people can continue to use v3 of cachified without incident, but anyone who's setting up cachified for the first time (or upgrading) will be notified that it's been moved.

I've tried to make the process as simple as possible. Here's what you need to do.

  1. Login to your npm account locally in the terminal
  2. Clone the move-v4 branch I prepared for you
  3. npm publish (will publish v4 based on what's in the package.json)
  4. npm deprecate v4 with a nice message

Here's something you should be able to copy/paste:

git clone git@github.com:epicweb-dev/cachified.git
cd ./cachified
git checkout move-v4
npm publish
npm deprecate cachified@">=4.0.0" "cachified has been moved to @epic-web/cachified with no breaking changes. Please uninstall cachified and install @epic-web/cachified instead then update all your imports. Learn more at: https://github.com/epicweb-dev/cachified/issues/74"

I've done things this way before and it strikes the best balance of not annoying people who are happy with their current version of the package but also incrementally migrating people over to the new one. Let me know if you have any questions!

Done! Thanks a lot for the help with this ๐Ÿ‘

This went faster and smoother then expected ๐Ÿคฉ
I'll still be around, continue to watch this space and will happily continue to collaborate on the tool.

Have a wonderful day โ˜€๏ธ

Thanks!

I just checked https://npm.im/cachified and I see v4 was published, but it doesn't look like it was deprecated. Did you run that command?

Ah, seems as if that hasn't run through correctly. Thanks for double-checking ๐Ÿ™ It's done now

image

Thanks! That went well ๐Ÿ‘