upgrading to latest MM version

JMac

Finally getting round to updating the base MM version.

used @sdetweil bash -c “$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)”

and it did what it wanted to do.

How do I know that the second line bash -c “$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)” apply

can be run without issue?

I get this before it runs through all the package.json files for modules I’m using,

Check current Node installation …
Node currently installed. Checking version number.
Minimum Node version: v20.18.1
Installed Node version: v20.8.0
Node should be upgraded.
Node.js upgrade defered, doing test run
Check current NPM installation …
NPM currently installed. Checking version number.
Minimum npm version: V10.8.2
Installed npm version: V10.1.0
npm should be upgraded.
npm upgrade defered, doing test run …

is it safe at this point to use the code to make the changes?
Cheers,
John.

JMac

@sdetweil restarted the MM with PM2, still no info being displayed in the CalendarEXT3 module.

edit to add, after letting the mirror settle down, it’s now pulling the data

sdetweil

@JMac yes, run the apply version

things will be ok

always backup first

https://github.com/sdetweil/MagicMirror-backup-restore

JMac

out of curiosity, what would I do if I needed to retrieve the back up, do I need a GitHub account?

sdetweil

@JMac it depends on what you want to do
if you are just upgrading MM and don’t expect any sd card or OS issues
– no ‘need’ to copy
otherwise
– at minimum you can copy the ~/MM-backup folder to some other media

if you want you can use a githib PRIVATE repo for that
(private only because it contains private info)
its free, just takes a login and create a repo

then use the repo name in the backup
(git will prompt for the password, not my code)

by using git and github, i also version the backup too(using git tags)
so todays may be different than yesterday or last week…
you can restore ANY of those…
(and you didn’t lose a usb stick, or sd card… or whatever)
(AND you can tell the difference between versions)

the MM source is also tagged (git term for labeled) at each release,
so we can get bback there pretty easily

sdetweil

@JMac to restore, you run the restore script . it takes parameters to tell it what to do

JMac

@sdetweil This is useful to know.

Just add, I’ve had the same Issue as the last MM update, Calendar EXT3 is no longer pulling information from the base calendar module.

sdetweil

@JMac did you put on the fix

see https://forum.magicmirror.builders/topic/19282/version-2-30-0-calendar-fix-for-clipping-broadcast-events

JMac

@sdetweil I hadn’t seen that, I was about to update the module individually then do some digging on here to see if others had had the issue.

do I use the list of commands in the link above, or the ones in this link?
https://forum.magicmirror.builders/topic/14327/testing-new-fixes-or-solving-current-problems-with-next-release-code

JMac

@sdetweil I’ve hit this at the 3 command,
MagicMirror@raspberrypi:~/MagicMirror $ git switch _fix_clipping
error: Your local changes to the following files would be overwritten by checkout:
package-lock.json
Please commit your changes or stash them before you switch branches.
Aborting

sdetweil

@JMac rm package-lock.json