Project dependencies: addresses, preview stacks, Affects, and agents who know
A project can depend on others in its workspace, declared on the site (Settings → Dependencies) or in its .g1t/project.yml, which is read on every push to the default branch: dependsOn: - project: api as: API_URL Verified live with syntaqx/lab-api and automation-lab: production of automation-lab got API_URL=https://lab-api-syntaqx.g1t.page; lab-api#1's pull request listed automation-lab under Affects, and "Preview them against this change" built automation-lab-git-v2-syntaqx.g1t.page with API_URL pointing at lab-api's v2 preview. - services/projects: a dependencies table (migration 0002), cycles and unknown projects refused; dependencies, add_dependency, remove_dependency, graph and context_for_repo; .g1t/project.yml synced on pushes to the default branch, replacing what the file declared. - Deployments: builds and running apps get each dependency's address for the same environment under its variable (the same branch's preview when one is up); a project's own rows win. `stack` builds the dependents' previews against a branch's preview, in the background, so leaving the page does not cancel them. - Agents: the runner tells every agent what its repository's projects use and what uses them, and to keep dependents working or open an issue on each with create_issue. - Site: Settings → Dependencies; Dependencies on the overview; Affects and "Preview them against this change" on pull requests. - Billing copes with moving to another Stripe account: a saved customer the new account does not know is forgotten and the payment starts afresh; a plan whose subscription it does not know ends at renewal. The billing secret now holds the new Flagon, Inc. sandbox key. - Docs: Dependencies in the Projects guide; addresses of other projects and preview stacks in the Deployments guide.
No changes