Skip to content

Feat modern pipelines - #352

Draft
salfuen wants to merge 2 commits into
masterfrom
feat-modern-pipelines
Draft

Feat modern pipelines#352
salfuen wants to merge 2 commits into
masterfrom
feat-modern-pipelines

Conversation

@salfuen

@salfuen salfuen commented Aug 4, 2026

Copy link
Copy Markdown
Collaborator

This PR moves our release flow fully to GitHub Actions and removes the old Makefile-based process.

The release workflow now runs manually with a version input, updates the project version, builds, tests, packs, and publishes from the pipeline. It also supports a dry run mode so we can validate everything without pushing tags, packages, or GitHub releases.

I also cleaned up old pipeline files and updated the docs so build, release, and docs deploy commands no longer depend on make. (docs were moved to docker compose as well)

@DFDS-Snyk

DFDS-Snyk commented Aug 4, 2026

Copy link
Copy Markdown

Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues
Licenses 0 0 0 0 0 issues
Code Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@nabisobhi nabisobhi left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Really like this direction 🙌 Consolidating the Makefile + Azure pipeline into a single manual GitHub Actions release is a big win for readability and maintainability 💯

permissions:
contents: write

jobs:

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One suggestion: I noticed the commit/tag/push currently happens before the build & test. So if the tests fail, we’ve already pushed a release: x.y.z commit and tag to the branch, but nothing has actually been published to NuGet. I’d suggest slightly changing the order:

  1. Update src/Dafda/Dafda.csproj version
  2. Build → Test → Pack
  3. Commit + tag + git push --follow-tags
  4. NuGet push + GitHub Release

That way, we only push the tag once we have a green build. 🙂

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.

3 participants