Publish to respective package managers

[markdboyd]

npm run package builds distribution artifacts for NPM and PyPI, so we should add some scripting that publishes those build artifacts.

Open questions:

• What account would be used for publishing to each package manager?
• When/how would publishing happen?
  • Seems like having it run as part of CI would be preferable
  • Only publish if the version number has changed?

[markdboyd]

This seems interesting: https://github.com/marketplace/actions/jsii-publish

[alukach]

Currently working on this in 6/publish-packages.

My dev notes so far:

Versioning

• Ideas:
  • Each package should be versioned separately. No need to up the version (and thus have consumers upgrade) when the package hasn't changed.
  • Can we have CI manage versions? Or should this be a required part of manual edits made to each component?
    • It seems that Lerna has tooling to support managing versions via lerna version
      • If we use the conventional commit flag which includes logic to determine the correct version number based on the commit message (read more)
• Questions:
  • In a world where we have multiple versions of packages alongside one another, does that exclude of from registering releases via a Github Release? I think so.
• Suggestions:
  • To keep us moving, we may want to go with manual control over versioning right now and approach auto-versioning via CI in the future.

Publish

• Notes:
  • Lerna supports publishing via lerna publish. I'm not sure how well this plays with the distributables created by jsii-pacmak. Being that we will want to be publishing to multiple package managers, I'm leaning towards the idea that we will want to use a custom script that iterates over the directories in /packages and publishes each to the appropriate package managers.
  • While https://github.com/marketplace/actions/jsii-publish is cool, it is built to handle repos that represent a single construct. To handle publishing multiple constructs, we will likely want to use that action as an example but will need to build our own logic.
  • In an ideal world, we'll publish packages via CI and only those packages have changed (using Lerna to manage versions can help with this, I believe) when the code has been pushed to main. Someday, it may even be possible to use commit messages to instruct CI to publish alpha pre-release versions for testing.