Add Inno Setup installer and automatic version bump #7
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feature/installer"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What does this PR do?
Adds a Windows installer for Tayler Log Tailer plus automatic version management.
Installer (Inno Setup 6): per-machine (Program Files, admin elevation),
x64-only, and self-contained - the .NET 10 runtime is bundled, so no separate
runtime install is required. Always creates a Start Menu entry and offers an
optional desktop shortcut (unchecked by default).
installer/TaylerLogTailer.iss- the Inno Setup script.installer/build-installer.ps1- publishes the self-contained x64 build thencompiles the installer with ISCC. Parse-validated.
Versioning (mirrors SqlServerAgMonitor): the assembly and installer version
is derived from git tags by MinVer, and a Forgejo Actions workflow tags a new
version on each
devtomainmerge.Directory.Build.props- MinVer 6.0.0 (PrivateAssets=All), tag prefixv,minimum 1.0.
TaylerLogTailer.csproj- dropped the static<Version>(MinVer supplies it);kept Company/Product/Copyright metadata.
.github/workflows/version-bump.yml- on a merged PR intomain, incrementsthe minor and sets patch to the PR number, then pushes a new
v{major}.{minor}.{patch}tag. Targets theubuntu-latestrunner..gitignore- ignorespublish/anddist/build artifacts..gitattributes- marks*.issas CRLF.README.md- new Installer and Versioning sections; updated project layout.THIRD-PARTY-NOTICES.md- notes MinVer and Inno Setup as build-time tooling.A Windows-based Forgejo runner and a release/installer-build workflow (publish +
compile the installer + attach to a Forgejo release) are deferred to a follow-up.
Fixes #
How was this tested?
dotnet build Tayler.slnx- 0 errors, 0 warnings (with MinVer restoring andresolving the version)
FileVersion 1.0.0.0,ProductVersion 1.0.0-alpha.0.N(pre-release, no tag yet).installer/build-installer.ps1end-to-end: published the self-containedx64 build then compiled
dist/TaylerLogTailer-1.0.0.0-setup-x64.exe(44.7 MB).devtomainmerge (runner +tag-push permissions confirmed)
Checklist
Mirror the versioning approach from SqlServerAgMonitor so releases are tagged and versioned automatically. - Directory.Build.props: add MinVer 6.0.0 (PrivateAssets=All) with tag prefix v and MinVerMinimumMajorMinor 1.0, so the assembly/installer version derives from git tags. - TaylerLogTailer.csproj: drop the static <Version> (MinVer now supplies it); keep Company/Product/Copyright. - .github/workflows/version-bump.yml: Forgejo Actions workflow that, on a merged PR into main, increments the minor and sets patch to the PR number, then pushes a new v{major}.{minor}.{patch} tag. Targets the ubuntu-latest runner. - README.md: add a Versioning section and list the workflow in the project layout. - THIRD-PARTY-NOTICES.md: note MinVer alongside Inno Setup as build-time tooling. The installer reads the published exe's file version, so tagged builds flow straight into the setup filename and metadata. A Windows runner plus a release/installer-build workflow are deferred to a follow-up. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>Add Inno Setup installer for self-contained x64 buildto Add Inno Setup installer and automatic version bump