Anyone arriving here getting this message:
Running:
snap refresh --channel=latest/beta dvc (to upgrade now), orsnap refresh --channel=v0/stable dvc (to never upgrade)
makes the message go away.
Otherwise (if you ignore the message) you'll be upgraded from v0 to v1 automatically in a few days.
See https://dvc.org/blog/june-20-community-gems for some notes on upgrading to v1 (it's simple!)
Maintainer notes:
Snap packages automatically update to the most recent version in a channel.
The default channel is --latest/stable (with the slash, yes; not my design choice) and normally we push tagged releases to it.
During breaking transitions (v0 to v1), though, we need a transition phase.
After the transition period (say 30 days?) we go back to normalcy:
Some people will be be hit by errors at this stage, but serves them right for ignoring the transition warning messages we tried our best.
I'm not happy with the channel naming conventions either but such is life: https://snapcraft.io/docs/channels. In fact we have to manually request --v0, --v1 etc.
Anyone arriving here getting this message:
Running:
snap refresh --channel=latest/beta dvc(to upgrade now), orsnap refresh --channel=v0/stable dvc(to never upgrade)makes the message go away.
Otherwise (if you ignore the message) you'll be upgraded from
v0tov1automatically in a few days.See https://dvc.org/blog/june-20-community-gems for some notes on upgrading to v1 (it's simple!)
Maintainer notes:
Snap packages automatically update to the most recent version in a channel.
The default channel is
--latest/stable(with the slash, yes; not my design choice) and normally we push tagged releases to it.During breaking transitions (v0 to v1), though, we need a transition phase.
0.xto a new--v0/stablechannel1.xto--v1/betaand--latest/beta0.x-finalto--latest/stablesnap refresh --channel=v0/stableto stick to the old versionsnap refresh --channel=latest/beta& use new API/syntaxsnap refresh --channel=v1/beta& use new API/syntax. This would stop them getting warnings about--v2in future. Probably bizarre ("I wanna upgrade now but never again") and not worth mentioning this option.After the transition period (say 30 days?) we go back to normalcy:
--v1/betachannel. Users on it will automatically get shifted to--v1/stable.1.xupdates to--v1/stableand--latest/stableSome people will be be hit by errors at this stage, but
serves them right for ignoring the transition warning messageswe tried our best.I'm not happy with the channel naming conventions either but such is life: https://snapcraft.io/docs/channels. In fact we have to manually request
--v0,--v1etc.Please bump heredone: https://forum.snapcraft.io/t/track-request-for-dvc/17735v1andv0snap build improvements (e.g. snap: build fixes #3990, CI: fix Mac builds #4037)