`lerna publish` doesn't publish due to no change since last release in CI

Hello,

I am trying to publish packages in travis CI for my project, along with other deployment processes. For my setup, I create a tag with a new version for the project and the deployments are triggered on every new tag. I want to publish the packages for that tag in the CI.

I use lerna publish from-git --force-publish=* --no-git-tag-version --no-push --yes to publish but it doesn’t work, saying that there are no changes to publish.

Is there something I am missing, or is it not possible to achieve this with lerna?

[alexjsdev]

so i have a question that i can’t seem to find the answer too… I changed the root babel config that is used by all the packages in my lerna monorepo, how do i get lerna to republish (which is when it will re-transpile) all the packages so they will be using my latest babel config? Since my babel config is outside of the packages/ directory, lerna is saying there are no changes to publish…

Edit: i’m an idiot… --force-publish=* is all i needed to pass to the lerna publish command, but i thought it was not an option since it’s in the docs (and CL help info) only for lerna version… i think i now understand that lerna publish, runs lerna version as part of what it does… guess i was holding it wrong.

[evocateur]

collect-updates is where the rubber hits the road. But in general terms, once we’ve identified the subpaths where packages live, we just loop through them and run git diff --name-only ${PREVIOUS_TAG} -- packages/${PACKAGE} and if there are changes that aren’t ignored we add them to the list of packages to operate on.

Deceptively simple.