Merged
Conversation
Contributor
Author
|
Well this pr fails CI because it's a special case of changing the "version" file without making a release 😉 |
e895f5c to
e2589f3
Compare
e2589f3 to
572cd0d
Compare
Member
|
Strange that we include DCO, but not COPYING. looks good otherwise. |
a3f
approved these changes
Nov 28, 2025
This github actions workflow will create a draft release for PRs that updates the version file. The commit message subject line must be Release microcom <version> The commit message body will be used as release description. The release is converted from draft to an actual release, and the commit thereby tagged once the PR is merged. Signed-off-by: Jonas Rebmann <jre@pengutronix.de>
572cd0d to
95f4e35
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This github actions workflow will create a draft release for PRs that updates the version file.
The commit message subject line must be
Release microcom <version>The commit message body will be used as release description. The release is converted from draft to an actual release, and the commit thereby tagged once the release PR is merged.
Commits are tagged as v as usual.
tar.gzandtar.xzoutput ofmake distis added to the release assets.see
https://github.com/jonrebm/microcom/releases/tag/v2025.11.0
for results