[Production] Release 2026-07-07 - #129
Merged
Merged
Conversation
) * Move user-facing docs to the docs site; keep only contributor docs here developer-docs/ had a mix of user/operator/admin guides (installing a watcher, adding an instrument, managing tokens, upgrading the watcher) and reference docs (REST API, MCP server) that duplicated — or were superseded by — the polished docs site at arcadia-data-hub-docs.vercel.app. - Delete developer-docs/guides/ (adding-an-instrument, installing-a-watcher, managing-tokens, upgrading-the-watcher) and developer-docs/reference/ {api,mcp}.md — all fully covered by the docs site now. - Preserve the two pieces of dev-only content those files carried that weren't duplicated anywhere else: the S3 trigger + deploy step for adding a Lambda processor (folded into the docs site's deploying-aws-infrastructure page) and the 0022_pat_scopes wildcard-backfill rationale (added to architecture.md's design decisions). - Repoint every remaining cross-reference (READMEs, reference/*.md, watcher/pyproject.toml) at the docs site instead of the deleted files. - Add a Documentation section to AGENTS.md directing agents to the docs site for user/operator/admin questions, since developer-docs/ now only covers contributing to Data Hub itself. Co-authored-by: Cursor <cursoragent@cursor.com> * Flatten the developer-docs index in README The Guides/Reference split no longer earned its keep once guides/ shrank to a single entry — Reference also mixed genuine reference docs (watcher, lambda, shared-library) with conceptual/onboarding ones (architecture, getting-started, conventions). Flatten into one ordered list, and add the missing link to ops/run-archives.md. Co-authored-by: Cursor <cursoragent@cursor.com> * docs: Reorganize documentation * docs: Update README --------- Co-authored-by: Cursor <cursoragent@cursor.com>
The staging deploy failed because the CI role lacks s3:PutBucketCORS, which the new bucket CorsConfiguration requires. Add Get/PutBucketCORS scoped to the three data buckets, note the admin-first-deploy caveat in the docs, and add a sam-status helper to check stack state. Co-authored-by: Cursor <cursoragent@cursor.com>
Replace the hardcoded API_URLS map with per-environment URLs stored in config (`api_base_urls`), so self-hosted deployments point each of staging/production/preview at their own Data Hub without editing source. - WatcherConfig: `api_base_urls` dict + `api_base_url` property, with transparent migration of legacy scalar `api_base_url`/`watcher_id`. - CLI: prompt for the URL on `init` for every environment; switching resolves flag > stored > error and preserves other envs' URLs. - Service/client: require a URL for the active environment and fail loudly when none is configured. - Update docs and tests; bump watcher to 0.5.0. Co-authored-by: Cursor <cursoragent@cursor.com>
* Route the docs site as a microfrontend at /docs Make the web app the default application in a Vercel Microfrontends group so datahub.arcadiascience.com/docs is served by the separate docs project while the web app owns the rest of the apex domain. - Add web/microfrontends.json routing /docs/:path* to the data-hub-docs project (packageName mappings since the Vercel project names differ from the package.json names). - Wrap next.config with withMicrofrontends for asset-prefix and client-config handling. - Allow /docs in robots.txt and point crawlers at the docs sitemap, keeping the rest of the product noindex. Co-authored-by: Cursor <cursoragent@cursor.com> * Sync package-lock with @vercel/microfrontends dependency tree The initial install left `web/package-lock.json` missing the nested `@rolldown/binding-wasm32-wasi` copy of `@emnapi/*` that `@vercel/microfrontends` pulls in, so `npm ci` failed with an out-of-sync lockfile. Reconcile the lockfile so CI installs cleanly. Co-authored-by: Cursor <cursoragent@cursor.com> * Regenerate package-lock on Linux to match CI My earlier lockfile edit was generated on macOS, which prunes the Linux optional dependencies (the wasm `@emnapi`/`rolldown` fallback tree that `@vercel/microfrontends` pulls in), so `npm ci` still failed on the Linux CI runners. Regenerate the lockfile on Linux (node:24, matching CI and Vercel) so `npm ci` resolves the complete optional-dependency tree. Verified with a clean `npm ci` in a Linux container. Co-authored-by: Cursor <cursoragent@cursor.com> --------- Co-authored-by: Cursor <cursoragent@cursor.com>
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.