Skip to content
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(bundler): store and remove old main binary on updates if main binary name has change #10962

Merged
merged 5 commits into from
Sep 13, 2024

Conversation

amrbashir
Copy link
Member

ref: #10952

@amrbashir amrbashir requested a review from a team as a code owner September 11, 2024 16:27
Copy link
Contributor

github-actions bot commented Sep 11, 2024

Package Changes Through 7e5d257

There are 2 changes which include tauri-bundler with prerelease, tauri-cli 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
tauri-bundler 2.0.1-rc.10 2.0.1-rc.11
@tauri-apps/cli 2.0.0-rc.13 2.0.0-rc.14
tauri-cli 2.0.0-rc.12 2.0.0-rc.13

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


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

@amrbashir amrbashir force-pushed the feat/store-and-remove-main-binary-name branch from 33c85f2 to ce11113 Compare September 11, 2024 23:03
@@ -637,6 +637,15 @@ Section Install
WriteRegStr SHCTX "${UNINSTKEY}" $MultiUser.InstallMode 1
!endif

; Remove old main binary if it doesn't match new main binary name
ReadRegStr $0 SHCTX "${UNINSTKEY}" "MainBinaryName"
Copy link
Member

Choose a reason for hiding this comment

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

does this delete the binary on each install? since the v2 installer also uses the same key.. maybe we should use a different one for v2?

Copy link
Member Author

Choose a reason for hiding this comment

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

no this key will be removed when running the uninstaller, so it is only valid when doing updates. It has to be the same key for every installer (whether v1 or v2) so it can detect main binary name changes on updates

lucasfernog
lucasfernog previously approved these changes Sep 13, 2024
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.

2 participants