feat: add nightly preview NuGet release workflow - #218
Merged
Conversation
Adds .github/workflows/nightly-preview.yml which publishes a preview NuGet package for IntelliTect.Multitool nightly, but only when there are commits newer than the last published package (checked via the NuGet registration API). Manual runs via workflow_dispatch always force a build/publish. Reuses the existing OIDC-based NuGet trusted publishing login step from deploy.yml. Preview packages are versioned as <base>-preview.<yyyyMMdd>.<run_number> and are not attached to a GitHub Release (only tagged releases get those, via deploy.yml). Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds
.github/workflows/nightly-preview.yml- a nightly workflow that publishes a preview NuGet package forIntelliTect.Multitool, but only when there have been changes since the last published package. Modeled after the pattern in BenjaminMichaelis/DotnetTemplates, adapted to this repo's existing conventions.How it works
check-for-changes- checks out full history, queries the NuGet registration API (intellitect.multitool) for the latest published version's publish date, and compares it against the latest commit date. If nothing changed, the rest of the workflow is skipped.workflow_dispatchalways forces a run (for manual testing).build-test-pack- restores, builds, tests, and packs using the same flags asbuild-and-test.yml/deploy.yml. Version is computed as<latest-tag-patch-bumped>-preview.<yyyyMMdd>.<run_number>(e.g.1.0.2-preview.20260806.42).deploy- reuses the existing OIDC-based NuGet trusted publishing login (NuGet/login@v1, same asdeploy.yml) and pushes with--skip-duplicate. No GitHub Release is created for these preview builds - only tagged releases get those viadeploy.yml.Notes / assumptions
5 10 * * *(10:05 UTC daily) - adjust if a different time is preferred.deploy.ymlorbuild-and-test.yml; fully additive.attest/softprops/action-gh-releasesteps for nightly builds, since these are ephemeral preview packages rather than tagged releases.Verified the workflow YAML parses correctly (
yaml.safe_load);actionlintwasn't available locally to lint further.