tldraw/scripts/vercel/build-docs.sh

#!/usr/bin/env bash
set -eux

yarn run -T lazy build-api
yarn run -T lazy refresh-everything  --filter=apps/docs
yarn run -T lazy build --filter=apps/docs
[Internal] Create build-docs.sh (#2569) Fix docs build. ### Change Type - [ ] `patch` — Bug fix - [ ] `minor` — New feature - [ ] `major` — Breaking change - [ ] `dependencies` — Changes to package dependencies[^1] - [ ] `documentation` — Changes to the documentation only[^2] - [ ] `tests` — Changes to any test code only[^2] - [x] `internal` — Any other changes that don't affect the published package[^2] - [ ] I don't know [^1]: publishes a `patch` release, for devDependencies use `internal` [^2]: will not publish a new version 2024-01-21 14:47:17 +00:00			`#!/usr/bin/env bash`
			`set -eux`

Don't check api.json files into git (#3565) These were needed when the docs lived in a different repo, but they don't any more so we can get rid of them. ### Change Type - [x] `internal` — Does not affect user-facing stuff - [x] `chore` — Updating dependencies, other boring stuff 2024-04-24 15:58:26 +00:00			`yarn run -T lazy build-api`
fix docs build (#3201) - always refresh docs content when building on CI - use local api.json files now since we don't want to use SOURCE_SHA - @steveruizok it feels kinda problematic that we check in a bunch of derived files that the docs build requires. Things can get out of sync easily, and whose responsibility is it to update them? In the future I reckon we should explore ways to remove these files from the git index as much as possible. closes #3200 ### Change Type <!-- ❗ Please select a 'Scope' label ❗️ --> - [ ] `sdk` — Changes the tldraw SDK - [ ] `dotcom` — Changes the tldraw.com web app - [x] `docs` — Changes to the documentation, examples, or templates. - [ ] `vs code` — Changes to the vscode plugin - [ ] `internal` — Does not affect user-facing stuff <!-- ❗ Please select a 'Type' label ❗️ --> - [x] `bugfix` — Bug fix - [ ] `feature` — New feature - [ ] `improvement` — Improving existing features - [ ] `chore` — Updating dependencies, other boring stuff - [ ] `galaxy brain` — Architectural changes - [ ] `tests` — Changes to any test code - [ ] `tools` — Changes to infrastructure, CI, internal scripts, debugging tools, etc. - [ ] `dunno` — I don't know ### Test Plan 1. Add a step-by-step description of how to test your PR here. 2. - [ ] Unit Tests - [ ] End to end tests ### Release Notes - Add a brief release note for your PR here. 2024-03-18 15:59:29 +00:00			`yarn run -T lazy refresh-everything --filter=apps/docs`
[Internal] Create build-docs.sh (#2569) Fix docs build. ### Change Type - [ ] `patch` — Bug fix - [ ] `minor` — New feature - [ ] `major` — Breaking change - [ ] `dependencies` — Changes to package dependencies[^1] - [ ] `documentation` — Changes to the documentation only[^2] - [ ] `tests` — Changes to any test code only[^2] - [x] `internal` — Any other changes that don't affect the published package[^2] - [ ] I don't know [^1]: publishes a `patch` release, for devDependencies use `internal` [^2]: will not publish a new version 2024-01-21 14:47:17 +00:00			`yarn run -T lazy build --filter=apps/docs`