-
Notifications
You must be signed in to change notification settings - Fork 431
fix(updater): format Update.date
to RFC 3339
#2573
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(updater): format Update.date
to RFC 3339
#2573
Conversation
Package Changes Through 20e5d33There are 10 changes which include autostart with minor, autostart-js with minor, http with patch, http-js with patch, deep-link with patch, deep-link-js with patch, fs with patch, fs-js with patch, updater with minor, updater-js with minor Planned Package VersionsThe following package releases are the planned based on the context of changes in this pull request.
Add another change file through the GitHub UI by following this link. Read about change files or the docs at github.com/jbolda/covector |
Didn't test it locally yet, will mark as ready then Tested, seems to work |
* fix(updater): format `Update.date` to RFC 3339 * Messed up on argument in tauri-apps#2572 * Format * Update example * Avoid extra to_string * Deprecate `Update.available`
check core plugin versions for incompatibilities between Cargo and NPM releases a plugin NPM/cargo version is considered "incompatible" if their major or minor versions are not equal on dev we show an warning on build we error out (with a `--ignore-incompatible-plugins` flag to prevent that) this is an idea from @oscartbeaumont we've seen several plugin changes that require updates for both the cargo and the NPM releases of a plugin, and if they are not in sync, the functionality does not work e.g. tauri-apps/plugins-workspace#2573 where the change actually breaks the app updater if you miss the NPM update
* feat(cli): check plugin versions for incompatibilities check core plugin versions for incompatibilities between Cargo and NPM releases a plugin NPM/cargo version is considered "incompatible" if their major or minor versions are not equal on dev we show an warning on build we error out (with a `--ignore-incompatible-plugins` flag to prevent that) this is an idea from @oscartbeaumont we've seen several plugin changes that require updates for both the cargo and the NPM releases of a plugin, and if they are not in sync, the functionality does not work e.g. tauri-apps/plugins-workspace#2573 where the change actually breaks the app updater if you miss the NPM update * Use list to get multiple package versions at once * Fix for older rust versions * Clippy * Support yarn classic * Support yarn berry * Use `.cmd` only for `npm`, `yarn`, `pnpm` * Use yarn list without --pattern * rename * Extract function `check_incompatible_packages` * Check `tauri` <-> `@tauri-apps/api` * incompatible -> mismatched * run build check in parallel * rename struct * Switch back to use sync check and add todo * Extract to function `cargo_manifest_and_lock` --------- Co-authored-by: Tony <[email protected]>
Closes #2416
Closes #2417
Also aligned
check
's return to match the js side's structure