Skip to content

Fix nightly release workflow #3637

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dapplion merged 1 commit into from
Jan 18, 2022
Merged

Fix nightly release workflow #3637

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
31 changes: 24 additions & 7 deletions .github/workflows/release-nightly.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,15 +42,32 @@ jobs:
# </common-build>

- name: Publish to npm registry
# from-package: Base the latest nightly ref count from NPM registry
# --no-git-reset: Do not delete code version artifacts so the next step can pick the version
# --canary: Format version with commit (1.1.0-alpha.0+81e3b443)
# --dist-tag next: Make this nightly version installable with `@next`
# --preid dev: Tag version with `dev` instead of `alpha`
# --force-publish: lerna doesn't want to publish anything otherwise - "lerna success No changed packages to publish"
# Just use lerna publish with --canary option. Using 'from-package' ignore other options
# and only compares against the verison in package.json, and skips release if already
# published.
#
# --no-git-reset:
# Do not delete code version artifacts so the next step can pick the version
#
# --canary:
# Format version with commit (1.1.0-alpha.0+81e3b443). Make sure the previous
# released tags are not lightweight("commit" type), but proper annotated ("tag" type)
# Otherwise the version canary will generate will be from last annotated tag type
# Best way to create such a tag is by using 'git tag -a' or using lerna publish!
#
# --dist-tag next:
# Make this nightly version installable with `@next`
#
# --preid dev:
# Tag version with `dev` instead of `alpha`
#
# --force-publish:
# lerna doesn't want to publish anything otherwise - "lerna success No changed packages
# to publish"
#
# NOTE: Using --preid dev.$(git rev-parse --short=7 HEAD) results in `0.24.3-dev.3ddb91d.0+3ddb91d`
run: |
node_modules/.bin/lerna publish from-package --yes --no-verify-access \
node_modules/.bin/lerna publish --yes --no-verify-access \
--canary --dist-tag next --no-git-reset --force-publish \
--preid dev
env:
Expand Down