Repository navigation
Move CI and release to GitHub Actions - #33
Merged
Merged
Conversation
Replaces the two Azure Pipelines definitions with the workflows the other DSoft libraries use. ci.yml builds Release for every target framework on pull requests to master and development. release.yml runs on every push to master: builds Release as 4.0.yyMM.<run number>, uploads the package as the drop artifact, pushes it to nuget.org with Trusted Publishing, and tags the commit and creates a GitHub release. AssemblyVersion is still not stamped by CI; it stays pinned in the project file for the reason recorded there. ContinuousIntegrationBuild now also switches on under GITHUB_ACTIONS so Source Link keeps emitting. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.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
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.
Replaces the two Azure Pipelines definitions with the GitHub Actions workflows the other DSoft libraries use (MessageBus, DSoft.DataPrivacy, System.Mvvm), adapted for this repository.
Workflows
.github/workflows/ci.yml: pull requests tomasteranddevelopment,windows-latest. Restores workloads, restores and builds the solution in Release for every target framework. No test project exists;WpfSamplebuilds with the solution..github/workflows/release.yml: every push tomaster(Markdown and workflow-only changes skipped). Builds Release as4.0.yyMM.<run number>plusRELEASE_SUFFIX, collects the.nupkgand.snupkg, uploads them as thedropartifact, signs in to nuget.org with Trusted Publishing (NuGet/login,NUGET_USERsecret,nugetenvironment) and pushes, then tagsv<version>and creates a GitHub release.Differences from the reference repositories, on purpose
master, notmain; this repository has not been renamed./p:AssemblyVersionis not passed. The project pinsAssemblyVersionat 4.0.0.0 because a strong-named assembly whose identity moves every build forces a binding redirect on net481.FileVersionstill carries the build number. The Azure definition had the same rule.ContinuousIntegrationBuildin the csproj now also switches on underGITHUB_ACTIONS, so Source Link keeps emitting deterministic builds on the new runner.Also
azure-pipelines-mergetest.ymlandazure-pipelines-release.ymlremoved; the solution's.cifolder now lists the workflows.nugetenvironment has been created on the repository.Before merging to master
NUGET_USERsecret to thenugetenvironment (the nuget.org account that holds the Trusted Publishing policy).newky2k/DSoft.System.BluetoothLe, workflowrelease.yml, environmentnuget.Version caveat
The first Actions release in a given month gets run number 1. Azure published
4.0.2610.91on 2026-10-09, so an Actions release before November would sort below it (4.0.2610.1). Either merge to master in November or later, or run the first release with a bumped prefix.🤖 Generated with Claude Code
https://claude.ai/code/session_011BUngYxwUVBfZrK5gCvzgm