Repository navigation
Conversation
…anual-agent-evals
docs: establish version-aware agent guidance
feat: bundle version-matched package agent references
feat: expose version-aware application context for agents
…elivery fix: protect automated project credential delivery
feat: configure hosted MCP connections independently
feat: add read-only application diagnostics for agents
feat: add version-aware setup skill and repository plugin
feat: install reproducible agent assets with the CLI
…-secrets fix(cli): protect automated provisioning secrets
test(agents): add isolated manual artifact evaluations
fix: patch TanStack Start security vulnerability
…' into codex/docs/access-control-stable
…copy docs: prepare Ravi’s v1 release announcement
…able docs: remove experimental label from access control
Write the edgestore_attribution cookie on a visitor's first page load and use its visitor ID as the PostHog distinct ID, so the dashboard can link docs visits to the account at signup. Track docs_dashboard_clicked and only create person profiles for identified users. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Register site=docs on every docs event, since docs and dashboard events now share a PostHog project. Only start PostHog in production builds so next dev never sends events to the production project. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
posthog-js already keeps the anonymous ID and first page and referrer in its default cookie on .edgestore.dev, which the dashboard reads at signup. Drop the custom attribution cookie, bootstrap ID, and beacon options; keep the production-only init, the site=docs super property, and the dashboard click event. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Share first-touch attribution with the dashboard
fix: make blog upload demo responsive on mobile
|
The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
|
raviships
changed the title
raviships
deleted the
release/promote-next-75c9734ed26aa20b8809a7c354481bed804996ba
branch
October 4, 2026 05:50
This branch was successfully deployed
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.
Promotes the selected
nextrelease directly to stable v1, including the matching docs and agent setup instructions.@edgestore/server,react,shared,sdk, andcliat1.0.0, with stable internal dependencies and changelogs.latestand use prereleases only when requested or required. Package builds generate matching agent references and CLI skill assets.nextdocs and release article. Merging deploys the production docs; the normal Release workflow publishes the five packages to npmlatest.Merge using “Create a merge commit.” This preserves the ancestry needed to synchronize
nextafterward. There is no separate RC-on-main or RC-docs step; #265 and #267 are superseded by this promotion.Ravi approved a brief interval between docs deployment and npm publication. Keep the release sequence: publish stable → enable project domains → announce after both required videos are ready.
Validation: local package build, dependency/version synchronization checks, 11 agent-reference tests, 8 hosted-agent docs tests, 6 blog tests, exact generated references and skill bytes in real package tarballs. All checks passed on
ff76b82f: full CI (format, lint, typecheck, build, runtime/type tests and docs/agent contracts), S3 and Azure storage tests, CLI smoke on Linux/macOS/Windows and the production-configured docs preview. All five stable tarballs were audited for versions, internal dependencies and available exports; quick-start, SDK and CLI install commands were verified in the deployed preview.This PR is prepared for owner merge. Stable publication and post-publication verification remain pending until then.