Add Release Drafter for automating releases notes

[shivay-at-pieces]

Add release-drafter.yml for automating release notes

on:
  push:
    branches:
      - main

jobs:
  update_release_draft:
    runs-on: ubuntu-latest
    steps:
      - uses: release-drafter/release-drafter@v5
        with:
          config-name: release-draft-template.yml
        env:
          GITHUB_TOKEN: ${{ secrets.RELEASE_DRAFTER_TOKEN }}```

Release-drafter template:

name-template: 'Pieces TypeScript SDK v$NEXT_PATCH_VERSION'
tag-template: 'v$NEXT_PATCH_VERSION'
categories:
  - title: '🚀 Features'
    labels:
      - 'kind/feature'
      - 'kind/enhancement'
  - title: '🐛 Bug Fixes'
    labels:
      - 'kind/fix'
      - 'kind/bugfix'
      - 'kind/bug'
  - title: '🧰 Maintenance'
    labels:
      - 'kind/chore'
      - 'area/ci'
      - 'area/tests'
  - title: 📖 Documentation
    label: area/docs
change-template: '- $TITLE @$AUTHOR (#$NUMBER)'
template: |
  ## What's New
  ## 🔤 General
  $CHANGES

  ## 👨🏽‍💻 Contributors

  Thank you to our contributors for making this release possible:
  $CONTRIBUTORS

[jwafu]

looks good lets get this in! ill queue this up on a PR and tag you to review just to make sure i didnt miss anything

[jwafu]

do we need to do anything here with the secrets? i generated and added a key that is named as follows:

on the open source parent repo. let me know what you think about this approach, that way we can pipe updates through the parent repo for other updates. if this is all looking solid i should be able to test this today

@shivay-at-pieces let me know what you see here - can always update a secret/add a new secret to this public repo individually for now as well.

[shivay-at-pieces]

Sure I think we can test this approach with the secret being in the parent repo @jordan-pieces

[jwafu]

going to update the secrets name, but we should test this and see if it works properly. also i am not sure how much we need to use keys since both repos are public, unless i am missing something there. but let me know.

[jwafu]

@shivay-at-pieces is this functioning as desired currently? or are there some steps that need tested ?

[CBID2]

Hey @mason-at-pieces, can I work on this while you're still working on docs migration?

[mason-at-pieces]

@shivay-at-pieces what is the status of this issue? Was it essentially put on hold about a month ago?

[shivay-at-pieces]

Hi @mason-at-pieces we are yet to test this out at the moment. But @CBID2 if you are interested in also contributing, let us know. Also @mason-at-pieces will touch base with you regarding Release drafter in general for our SDK docs internally.

[CBID2]

Hi @mason-at-pieces we are yet to test this out at the moment. But @CBID2 if you are interested in also contributing, let us know. Also @mason-at-pieces will touch base with you regarding Release drafter in general for our SDK docs internally.

I want to contribute to this @shivay-at-pieces