✓ Uses Rust 2018 edition
|0.1.3||Mar 16, 2019|
|0.1.2||Feb 14, 2019|
|0.1.1||Jan 31, 2019|
|0.1.0||Jan 31, 2019|
#9 in #lambda
1,103 downloads per month
This is a monorepo containing the Official Builders provided by the ZEIT team.
There are two Channels:
|Channel||Git Branch||npm dist-tag||use example|
All PRs should be submitted to the
Once a PR is merged into the
canary branch, it should be published to npm immediately using the Canary Channel.
For the Canary Channel, publish the modified Builders to npm with the following:
For the Stable Channel, you must do the following:
- Cherry pick each commit from canary to master
- Verify that you are in-sync with canary (with the exception of the
- Deploy the modified Builders
# View differences excluding "Publish" commits git checkout canary && git pull git log --pretty=format:"$ad- %s [%an]" | grep -v Publish > ~/Desktop/canary.txt git checkout master && git pull git log --pretty=format:"$ad- %s [%an]" | grep -v Publish > ~/Desktop/master.txt diff ~/Desktop/canary.txt ~/Desktop/master.txt # Cherry pick all PRs from canary into master ... git cherry-pick <PR501_COMMIT_SHA> git cherry-pick <PR502_COMMIT_SHA> git cherry-pick <PR503_COMMIT_SHA> git cherry-pick <PR504_COMMIT_SHA> # Verify the only difference is "version" in package.json git diff origin/canary # Ship it yarn publish-stable
After running this publish step, GitHub Actions will take care of publishing the modified Builder packages to npm.
If for some reason GitHub Actions fails to publish the npm package, you may do so
manually by running
npm publish from the package directory. Make sure to
npm publish --tag canary if you are publishing a canary release!
See the Contribution guidelines for this project, it also contains guidance on interpreting tests failures.
To create your own Builder, see the Builder's Developer Reference.