Repository navigation
docs(pages): cover the v0.0.54 changes - #797
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01M1cykCQdN5QWWVb3FLTkG7
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
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.
Summary
Rewrites the pages the marfa v0.0.54 docs issues name: read-only types at connector registration and the
read_onlyitem field, the type-conflict report for a shipped type, exception reports that need only the PostHog settings withOTEL_SDK_DISABLED, and the connector quiet-run guidance.Closes #782, closes #785, closes #789, closes #784.
Changes
run/telemetry.mdx: exception reports need onlyMARFA_POSTHOG_HOSTandMARFA_POSTHOG_PROJECT_TOKEN;OTEL_SDK_DISABLEDturns off traces, logs and exceptions; the https host rule and its start warning;error_reporting_enabledstops reports and notices without a restart.build/connector-pull-and-push.mdxwas over the guide limit once the new sections went in, so it is now two guides:build/connector-pull.mdx("Pull from a vendor", with "Keep a quiet run light" and "Declare the types you don't carry back") andbuild/connector-push.mdx("Carry changes back"). Every link to the old page, andbuild/meta.json, now name the new pages.(start)/connectors.mdx: a connector says which types it holds read only, and items readread_only: true.run/upgrade.mdx: new section "Types a new build leaves in conflict" (conflictsinGET /types, the start warning, the refused re-registration and the fix).catalog/(types)/type-rules.mdx: links a parent change from a new build to that section.Testing
pnpm testpasses exceptsync-changelog.test.ts, which fails in this sandbox for want of network and is unrelated. The content lint checks every link and anchor. Facts checked againstconformance/spec/(items/read-only-*,connectors/read-only-types-*,types/conflict-*,instance/telemetry-*) andopenapi.jsonat v0.0.54.Notes for reviewers
The old address
/build/connector-pull-and-pushgets no redirect. #794 stays open: the kit does not yet sendread_only_types(withmarfa/marfa-connectors#331 is a draft), so the guide documents the registration field and says the kit does not declare it. #793 stays open: withmarfa/marfa#2602 is not in v0.0.54.Checklist
Generated by Claude Code