Epic: Automated release spike

[darcyclarke]

• Identify a project (not cli) to automate the releases of
• Set up CI integration to run tests/benchmarks
• Set up CD integration to automate versioning/releasing/publishing

[wraithgar]

Notes from chats w/ @nlf:

We may want to remove the package-locks from our packages so that our deps PRs don't get unmanageable
If we remove them, we want a scheduled CI for our packages that runs periodically so we know if new deps break our tests. These can be weekly, nothing egregious.

[wraithgar]

With no package-lock audits become tricky. We can either have an audit action or make npm audit work with no lockfile.

[ljharb]

@wraithgar npx aud has you covered :-p or you could do the latter, which was mildly promised 3 years ago

[darcyclarke]

Update

• spike completed
• will be pulling in changes to template-oss as a a result of this r&d (ref. feat: add release process scripts template-oss#20)