3cbcc4a0ab
fix: Improve update script ( #27308 )
2025-05-04 14:43:22 +02:00
6e781eafae
fix(ignore): Make update check less verbose ( #26774 )
2025-03-17 20:43:56 +01:00
fb48bd0cb9
fix(ignore): Fix update check ( #26723 )
2025-03-15 08:09:55 +01:00
1b6ad46462
fix: Check if new commits are available in update.sh ( #26631 )
2025-03-08 14:14:25 +01:00
5e55ef0454
fix: Support FreeBSD for update.sh ( #26261 )
2025-02-09 14:50:36 +01:00
b6186623f0
feat!: The big cleanup ( #24200 )
...
* Remove `deviceGroupMembership`
* Fix controller.ts
* Remove `legacy_api` logic from non-legacy extensions.
* Fix network map coverage.
* Remove all `legacy` extensions.
* Remove `legacy_availability_payload`, `legacy_api`. Remove legacy from configure.
* Fix prettier.
* Remove some leftovers
* Renamed `updateAvailable` to `update_available`
* Remove emitPublishAvailability
* Remove `configuration.yaml`
* Switch to pnpm
* Remove direct mqtt-packet dependency.
* fix pretty
* fix `getDependencyVersion`
* fix pnpm publish
* fix(ignore): fix pnpm publish
* Remove deprecated bridge `config/*`
* Improve update script
* Improve update.sh
---------
Co-authored-by: Nerivec <62446222+Nerivec@users.noreply.github.com >
2024-12-01 20:06:49 +01:00
ee5cf5a901
chore: Improve update.sh ( #22395 )
...
Pulling without specifying how to reconcile divergent branches is discouraged and produces an ugly "hint" that can be a little disconcerting when running update.sh
2024-05-02 21:18:25 +02:00
8b694432aa
fix: Check if Zigbee2MQTT is running in update.sh ( #21494 )
2024-02-20 19:46:44 +01:00
346cb90e9e
fix: Make update script work from anywhere ( #19965 )
...
Makes update script work from anywhere changing the current directory to where the file is located.
2023-12-02 19:48:17 +01:00
311ea070b1
chore: Add build step to update script https://github.com/Koenkk/zigbee2mqtt/pull/19232
2023-11-14 20:16:40 +01:00
f224ef7b7c
chore: Improve update script in case of local changes ( #18837 )
...
* Stash local changes to prevent update failing
Call git stash to stash any local changes that would prevent the update.sh script from failing
* Update update.sh
changed to git checkout package-lock.json
2023-09-02 09:08:09 +02:00
d064a73131
Rework ci and use package-lock.json instead of npm-shrinkwrap.json ( #12631 )
...
* Update ci
* Use package-lock
* Use package-lock.json
* Use cache for ci
* Enable node18 windows
* Revert "Enable node18 windows"
This reverts commit e427551acdd64c3a256b48a5b8e86b3c4c986405.
* Remove redundant cache
* Don't do shrinkwrap
* Remove shrinkwrap
* Remove redundant step
* Cache node-gyp
* Debug
* Add key
* Update ci.yml
* Add cache detection
* Fix
* Add deps
* Fix2
* Update caches
* Fix ci
* Update patsh
* Update paths
* Update paths
* Fix max cache path
* Change cache key
* Remove spaces
* Split caches
* Fix linux cache
* Fix linux cache
* Merge caches
* Ignore errs
* Find only dirs
* Run find after ci
* Fix mac cache
* Fix caches
* Remove env run
Co-authored-by: nurikk <ainur@yojee.com >
2022-06-02 14:38:07 +00:00
cabef43421
Revert "Switch to package-lock.json"
...
This reverts commit 0163b7281a
2022-04-03 08:49:03 +02:00
0163b7281a
Switch to package-lock.json
2022-04-02 20:57:44 +02:00
db61a623d5
Allow non systemctl systems to use update.sh ( #8206 )
...
With this change update.sh works on systems that do not use systemctl.
I can update z2m on my illumos machine by running `svcadm disable zigbee2mqtt; ./update.sh ; svcadm enable zigbee2mqtt`
2021-08-02 09:38:08 +02:00
82f3d7d9bb
update.sh: add checking if data-backup exists ( #4793 )
2020-10-28 10:45:49 +01:00
9a6397fe75
Make Zigbee2MQTT naming consistent
2020-08-01 10:36:20 +02:00
eac15a748a
npm ci. https://github.com/Koenkk/zigbee2mqtt/issues/2918
2020-02-13 21:31:14 +01:00
e54de4bea7
Adding update script ( #525 )
...
* Adding update script
Fix #389
* Update update.sh :)
* Make executable & update update.sh
2018-10-22 18:08:03 +02:00
0xdefec71f