@reilley I just did the git pull on my installation
git pull
remote: Enumerating objects: 58, done.
remote: Counting objects: 100% (36/36), done.
remote: Compressing objects: 100% (14/14), done.
remote: Total 58 (delta 25), reused 27 (delta 22), pack-reused 22 (from 1)
Unpacking objects: 100% (58/58), 205.78 KiB | 1.34 MiB/s, done.
From https://github.com/randomBrainstormer/MMM-GoogleCalendar
8679522..faf438e main -> origin/main
* [new tag] v1.2.7 -> v1.2.7
* [new tag] v1.2.5 -> v1.2.5
* [new tag] v1.2.6 -> v1.2.6
Updating 8679522..faf438e
Fast-forward
.github/workflows/version-bump.yml | 55 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
MMM-GoogleCalendar.js | 108 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++----
__tests__/MMM-GoogleCalendar.test.js | 102 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
node_helper.js | 49 +++++++++++++++++++++++++++++++++++++++++++++++--
package-lock.json | 4 ++--
package.json | 2 +-
translations/en.json | 3 ++-
7 files changed, 313 insertions(+), 10 deletions(-)
create mode 100644 .github/workflows/version-bump.yml
sam@sams:~/MagicMirror.2.36.dev/modules/MMM-GoogleCalendar$ npm install
up to date, audited 383 packages in 2s
65 packages are looking for funding
run `npm fund` for details
12 vulnerabilities (8 moderate, 4 high)
To address issues that do not require attention, run:
npm audit fix
To address all issues (including breaking changes), run:
npm audit fix --force
Run `npm audit` for details.
and updatenotification does not report being behind