Add automated release for end-to-end (e2e) automation - #70
Open
BartoszBlizniak wants to merge 2 commits into
Open
Add automated release for end-to-end (e2e) automation#70BartoszBlizniak wants to merge 2 commits into
BartoszBlizniak wants to merge 2 commits into
Conversation
There was a problem hiding this comment.
Pull request overview
Automates the repository’s release process for generated Go bindings by adding a GitHub Actions workflow that tags/releases based on the version in bin/generate, and updates contributor/docs/scripts to reflect the new post-merge release flow.
Changes:
- Added a Release GitHub Actions workflow that determines the binding version, runs
go test, and creates/attaches a GitHub release forv$PKG_VERSIONwhen not already published. - Updated contributor documentation to describe the automated release behavior after merging.
- Updated
scripts/update-bindings.shmessaging to remove now-obsolete manual tagging/release steps.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
.github/workflows/release.yml |
New workflow to compute version from bin/generate, run tests, and create/attach GitHub releases/tags. |
CONTRIBUTING.MD |
Documentation updated to reflect the automated tagging/release workflow after merges. |
scripts/update-bindings.sh |
Usage/instructions updated to point users to the Release workflow instead of manual tagging. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
…casing/spelling fixes Co-authored-by: BartoszBlizniak <55028730+BartoszBlizniak@users.noreply.github.com>
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 pull request automates the release process by introducing a GitHub Actions workflow to handle tagging and releasing, and updates documentation and scripts to reflect this new workflow. The main goal is to reduce manual steps and potential errors during releases.
Release automation:
.github/workflows/release.yml) that runs on every push tomasteror via manual dispatch. This workflow reads thePKG_VERSIONfrombin/generate, checks for existing releases/tags, runs tests, and creates the corresponding Git tag and GitHub release if needed.Documentation updates:
CONTRIBUTING.MDto explain that the release workflow now handles tagging and releasing automatically after a PR is merged, replacing previous manual steps.Script improvements:
scripts/update-bindings.shto update the post-merge instructions, informing users that the release workflow will handle publishing, and to suggest re-running the workflow if it fails or is skipped.scripts/update-bindings.shto reflect that tag and release creation are now automated by the workflow.