Auto Release By Psmodule Github Marketplace

Leo Migdal

-Dec 4, 2025, 7:31 PM

auto release by psmodule github marketplace

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. 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. 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. There was an error while loading. Please reload this page. There was an error while loading. Please reload this page. Sourced from actions/checkout's releases.

Full Changelog: actions/checkout@v5.0.0...v6.0.0 Updated persist-credentials to store the credentials under $RUNNER_TEMP instead of directly in the local git config. There was an error while loading. Please reload this page. There was an error while loading. Please reload this page.

There was an error while loading. Please reload this page. 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. When developers work on software projects, they often reach points where they want to make a specific version of their software available to users or other developers and at that point they create a... GitHub Releases are a way to package and distribute software releases on the GitHub platform.

The most common way of publishing release is in X.Y.Z format. There is also release types like Pre-Release/Beta, Release Candidate(RC) or Alpha Release being used frequently. The choice of release type depends on factors such as the development process, project requirements, and the level of stability and maturity desired for the software. For now, we will just focus on Major and Minor Release type. Using Github Action we can automate the release process. Lets jump into the process.

Auto Release By Psmodule Github Marketplace

People Also Search

Automatically Creates Releases Based On Pull Requests And Labels. The

The Workflow Will Trigger On Pull Requests To The Main

It Will Use Your CHANGELOG File To Determine The Description

You Can Define Your Own Replacements By Using A Custom

Full Changelog: Actions/checkout@v5.0.0...v6.0.0 Updated Persist-credentials To Store The Credentials Under