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

Add release automation #3

Open
agilgur5 opened this issue Jun 14, 2022 · 0 comments
Open

Add release automation #3

agilgur5 opened this issue Jun 14, 2022 · 0 comments
Labels
kind: internal Changes only affect the internal API

Comments

@agilgur5
Copy link
Owner

agilgur5 commented Jun 14, 2022

Release / Publishing automation

Add GH Action(s) for release automation.

This is a fairly important piece that I've been missing in my libraries for a bit now and that simplifies the process of publishing into something that requires less effort and can have a quick loop (at least from PR to patch release).
This would also make it less error-prone (even I forget my own release steps occasionally after being away for a while, due to some of the manual portions that I never got around to automating) and easier to hand-off to collaborators to release too; not dependent on a single person to do releases then.

Can see some past thoughts and tools here: jaredpalmer/tsdx#254 (comment)

A brief list (will add more over time):

Nice to have: create GH release with the compiled/bundled JS code as well as artifacts (not just the source in the GH release)

Changelog / Release Notes vs. Publishing

May need/want a separate tool for changelog generation/release notes vs. just publishing a release.

I do more or less like the release notes I've crafted for TSDX and rpt2

Some tools (will add more over time):

other potential GH Actions to add

Split off from #1 (comment)

Might also want to add actions for community management, e.g. auto mark as stale if no OP response in 30+ days, auto-lock in 90+ days if closed, stale, and no response

@agilgur5 agilgur5 added the kind: internal Changes only affect the internal API label Jun 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind: internal Changes only affect the internal API
Projects
None yet
Development

No branches or pull requests

1 participant