Auto Release Actions Github Marketplace Github

Leo Migdal

-Nov 9, 2025, 2:43 PM

auto release actions github marketplace github

A GitHub Action to automatically create a Release when a commit message matches a pattern. Auto-Release on Commit will create a release for you when you push a commit with a message matching a pattern. It will use your CHANGELOG file to determine the description of your Release. To get started, create a workflow .yml file in your .github/workflows directory. There is an example workflow below. For more information, take a look at the GitHub Help Documentation for GitHub Actions

Certain inputs can use replacements that use the version information from the commit message. The following replacements can be used in the title, tag, and changelog-entry inputs. You can define your own replacements by using a custom regex input, see the Patterns section for more info. Wouldn't it be nice if you could automatically generate GitHub releases with detailed release notes? Writing release notes can be a pain, but if you take care in structuring your branches into logical work packages, writing informative commit messages, and adding summaries to your pull requests, you can automate... In this article, I will show you how to set up a GitHub Actions workflow that does just that.

This article assumes that you have a setup similar to a previous article of mine about Bulding and deploying locally using GitHub Actions and webhooks. If you followed the previous article, the workflow code you see here will be a direct drop-in into your existing workflow. If you have a different setup, you might need to adjust the workflow to fit your needs. Perhaps the most critical prerequisite is that you follow semantic versioning and write good commit messages and PR summaries. This is what the workflow will use to generate the release notes and also ensure you get major, minor, and patch versions correctly. This is really important for helping your users understand the impact of changes in your releases.

The partial workflow below is drop-in code for the workflow in the previous article. It will generate release notes based on the PR title, body, and commit messages. It will also generate links to the Docker images that were built in the workflow. Communities for your favorite technologies. Explore all Collectives Stack Overflow for Teams is now called Stack Internal.

Bring the best of human thought and AI automation together at your work. Bring the best of human thought and AI automation together at your work. Learn more Find centralized, trusted content and collaborate around the technologies you use most. Bring the best of human thought and AI automation together at your work. This action simplifies the GitHub release process by automatically uploading assets, generating changelogs, handling pre-releases, and so on.

NOTE: The marvinpinto/action-automatic-releases repository is an automatically generated mirror of the marvinpinto/actions monorepo containing this and other actions. Please file issues and pull requests over there. This example workflow will kick in as soon as changes land on master. After running the steps to build and test your project: You can see a working example of this workflow over at marvinpinto/actions. Similar to the previous example, this workflow will kick in as soon as new tags are pushed to GitHub.

After building & testing your project: Automate your GitHub release workflow with GitHub Actions—no more manual tagging or UI clicks. In this tutorial, we’ll use the Troubleshooting JavaScript Actions repository as our example, transforming a once-manual process into a seamless pipeline. Before automation, releases were created by hand: For each release, you specify the tag, assign the branch, and craft release notes: Each published release is tied to a Git tag, pointing to a precise code snapshot.

Automating this ensures consistency and saves time. GitHub’s Actions Marketplace provides community-maintained workflows. A search for “release” surfaces many options. We’ll use the popular softprops/action-gh-release action: Automatically generate a release when the package.json version changes. The release name and tag will match the new version.

If no releases yet exist, this action will create the first release. The release notes will contain a change log generated from git history in the following format: Works great in tandem with auto-publishing. Here's an example for the GitHub Package Registry: Automatic GitHub Release is not certified by GitHub. It is provided by a third-party and is governed by separate terms of service, privacy policy, and support documentation.

Automatic GitHub Release is not certified by GitHub. It is provided by a third-party and is governed by separate terms of service, privacy policy, and support documentation. Automatically creates releases based on pull requests and labels. The workflow will trigger on pull requests to the main branch. The following labels will inform the action what kind of release to create: When a pull request is closed, the action will create a release based on the labels and clean up any previous prereleases that was created.

The labels can be configured using the MajorLabels, MinorLabels and PatchLabels parameters/settings in the configuration file to trigger on other labels. Join the DZone community and get the full member experience. Deploying FastAPI apps manually gets old fast. You SSH into a server, pull the latest code, restart the service, and hope nothing breaks. Maybe you remember to run tests first. Maybe you don't.

One forgotten environment variable or skipped test, and your API is down. Users get 500 errors. You're frantically SSHing back in to fix it. GitHub Actions can automate the entire deployment process. Push to your main branch, tests run automatically, and if they pass, your app deploys. No SSH.

No manual steps. No forgotten checks. We'll use a simple FastAPI app to demonstrate the pipeline. Your actual app will be more complex, but the deployment process stays the same.

Auto Release Actions Github Marketplace Github

People Also Search

A GitHub Action To Automatically Create A Release When A

Certain Inputs Can Use Replacements That Use The Version Information

This Article Assumes That You Have A Setup Similar To

The Partial Workflow Below Is Drop-in Code For The Workflow

Bring The Best Of Human Thought And AI Automation Together