bug: release pipeline does not iterate package version or create tags

[johnjenkins]

Prerequisites

• I have read the Contributing Guidelines.
• I agree to follow the Code of Conduct.
• I have searched for existing issues that already include this feature request, without success.

Describe the Feature Request

Since migrating to the new npm publish flow, the new store package version is correctly iterated and published to npm, however the that same version number is does not change the package.json , package-lock.json or create a new tag in github meaning we manually have to change those files.

Describe the Use Case

n/a

Describe Preferred Solution

n/a

Describe Alternatives

No response

Related Code

No response

Additional Information

No response

[gnbm]

@johnjenkins didn't get much time put if you could check this out, I would appreciate it

[gnbm]

@johnjenkins, the PR was merged. Next time you run the pipeline, please let me know if it worked and if we can close this issue. Cheer