Skip to main content

Github–Create a new release–The automated version

Yesterday I showed you how to create a new release in Github manually. This was a good starting point as it introduced the different elements of a release and the options we have. Today let us automate the process of creating a release on GitHub using GitHub Actions.

Create a new release using Github Actions

  • Go to Actions inside Github and click on new workflow.

  • We’ll not use an existing template but instead choose to setup the workflow ourself:

  • Paste the following yaml content in the editor screen. I’ll explain it afterwards…


Explanation of the Workflow

  • name: This is the name of your workflow. You can name it something like "Release".

  • on: Specifies the event that will trigger the workflow. In this case, it’s triggered by a push to a tag that matches the pattern v*.*.* (e.g., v1.0.0).

  • jobs: This defines the job that will be run by the workflow.

  • runs-on: Specifies the environment where the job will run. In this case, it uses the latest Windows environment.

  • steps: This section lists the steps the job will take. I’ll focus on the actions specific for the release

    • actions/checkout@v4: Checks out the repository's code so that the workflow can access it.

    • actions/create-release@v1: This action is used to create the release. It uses the GITHUB_TOKEN secret to authenticate with GitHub. The release is named after the tag and includes a basic description. The draft and prerelease options can be set to true if you want the release to be a draft or a pre-release.

    • actions/upload-release-asset@v1: This action uploads assets (like compiled binaries, zipped files, etc.) to the release. The upload_url is provided by the previous step where the release was created.

Trigger the workflow

The workflow is set to trigger on a tag push that matches the pattern v*.*.*. Create a new tag and push it to trigger the workflow.

I can do this through the commandline:

git tag v1.0.0
git push origin v1.0.0

Or if you prefer a GUI, you can use for example Github Desktop:

  • Go to the History tab to see the latest commits: 

  • Right click on a commit and choose Create tag:
  • Specify a tag name using the v*.*.* pattern
  • Now we have one change that we should push to our remote origin:

The Github Actions workflow should pick up this change and start the release pipeline:

Once completed we have a brand new release available:


Nice!

Remark: We can further improve this by automatically generating the release notes but that is something I’ll leave for another post.




Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...
Read more

A complex system designed from scratch never works

A few years ago, I worked as an architect on a big mainframe rewrite. I still count it as one of my failures. Not because the technology was wrong, but because I couldn't convince the management team to simplify the approach. Years later, the organization is still struggling to get the new system up and running. I left the project at the time, because I couldn't put my name behind an approach that would take very long and cost a lot of money without a working system to show for it along the way. Gall’s Law That memory keeps coming back to me, because it's a textbook case of Gall's Law playing out in real life. Gall's Law , from John Gall's Systemantics , states it plainly: A complex system that works is invariably found to have evolved from a simple system that worked. A complex system designed from scratch never works, and it cannot be patched to make it work. You have to start over with a simple system that works. What does that mean in practice,...
Read more