Maintenance: move away from `lerna publish` command

[dreamorosi]

Summary

As part of the migration off lerna we should remove our usage of lerna publish, which as the name suggests is currently used to publish the packages to the npm registry during the release workflow.

This functionality can most likely be assumed by npm workspaces without any additional dependencies, but we'll have to do some tests to verify.

Why is this needed?

See reasoning of why we're migrating off lerna in the parent issue, but ultimately removing it would allow us to do this:

 npm un lerna

removed 554 packages, changed 2 packages, and audited 1088 packages in 5s

found 0 vulnerabilities

Which area does this relate to?

Automation

Solution

No response

Acknowledgment

• This request meets Powertools for AWS Lambda (TypeScript) Tenets
• Should this be considered in other Powertools for AWS Lambda languages? i.e. Python, Java, and .NET

Future readers

Please react with 👍 and your use case to help us understand customer demand.

[dreamorosi]

Hi @sdangol, before you start working on the other issue we spoke about, we could really use your help with this one.

Before we can move off lerna publish we need to make a quick test to ensure we're publishing correctly at the first try during the next release.

Below is a plan I came up with, if you have any suggestions to simplify it while maintaining the same test fidelity please let me know:

• Set up verdaccio in a EC2 instance
• Create a sample private repo with npm 3 workspaces using @test-pkg/a, @test-pkg/b, and @test-pkg/c - one of them should be marked as private, the other two as public (the idea here is to mimic the setup we have in this repo in a very minimal way)
• Make mock release in sample repo targeting verdaccio using npm publish in a GitHub Action (you can copy almost exactly the make-release.yaml file in this repo)
• Clean up sample repo and verdaccio server
• Update make-release.yaml to use npm publish as tested instead of lerna publish

Of all the flags we're passing to lerna publish the only one that we really care about is the one about provenance, everything else can go since we always publish all the public packages at every release. You most likely won't be able to test provenance on verdaccio - that's fine.

After you make the mock release, and before you clean things up, ping me so I can check the logs of the mock release workflow and do a couple tests on the published packages as well.

Let me know if you are available or have any questions!

[sdangol]

Hi @dreamorosi, yeah you can assign this to me. I will try to explore more about this.