Set up semantic release of packages to npm about spark-packages HOT 8 CLOSED

from spark-packages.

Maybe changesets could be something to look at? It's focused on creating releases from monorepo repositories.

from spark-packages.

@believer Sure! Have never used it but I also never saw a good setup for working with releases in a package based monorepo so let's do it 😄

from spark-packages.

@JohanObrink I'll see what I can do! Do we need an organization on npm for it? Should they be published as private packages?

from spark-packages.

@believer

from spark-packages.

This process with Changesets is semi-automatic.

• You create "changesets" locally using yarn changeset. It opens a guide where you specify which package to update and what the change is. This gives us control of when a new release should be created as all changes, like minor updates or documentation changes, probably don't require a release.
• Once the change is pushed, a release PR is created using a GitHub action when unprocessed changesets exist in the repository. The PR is created only if lint and tests pass. If a PR already exists, it is updated with the new changes.
• Upon merging the PR, the changesets are consumed.

Next up, I'll add automatic publishing to npm when the PR is merged.

from spark-packages.

@believer How do you specify which package is changed?

from spark-packages.

@JohanObrink it shows a wizard where you can select one or more packages that should be updated. Here's an example screenshot:

from spark-packages.