Closed ColdFire87 closed 5 months ago
npm publish uses --provider-app-version $(npx -y absolute-version). This generates a version like baa5bb-master+baa5bb.
npm publish
--provider-app-version $(npx -y absolute-version)
baa5bb-master+baa5bb
npm can-i-deploy (& npm deploy) uses npx @pact-foundation/absolute-version. This generates a version like baa5bb-master+baa5bb.SNAPSHOT.ubuntu.
npm can-i-deploy
npm deploy
npx @pact-foundation/absolute-version
baa5bb-master+baa5bb.SNAPSHOT.ubuntu
The 2 versions are hence different & can-i-deploy fails. I encountered this problem while doing the Pactflow Bi-directional tutorial at https://killercoda.com/pactflow/scenario/pactflow-bi-directional-contracts-intro
can-i-deploy
Hey thanks for the report @ColdFire87, I've updated that now.
npm publish
uses--provider-app-version $(npx -y absolute-version)
. This generates a version likebaa5bb-master+baa5bb
.npm can-i-deploy
(&npm deploy
) usesnpx @pact-foundation/absolute-version
. This generates a version likebaa5bb-master+baa5bb.SNAPSHOT.ubuntu
.The 2 versions are hence different &
can-i-deploy
fails. I encountered this problem while doing the Pactflow Bi-directional tutorial at https://killercoda.com/pactflow/scenario/pactflow-bi-directional-contracts-intro