#24 fix: release config Pull request opened by YOU54F Description Create automated release pipeline for changes to nestjs-pact Motivation and Context the current release pipeline did not have • a valid NPM_TOKEN for publishing to the current scope

nestjs-pact

- I do not have rights to publish to that, so have used a scoped

@pact-foundation/nestjs-pact

token • Lerna, which was the commands expected for publishing How Has This Been Tested? E2E and published here https://www.npmjs.com/package/@pact-foundation/nestjs-pact?activeTab=versions I'd ideally like to delete that version, within 72 hours of creation, so that we can re-use the version number again https://docs.npmjs.com/policies/unpublish#packages-published-less-than-72-hours-ago but as its the only version , we won't be able to publish again to it for 24 hours If you entirely unpublish all versions of a package, you may not publish any new versions of that package until 24 hours have passed. Types of changes ☑︎ Bug fix (non-breaking change which fixes an issue) ☐ New feature (non-breaking change which adds functionality) ☑︎ Breaking change (fix or feature that would cause existing functionality to change) Checklist: ☑︎ My change requires a change to the documentation. ☑︎ I have updated the documentation accordingly. ☐ I have added tests to cover my changes. ☑︎ All new and existing tests passed. This would actually be a breaking change, as it currently stands as it would break the user imports. @omermorad you could update the NPM_TOKEN secrets value with an automation token generated under your account, as that will allow us to use this method to publish under the original package name. That way this change wouldn't have an effect on end-user behaviour but provide us the means to have automated releases, which will support our current active contributors pact-foundation/nestjs-pact ✅ All checks have passed 4/4 successful checks