Auto: Rename npm package from "auto-release-cli" to just "auto"
I just got control of the npm package name "auto" so think we are gonna switch over to that. This will make npx a little cleaner and make it easier to install.
I will probably do this this weekend.
Any thoughts? @adierkens @orta @zephraph
TODO:
- [ ] rename github project
- [ ] change the pacakge.json github repo
- [ ] deprecate "auto-release-cli" on npm
- [ ] change logo
- [ ] update getting started
- [ ] replace all instances of "auto-release" to "auto" in code and docs
hipstersmoothie
All 11 comments
do it, we just moved most of our auto usage to one place anyway. It's totally net positive IMO.
https://github.com/artsy/orbs/blob/master/src/yarn/yarn.yml#L128-L132
orta
on 17 Jan 2019
That line is actually what prompted me to contact the previous owner of "auto"!
hipstersmoothie
on 17 Jan 2019
Yep, I’m all for it 👍
Sent with GitHawk
zephraph
on 17 Jan 2019
👍
Should we go all out and rename the repo and stuff too?
nevermind, just actually read your post :shipit:
adierkens
on 17 Jan 2019
Out of curiosity, would renaming the package be a major version bump?
Doesn't look like the original auto ever published a 1.0. Do we start over at 1.0? 🤷♀️
adierkens
on 17 Jan 2019
That is a good question. IDK really. Let's vote 😄
hipstersmoothie
on 17 Jan 2019
hipstersmoothie
on 17 Jan 2019
I don't know that it matters too much
Sent with GitHawk
zephraph
on 17 Jan 2019
After sleeping on it we can't go back to 1.0.0 because we would get tag conflicts. So I think major is the best going forward
hipstersmoothie
on 17 Jan 2019
Sure, major seems reasonable then to me
orta
on 17 Jan 2019
Yep, I came to that same conclusion after thinking about it a bit. Going back in versions would make github releases all whack.
zephraph
on 19 Jan 2019
Related issues
vincentbriglia
·
8Comments
zephraph
·
12Comments
glambert
·
4Comments
shilman
·
7Comments
reintroducing
·
15Comments