Update & automate changelog

[meritmalling]

• [x] Get manual updates to change log up to date by AM 6/25/24
• [ ] Refactor guides repo to accomadate automated updates triggered in other repos
• [ ] Create change log package that can be reused on repos that release on tagged cadences
• [ ] Add automations to the following repos that create a PR to the guides repo on release of a new version
  • [ ] flatfile-node (@flatfile/api)
  • [ ] flatfile-core-libraries (flatfile, @flatfile/listener, @flatfile/javascript, @flatfile/react, @flatfile/angular, @flatfile/vue)
  • [ ] flatfile-plugins (all)

[meritmalling]

WIP refactoring how the change log is structured in the guides repo. This piece of work is needed to allow other automations to send easy, incremental updates & the guides repo will know how to handle them.

[meritmalling]

WIP change log package that intakes tags and creates a pr to the guides repo.

[meritmalling]

Here's a lil sketch of the automation as it stands to go in. Just for this week I'm sure we can improve. Feedback very welcome @bangarang @NateFerrero!

[meritmalling]

These two PRs on the guides repo should go in for a full e2e test:

https://github.com/FlatFilers/Guides/pull/1161 (First action on guides in diagram) https://github.com/FlatFilers/Guides/pull/1168 (Second action on guides diagram)

When they go in I'll make and post a loom of the process!

TL:DR on process is that any repo with the changelog package installed/configured will, upon releasing a new package (eg @flatfile/react@8.0.0) will trigger these actions and create a PR in the guides repo. That PR still needs to be reviewed by a human before going in (we all agreed, cause hallucinations suck!) then it merged and goes live!

[meritmalling]

https://github.com/npm/cli/issues/2610 Is unfortunately causing issues for e2e since these actions run in actions.

ToDos to fix:

• Release package somewhere or use ssh credentials
• Also want gh bot credentials for prs instead of my PAC
• Bundle to support cjs and es