chore: switch to nx [EXT-7081]#2883
Conversation
| if: inputs.os != 'windows-latest' | ||
| shell: bash | ||
| run: npm ci && npm run bootstrap | ||
| run: npm ci |
There was a problem hiding this comment.
no longer need lerna bootstrap step
| GIT_COMMITTER_EMAIL: ${{ steps.vault.outputs.GIT_COMMITTER_EMAIL }} | ||
|
|
||
| - name: Version (canary branch) | ||
| - name: Push release commit + tags (canary) |
There was a problem hiding this comment.
in order to support canary releases on a dist-tag other than latest in npm we need to separate some of the nx life cycle commands so that we can call nx release publish --tag=canary. But this means that after we run the version + changelog + skip-publish via nx release that we have tags and a commit that has not been pushed.
This step pushes those commits
| "build": "nx run-many -t build", | ||
| "prepare-release": "nx release --verbose --skip-publish", | ||
| "prepare-release:canary": "nx release --preid alpha --verbose --skip-publish", | ||
| "publish-packages": "nx release publish --dry-run", |
There was a problem hiding this comment.
before I mess anything up in our public packages I want to do one last test in canary after this is main
| exit $LASTEXITCODE | ||
| } | ||
|
|
||
| - name: Disable Nx daemon |
There was a problem hiding this comment.
I assume this is all lerna nonsense and that's why it's being removed?
There was a problem hiding this comment.
yeah, it was some suggestions around some of the lerna + nx stuff to help with the windows builds
2 participants
I was able to canary to publish the 4 packages, this PR is me porting that code to a chore branch.
I still have publishes on main set to dry-run because I need the release.yaml file in main before I can do one last test in canary.
@contentful/app-scripts: GitHub, NPM
@contentful/create-contentful-app: GitHub, NPM
@contentful/react-apps-toolkit: GitHub, NPM
create-contentful-app: NPM