Skip to content

Decouple the app version from the pinned ezvpn.dll - #23

Merged
andrewchen5678 merged 1 commit into
mainfrom
decouple-app-version
Sep 1, 2026
Merged

andrewchen5678 merged 1 commit into
mainfrom
decouple-app-version

Conversation

@andrewchen5678

Copy link
Copy Markdown
Contributor

Summary

  • EzvpnVersion in Directory.Build.props is renamed EzvpnAppVersion and is now the app's own version; scripts/bump-dll.ps1 no longer touches it when re-pinning the DLL.
  • native/native.targets derives EzvpnCoreVersion from EzvpnReleaseTag; Ezvpn.App.csproj stamps it as assembly metadata and AppInfo exposes it. The main window header now reads v0.0.44 · core v0.0.44; the tray menu and Add/Remove Programs keep the app version.
  • The app version stays at 0.0.44 as its starting point.

Test plan

  • Windows CI (build, tests, publish, MSI)
  • pwsh scripts/bump-dll.ps1 v0.0.44 is a no-op diff (verified locally)

🤖 Generated with Claude Code

https://claude.ai/code/session_016bFY7oe5SzmhaKxy3TTo3y

Directory.Build.props EzvpnVersion becomes EzvpnAppVersion, the app's own
version: bump-dll.ps1 no longer rewrites it when re-pinning the DLL. The pinned
release is surfaced separately as EzvpnCoreVersion (derived from EzvpnReleaseTag
in native.targets) and stamped into the Ezvpn.App assembly metadata so the main
window header reads "v0.0.44 · core v0.0.44". Add/Remove Programs keeps
showing the app version.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016bFY7oe5SzmhaKxy3TTo3y
@andrewchen5678
andrewchen5678 merged commit 73d38b9 into main Sep 1, 2026
1 check passed
@andrewchen5678
andrewchen5678 deleted the decouple-app-version branch September 1, 2026 23:16
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.

1 participant