Skip to content

Conversation

@alexforster
Copy link
Member

No description provided.

@alexforster
Copy link
Member Author

@danielocfb Here's where I'm getting stuck with this release process. How do you get the tag on master? I'm assuming there's some Github-ism I'm unfamiliar with.

@alexforster alexforster self-assigned this Jul 1, 2025
@alexforster
Copy link
Member Author

alexforster commented Jul 1, 2025

Oh: 1753345

I guess it's been more than a year since I've published a release!

@alexforster alexforster merged commit f62bb01 into master Jul 1, 2025
33 checks passed
@alexforster alexforster deleted the 1.5.2+v1.5.1 branch July 1, 2025 21:45
@danielocfb
Copy link
Collaborator

Oh: 1753345

I guess it's been more than a year since I've published a release!

Yes, sorry, I should have pinged you back then. Let me know if we should document the workflow somewhere (I just figured it's pretty straight-forward, but I suppose nobody ever said otherwise). But at least it seems everything has worked now. A tag should be automatically created by GitHub Actions now.

@alexforster
Copy link
Member Author

It's fine, I like this much better! Seemed super straightforward to me once I realized things had changed.

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.

3 participants