add npm publish gha

[acharb]

ticket

I'll ping ops to add the npm token as a secret

[acharb]

@piyalbasu I played around with a way to auto-set the package.json version file using like:
yarn publish --access public -new-version ${{ github.event.release.tag_name }}

but it requires a github profile env var to do looks like

I was also thinking maybe isn't worth the customization? might be annoying with edge cases if we need to like release an older version or something?

[Ifropc]

Is this triggered on a new tag?

[acharb]

Is this triggered on a new tag?

on a new published release. the js sdk is using the same

[piyalbasu]

@piyalbasu I played around with a way to auto-set the package.json version file using like: yarn publish --access public -new-version ${{ github.event.release.tag_name }}

but it requires a github profile env var to do looks like

I was also thinking maybe isn't worth the customization? might be annoying with edge cases if we need to like release an older version or something?

Ah yeah. I tried to implement something similar in the GHA pipeline for Freighter (https://github.com/stellar/freighter/blob/master/.github/workflows/submitProduction.yml#L65) that updates the version and creates a PR. It's actually really annoying - the CI never runs properly on the generated PR due to a bug in GHA. I was hoping maybe it'd be easier in Jenkins 😄

Probably best to hold off on this for now until I can fix the Freighter version of bumping the version number