Release: Inno Setup installer and automatic version bump #8
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "dev"
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?
Promotes the installer and automatic versioning work from
devtomainforrelease.
Included since the last
mainrelease (from PR #7):optional desktop shortcut, always-on Start Menu entry.
installer/*.issplusa parse-validated
build-installer.ps1helper.git tags; the
version-bump.ymlForgejo Actions workflow tags a new version oneach
devtomainmerge (minor++, patch = PR number).THIRD-PARTY-NOTICES build-time tooling) and
.gitignore/.gitattributesadjustments for
publish/,dist/, and*.iss.Merging this PR is expected to trigger the Version Bump workflow and create the
first
v{major}.{minor}.{patch}tag.Fixes #
How was this tested?
dotnet build Tayler.slnx- 0 errors, 0 warnings (MinVer resolving theversion)
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)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>