Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Release process #1421

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

Closed
nurey opened this issue Jun 14, 2024 · 1 comment
Closed

Release process #1421

nurey opened this issue Jun 14, 2024 · 1 comment

Comments

@nurey
Copy link

nurey commented Jun 14, 2024

I am wondering what the release process is for this project. Forgive me if this is documented somewhere. I could not find it in the README. I see the last release was April 16. There's some fixes that have gone in that I would love to benefit from. I would love to know when the next release will be cut. Thank you!

@SutuSebastian
Copy link
Collaborator

It is not documented anywhere, but its a good idea to do so.
Initially I was planning to do a release at the end of each week (if we have any batch of updates), but slowly I got overwhelmed by work. Now that I have more free time on my hands I'll be pushing some more on the library, issues, PR's, discussions, etc.

Regarding how a release is done:
We are using Changesets so u can read more on their repo how things work, pretty much is no-code release, just a push of a button on the Version Packages PR, there u can find the summary of all the changes that will be brought to each package/namespace.

@themesberg themesberg locked and limited conversation to collaborators Jun 20, 2024
@SutuSebastian SutuSebastian converted this issue into discussion #1429 Jun 20, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants