Initial auto npm release workflow

[nayeonk]

As of 10/18:

• Completed the step: checkout release branch from master 🎉

As of 10/11:

• Triggers workflow via push for now, until this is merged into master
• Started on checking out release branch. Seeing describe errors.

As of 10/4:

• wrote out the steps for a larva release, discussed what can be automated and what cannot
• started reading into workflow_dispatch that triggers the release

Make sure you complete these items:

• Updated root CHANGELOG.md with summary of changes under Unpublished section
• npm run prod in this repo outputs expected changes (excepting the issue with re-ordered partials in larva-css algorithms partials - see LRVA-1885)
• If adding a new pattern, in the PR comment, included a screenshot and link to the static Vercel deployment
• If changes to build scripts or the Node.js server, tested changes in pmc-spark via a pre-release
• • If changes to build tools: npm scripts prod, lint, and dev scripts run as expected
• • If changes to Larva server: Static site generates as expected in a theme (avail. on a URL {brand}.stg.larva.pmcdev.io)

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
pmc-larva	❌ Failed (Inspect)			Sep 26, 2023 6:54pm