-
Notifications
You must be signed in to change notification settings - Fork 22
Add release workflow automation #79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Greptile SummaryAdds two GitHub Actions workflows to automate version management and releases for the WorkOS Elixir SDK. The
The workflows are well-structured with proper permissions, use pinned action versions for security, and integrate cleanly with the existing CI workflow. Confidence Score: 5/5
Important Files Changed
Sequence DiagramsequenceDiagram
participant Dev as Developer
participant VB as Version Bump Workflow
participant PR as Pull Request
participant RL as Release Workflow
participant GH as GitHub Release
participant Hex as Hex.pm
Dev->>VB: Trigger workflow_dispatch<br/>(select patch/minor/major)
VB->>VB: Read current version from mix.exs
VB->>VB: Calculate new version
VB->>VB: Update @version in mix.exs
VB->>PR: Create PR with version-bump label
Dev->>PR: Review and merge PR
PR->>RL: Trigger on PR close (merged + version-bump label)
RL->>RL: Extract version from mix.exs
RL->>GH: Create GitHub release with tag
RL->>RL: Setup Elixir/Erlang
RL->>RL: Install dependencies
RL->>Hex: Publish package with HEX_API_KEY
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
2 files reviewed, no comments
| pull_request: | ||
| types: [closed] | ||
| branches: [main] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure this flow will work with hex - releases become immutable one hour after publishing, so the version would need to be bumped with every PR before it can be pushed as a new release.
No description provided.