Skip to content

Patch release GitHub action.#244

Merged
cwize1 merged 2 commits into
mainfrom
user/chrisgun/patchPipeline
May 23, 2025
Merged

Patch release GitHub action.#244
cwize1 merged 2 commits into
mainfrom
user/chrisgun/patchPipeline

Conversation

@cwize1
Copy link
Copy Markdown
Contributor

@cwize1 cwize1 commented May 23, 2025

Create a GitHub action workflow for building and publishing patch releases. These are mostly the same as major/minor releases but they don't fork a release branch and they don't use Makefile for the version. Instead patch releases auto-generate the next release version based on the previous git tags.


Checklist

  • Tests added/updated
  • Documentation updated (if needed)
  • Code conforms to style guidelines

Create a GitHub action workflow for building and publishing patch
releases. These are mostly the same as major/minor releases but they
don't fork a release branch and they don't use Makefile for the version.
Instead patch releases auto-generate the next release version based on
the previous git tags.
@cwize1 cwize1 requested a review from a team as a code owner May 23, 2025 18:38
Comment thread .github/workflows/scripts/next_patch_version.py
Comment thread .github/workflows/scripts/next_patch_version.py Outdated
Comment thread toolkit/scripts/build_tag_imagecustomizer.mk Outdated
Copy link
Copy Markdown
Contributor

@romoh romoh left a comment

Choose a reason for hiding this comment

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

Aside from the version bump/minor comments, looks good

@cwize1 cwize1 merged commit 656e2ef into main May 23, 2025
8 checks passed
@cwize1 cwize1 deleted the user/chrisgun/patchPipeline branch May 23, 2025 21:31
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.

2 participants