diff options
| -rw-r--r-- | NOTICES.md | 36 | ||||
| -rw-r--r-- | deny.toml | 40 | ||||
| -rw-r--r-- | release.md | 81 |
3 files changed, 0 insertions, 157 deletions
diff --git a/NOTICES.md b/NOTICES.md deleted file mode 100644 index cbbf7cc..0000000 --- a/NOTICES.md +++ /dev/null @@ -1,36 +0,0 @@ -THIRD-PARTY SOFTWARE NOTICES - -This project incorporates components from the projects listed below. The original copyright notices and the licenses under which those components are redistributed are set forth below. - ---- - -- https://cs.opensource.google/go/go/+/refs/tags/go1.18.2:src/encoding/csv/reader.go -- https://cs.opensource.google/go/go/+/refs/tags/go1.18.2:src/encoding/csv/reader_test.go - -Copyright (c) 2009 The Go Authors. All rights reserved. - -Redistribution and use in source and binary forms, with or without -modification, are permitted provided that the following conditions are -met: - -- Redistributions of source code must retain the above copyright - notice, this list of conditions and the following disclaimer. -- Redistributions in binary form must reproduce the above - copyright notice, this list of conditions and the following disclaimer - in the documentation and/or other materials provided with the - distribution. -- Neither the name of Google Inc. nor the names of its - contributors may be used to endorse or promote products derived from - this software without specific prior written permission. - -THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS -"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT -LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR -A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT -OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, -SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT -LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, -DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY -THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT -(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE -OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. diff --git a/deny.toml b/deny.toml deleted file mode 100644 index 9284775..0000000 --- a/deny.toml +++ /dev/null @@ -1,40 +0,0 @@ -[licenses] -unlicensed = "deny" -allow-osi-fsf-free = "neither" -copyleft = "deny" -# We want really high confidence when inferring licenses from text -confidence-threshold = 0.93 -allow = [ - "Apache-2.0", - "Apache-2.0 WITH LLVM-exception", - "MIT", - "MIT-0", - "MPL-2.0", - # enum-iterator* - "0BSD", - # base16, notify - "CC0-1.0", - # Inflector, hyper-tungstenite - "BSD-2-Clause", - # inotify*, libloading, is_ci - "ISC", - # fuchsia-zircon*, instant, sourcemap - "BSD-3-Clause", - # unicode-ident - "Unicode-DFS-2016", - # portpicker - "Unlicense", - "OpenSSL", - "Zlib", - # webc (wasmer) - "BUSL-1.1", -] -[[licenses.clarify]] -name = "ring" -expression = "ISC AND MIT AND OpenSSL" -license-files = [{ path = "LICENSE", hash = 0xbd0eed23 }] - -[[licenses.clarify]] -name = "webpki" -expression = "ISC AND MIT AND OpenSSL" -license-files = [{ path = "LICENSE", hash = 0x001c7e6c }] diff --git a/release.md b/release.md deleted file mode 100644 index edf7329..0000000 --- a/release.md +++ /dev/null @@ -1,81 +0,0 @@ -# Release Documentation - -## Release npm packages - -We have a simple script to release npm packages from pnpm workspaces: `cargo xtask workspace --bump`. - -```text -? Select a package to bump -> [ ] @vercel/node-module-trace - [ ] @vercel/webpack-node-module-trace -[↑↓ to move, space to select one, → to all, ← to none, type to filter] -``` - -Press space to select the package you want to publish. -Press enter to choose the version type you want to bump: - -```text -? Select a package to bump @vercel/node-module-trace, @vercel/webpack-node-module-trace -? Version for @vercel/node-module-trace - patch - minor -> major - alpha - beta - canary -[↑↓ to move, enter to select, type to filter] -``` - -> **Note** -> -> This command will always increase the version according to the semver version. <br/> -> For example, if the current version of one package is `1.0.0`, and you choose `patch`, the version will be increased to `1.0.1`. <br/> - -> **Warning** -> -> If the version of one package is `1.0.0-beta.0`, and you choose `alpha`, the cli will panic and exit. Because the `beta` < `alpha` in semver. - -Once you have finished the bump, the script will do the following things: - -- bump the version you choose in the corresponding package -- update dependencies in other packages that depend on the package you choose -- update `pnpm-lock.yaml` file -- run `git tag -s pkg@version -m "pkg@version"` for each package - -You need to run `git push --follow-tags` to finish the release. - -## Release Turborepo - -We have a multi step release process for Turborepo right now. - -**NOTE**: The steps below _must_ be run serially, in the order specified. - -1. Create a release branch by triggering the [1. Turborepo Release (release branch)][1] workflow - - - Specify the semver increment using the SemVer Increment field (start with `prerelease`) - -2. Build the Go Binary by triggering the [2. Turborepo Release (go binary)][2] workflow. - - 1. Specify the release branch (example: `staging-1.7.0-canary.1`) in _both_ the "use workflow from", and "Staging branch to release from" fields. - -3. Build the Rust Wrapper by triggering the [3. Turborepo Release (rust binary & publish)][3] workflow. - 1. Specify the release branch (example: `staging-1.7.0-canary.1`) in _both_ the "use workflow from", and "Staging branch to release from" fields. (this should match step 2.1 above) -4. A PR is automatically opened to merge the release branch created in step 1 back into `main` - - 1. ⚠️ Merge this in! You don't need to wait for tests to pass. - - It's important to merge this branch soon after the publish is succesful - -5. `turbo-orchestrator.yml` polls `npm` every 5 mins. When a new version is detected, - [`turborepo-smoke-published.yml`][4] runs against `@latest` and `@canary` tags. - -### Notes - -- Github Release Notes are published on their own using config from `turborepo-release.yml`, - triggered by the `turbo-orchestrator` bot. -- `eslint-plugin-turbo` and `eslint-config-turbo` need to be published separately. - -[1]: https://github.com/vercel/turbo/actions/workflows/turborepo-release-step-1.yml -[2]: https://github.com/vercel/turbo/actions/workflows/turborepo-release-step-2.yml -[3]: https://github.com/vercel/turbo/actions/workflows/turborepo-release-step-3.yml -[3]: https://github.com/vercel/turbo/actions/workflows/turborepo-smoke-published.yml |