Skip to content

feat: release pipeline #186

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

Merged

Conversation

juleswritescode
Copy link
Collaborator

@juleswritescode juleswritescode commented Jan 30, 2025

A hand-made release pipeline that will do the following on manual trigger:

  • Run Tests on Windows, MacOS, Linux
  • build the pg_cli for six rust target-triples
  • increment the release-tag based on our commit history
  • create a GH release with that tag
  • attach a autogenerated changelog to the release
  • attach the compiled binaries to the release

The result for the first release will look something like below – which is why we should use semantic commits and squash merges 🤣:

-- image removed

@juleswritescode juleswritescode marked this pull request as draft January 30, 2025 08:58
@psteinroe
Copy link
Collaborator

@juleswritescode can we write the first release manually? 😂

@juleswritescode juleswritescode marked this pull request as ready for review January 31, 2025 12:00
@juleswritescode
Copy link
Collaborator Author

@juleswritescode can we write the first release manually? 😂

Let's do that :) I'll run it again on my private repo to see if everything works first.
Then, is it fine for you if we just edit the release body? Or should I disable setting the output in the yaml file before we merge?

@psteinroe
Copy link
Collaborator

I don't know how it works exactly. I fine with anything as long as we can edit the body manually before releasing.

@juleswritescode
Copy link
Collaborator Author

Update: the Workflow works with all six runner-types. :)

We can simply publish a release and then edit the Release body and write whatever we want.

It's ready for review 👍

Screenshot 2025-01-31 at 14 00 16

Copy link
Collaborator

@psteinroe psteinroe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome!!

@juleswritescode
Copy link
Collaborator Author

juleswritescode commented Jan 31, 2025

This will now create a Draft Release that is only visible to maintainers of the repo.
The workflow will output a Link to the Draft Release as a Summary. 👍

add cliff.toml

rename bin

switch to compile bin

checked in

remove that little one

quotes

single pie

cargolock
@juleswritescode juleswritescode merged commit c7aea51 into supabase-community:main Jan 31, 2025
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