Conversation
Agent-Logs-Url: https://github.com/LFPy/LFPykit/sessions/c4333dda-327a-4607-bfdb-8ec96a047a87 Co-authored-by: espenhgn <2492641+espenhgn@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Add GitHub action to automatize releases on merge
Add GitHub Action to automatically create GitHub releases on version bump
Apr 10, 2026
espenhgn
approved these changes
Apr 10, 2026
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.
Description
Adds
.github/workflows/create-release.yml— a workflow that automatically creates a GitHub release whenever a push tomasterintroduces a new version that hasn't been tagged yet.Workflow logic:
lfpykit/version.pyviagrep(noexec()/eval())v{version}tag usinggit ls-remote --exit-codev{version}, titleLFPykit-{version}, with auto-generated notesIntegration with existing workflows:
python-publish.ymltriggers onrelease: types: [created], so PyPI publishing is automatically chained after this workflow creates the release — no changes to the publish workflow needed.Related Issue
Closes #[issue]
Motivation and Context
Releases and PyPI publishes were previously manual. With this change, bumping the version in
version.pyand merging tomasteris sufficient to trigger the full release pipeline.How Has This Been Tested
Workflow logic verified by inspection: the
git ls-remote --exit-codeguard prevents duplicate releases on repeated pushes without a version bump.Types of changes
Checklist