Skip to content

update release process for expressions lib to reduce manual steps - #305

Merged
nathanbegbie merged 3 commits into
developfrom
update-release-process-for-expressions-lib-to-reduce-manual-steps
Jan 21, 2026
Merged

update release process for expressions lib to reduce manual steps#305
nathanbegbie merged 3 commits into
developfrom
update-release-process-for-expressions-lib-to-reduce-manual-steps

Conversation

@nathanbegbie

@nathanbegbie nathanbegbie commented Jan 21, 2026

Copy link
Copy Markdown
Member

This updates .github/workflows/releases.yml to do a few things.

  1. only trigger when a Release is created.
on:
  release:
    types: [published]
  1. have the script itself verify the version listed in mix.exs and README.md and if the version tag doesn't match, update it appropriately with version control, before releasing to hex and hexdocs. (I've had some success with this approach, in a personal project
  2. Add dependency caching, like we do in the elixir.yml workflow
  3. Update the README.md to reflect this process

BUT WHY?

Anything that we can do to simplify the release process, the better. This enables the support team to be able to rapidly create releases as needed, without needing to faff about with updating versions appropriately before creating a release. This can just be fire and forget.

Side Quests

Update the workflows so that they only trigger on appropriate file changes

- Trigger on GitHub release publish instead of tag push
- Automatically update mix.exs and README.md versions to match release tag
- Add dependency caching using same key format as elixir.yml
- Update README with new release process documentation
@nathanbegbie nathanbegbie self-assigned this Jan 21, 2026
@nathanbegbie
nathanbegbie requested review from samrat and smn January 21, 2026 13:54
@nathanbegbie
nathanbegbie merged commit da39fa0 into develop Jan 21, 2026
2 checks passed
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