improve circleci caching

[evant]

No description provided.

[eygraber]

Would you be willing to switch to using GitHub Actions? I have a pretty good flow in place for my own libraries that I could implement here if you want. It seems simpler than what's going on with CircleCI.

[evant]

I've been using circelci forever so it's the one I'm the most familiar with. It also has no build credit limit unlike github actions.

[evant]

welp still having issues, @eygraber if can show GitHub actions being more stable I'll switch

[eygraber]

I'll start putting something together.

Here's an example of what releases would look like (customizable via changelog_config.json).

Snapshots are published after PRs are merged, and releases are created and published by manually running the Publish release workflow in GitHub Actions.

Required secrets:

• PUSH_PAT: a GitHub token for a (bot) account that bumps the version after a release is made and automatically tracks changes to package-lock.json or yarn.lock
• SONATYPE_NEXUS_USERNAME
• SONATYPE_NEXUS_PASSWORD

Optional secrets:

• ARTIFACT_SIGNING_PRIVATE_KEY: a PGP key for signing the artifacts when publishing to maven central
• GIT_SIGNING_PRIVATE_KEY: a PGP key for signing the version bump commit and release tag
• GIT_SIGNING_PRIVATE_KEY_PASSWORD: password for GIT_SIGNING_PRIVATE_KEY

[evant]

created #486 to move discussion to so it's not lost the in ether