Skip to content

Move CI and release to GitHub Actions - #33

Merged
newky2k merged 1 commit into
developmentfrom
feature/github-actions
Oct 10, 2026
Merged

newky2k merged 1 commit into
developmentfrom
feature/github-actions

Conversation

@newky2k

@newky2k newky2k commented Oct 9, 2026

Copy link
Copy Markdown
Owner

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 to master and development, windows-latest. Restores workloads, restores and builds the solution in Release for every target framework. No test project exists; WpfSample builds with the solution.
  • .github/workflows/release.yml: every push to master (Markdown and workflow-only changes skipped). Builds Release as 4.0.yyMM.<run number> plus RELEASE_SUFFIX, collects the .nupkg and .snupkg, uploads them as the drop artifact, signs in to nuget.org with Trusted Publishing (NuGet/login, NUGET_USER secret, nuget environment) and pushes, then tags v<version> and creates a GitHub release.

Differences from the reference repositories, on purpose

  • Trigger branch is master, not main; this repository has not been renamed.
  • /p:AssemblyVersion is not passed. The project pins AssemblyVersion at 4.0.0.0 because a strong-named assembly whose identity moves every build forces a binding redirect on net481. FileVersion still carries the build number. The Azure definition had the same rule.
  • ContinuousIntegrationBuild in the csproj now also switches on under GITHUB_ACTIONS, so Source Link keeps emitting deterministic builds on the new runner.

Also

  • azure-pipelines-mergetest.yml and azure-pipelines-release.yml removed; the solution's .ci folder now lists the workflows.
  • README gains a "Continuous integration" section.
  • The nuget environment has been created on the repository.

Before merging to master

  1. Add the NUGET_USER secret to the nuget environment (the nuget.org account that holds the Trusted Publishing policy).
  2. On nuget.org, add a Trusted Publishing policy for newky2k/DSoft.System.BluetoothLe, workflow release.yml, environment nuget.
  3. Disable Azure pipelines 26 (MergeTest) and 27 (Release) and the classic release definition, so a master push does not publish twice.

Version caveat

The first Actions release in a given month gets run number 1. Azure published 4.0.2610.91 on 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

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>
@newky2k
newky2k merged commit 1bc0feb into development Oct 10, 2026
2 checks passed
@newky2k
newky2k deleted the feature/github-actions branch October 14, 2026 20:47
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