Skip to content

chore(ci): Automate Releases #1366

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

Open
wants to merge 6 commits into
base: main
Choose a base branch
from
Open

Conversation

cschiewek
Copy link
Contributor

This PR aims to automate the process of publishing releases to hex.pm.

Currently we need to manually update the changelog, create and push the tag, publish the release in github, and publish to hex. This makes publishing package updates onerous.

This automates all of that by:

  • Enforcing conventional commit messages for PR titles to enable automatic changelog updates
  • Leveraging the release-please to create and update release PRs, which track changes to the changelog and version bumps, and create releases when release PRs are merged.
  • Add a github action to publish the package to hex.pm when a github release is created.

Before merging this, there are a few things that need to happen in github:

  • Create an org level secret named ORG_GITHUB_TOKEN that contains a github token with permissions to write contents and pull requests.
  • Create an org level secret named HEX_API_KEY with permissions to publish to hex.
  • Update merge settings to:
    • Only allow squash & merge
    • Default PR titles to commit message

I do not have permissions to do those things, so if everyone on @absinthe-graphql/creators could do that for me, or give me permissions to do so, that'd be 💯 .

@cschiewek cschiewek changed the title Automate Releases chore(ci): Automate Releases May 29, 2025
@cschiewek cschiewek requested a review from a team May 29, 2025 15:00
@cschiewek cschiewek self-assigned this May 29, 2025
@cschiewek
Copy link
Contributor Author

@benwilson512 I would really love to move this forward. Could you please give me appropriate permissions to do the following (or alternatively do these things):

  • Create an org level secret named ORG_GITHUB_TOKEN that contains a github token with permissions to write contents and pull requests.
  • Create an org level secret named HEX_API_KEY with permissions to publish to hex.
  • Update merge settings to:
    • Only allow squash & merge
    • Default PR titles to commit message

Thank you.

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