Skip to content

fix(updater): use msiexec to install .msi updates#1454

Merged
amrbashir merged 3 commits into
v2from
fix/updater/msi
Jun 12, 2024
Merged

fix(updater): use msiexec to install .msi updates#1454
amrbashir merged 3 commits into
v2from
fix/updater/msi

Conversation

@amrbashir
Copy link
Copy Markdown
Member

@amrbashir amrbashir commented Jun 11, 2024

closes #1449

@amrbashir amrbashir requested a review from a team as a code owner June 11, 2024 17:16
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 11, 2024

Package Changes Through 2d8e89f

There are 6 changes which include notification with prerelease, deep-link-js with prerelease, http with prerelease, http-js with prerelease, sql with prerelease, updater with prerelease

Planned Package Versions

The following package releases are the planned based on the context of changes in this pull request.

package current next
api-example 2.0.0-beta.10 2.0.0-beta.11
api-example-js 2.0.0-beta.8 2.0.0-beta.9
deep-link-example-js 2.0.0-beta.6 2.0.0-beta.7
deep-link-js 2.0.0-beta.6 2.0.0-beta.7
http 2.0.0-beta.9 2.0.0-beta.10
http-js 2.0.0-beta.5 2.0.0-beta.6
notification 2.0.0-beta.7 2.0.0-beta.8
sql 2.0.0-beta.6 2.0.0-beta.7
updater 2.0.0-beta.7 2.0.0-beta.8

Add another change file through the GitHub UI by following this link.


Read about change files or the docs at github.com/jbolda/covector

@FabianLars
Copy link
Copy Markdown
Member

One thing i just noticed because of your nsis_installer_args change is that we never ported the std::env::args change to the v2 msi updater. Maybe we can use a public property for that to tell the msi about them (doesn't have to be this pr). On that note, can it even restart the app right now? We've used powershell for that in the past. Just on my phone rn so didn't test anything (including this pr)

@amrbashir
Copy link
Copy Markdown
Member Author

amrbashir commented Jun 12, 2024

The restart thing (and consecutively the current args) and the upgrade using TaskScheduler, were removed because we don't use powershell anymore. This is out of this PR scope, so I'd rather discuss this on Discord or in another issue but the generated installer should have a flag or something that could be used to launch the application afterwards.

I am not sure if it is possible but we plan to phase out msi installer anyways since no one in the team really wants to maintain it so might not worth the effort.

Edit: https://stackoverflow.com/questions/14762617/wix-bootstrapper-how-do-i-set-burn-variables-from-the-command-line

Copy link
Copy Markdown
Member

@FabianLars FabianLars left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

still didn't test it but can't be worse than the current version and the code looks good to me 🤷

@amrbashir amrbashir merged commit bf29a72 into v2 Jun 12, 2024
@amrbashir amrbashir deleted the fix/updater/msi branch June 12, 2024 22:35
@songjiachao
Copy link
Copy Markdown

when publish the next version

@nwehrhan
Copy link
Copy Markdown

Hmm I still can't msi to actually do the update. Says "success".
https://discord.com/channels/616186924390023171/1253345571599814666/1253345571599814666

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Updater ISSUE in Windows Installer .msi

4 participants