Skip to content
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

Thoughts on release automation? #585

Closed
rwjblue opened this issue Oct 22, 2020 · 3 comments · Fixed by #711
Closed

Thoughts on release automation? #585

rwjblue opened this issue Oct 22, 2020 · 3 comments · Fixed by #711

Comments

@rwjblue
Copy link
Collaborator

rwjblue commented Oct 22, 2020

I've been thinking that it may make sense to add some sort of release automation here to make it easier to do things like change log curation and updating GitHub releases (I don't think we currently do this, but its really nice for folks that want to watch this repo for "releases only").

I'm happy to whip up a PR to use my "go to" setup (basically npx create-rwjblue-release-it-setup).

Here is the general release documentation for it.

What do you think?

@simonihmig
Copy link
Collaborator

👍 would love it! I am using Rob's setup basically everywhere nowadays!

@ef4
Copy link
Contributor

ef4 commented Oct 22, 2020

Yeah, this sounds good, as long as your tool can update all the cross dependencies between packages. I didn’t use lerna because it has bit me in the past and keeping everything in lock step, at least right now, is enough.

Pretty soon though we will want to cut a stable release of (for example), the macros package. At which point fancier release management may be required, as not everything will stabilize at the same time.

@ef4
Copy link
Contributor

ef4 commented Oct 22, 2020

It may also be fine to let macros graduate to a separate repo.

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 a pull request may close this issue.

3 participants