[pull] main from fern-api:main#744
Merged
Merged
Conversation
…15929) Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
* chore: publish JSON Schema for fern.yml Generate a JSON Schema from the Zod FernYmlSchema using z.toJSONSchema() and commit it as fern-yml.schema.json so it can be served at https://schema.buildwithfern.dev/fern-yml.json for IDE integrations. - Add packages/cli/config/scripts/generate-jsonschema.mjs - Add fern-yml:jsonschema script to root package.json - Include fern-yml:jsonschema in the jsonschema aggregate script - Add unreleased changelog entry Co-Authored-By: federico <federico@buildwithfern.com> * fix: sort imports in generate-jsonschema.mjs Co-Authored-By: federico <federico@buildwithfern.com> * chore: regenerate fern-yml.schema.json from latest source Co-Authored-By: federico <federico@buildwithfern.com> * chore(cli): generate fern-yml schema via fern schema --output Add --output to fern schema for CI check-in of fern-yml.schema.json and remove the standalone generate-jsonschema.mjs script. Co-authored-by: Cursor <cursoragent@cursor.com> * chore(cli): refresh fern-yml.schema.json after merging main Include release in self-hosted git output mode enum (main #12277). Co-authored-by: Cursor <cursoragent@cursor.com> --------- Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> Co-authored-by: federico <federico@buildwithfern.com> Co-authored-by: Federico Zarantonello <fedezara2001@gmail.com> Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Swimburger <3382717+Swimburger@users.noreply.github.com>
…#15939) Restructures the buildwithfern/cli Sentry triage automation. - Move automation/sentry-triage/ to .devin/automation/sentry-triage/ so the Devin skill is discoverable from the standard skills location. - Split the monolithic ledger.json into one file per shortId (ledger/<SHORT_ID>.json) with a shared ledger/_meta.json for repo-wide constants. Eliminates merge conflicts when parallel subagent branches update disjoint issues. - Replace AGENT.md with SKILL.md (host-agnostic skill: works for Devin's managed Devins and Cursor's Task tool) and SUBAGENT_CONTRACT.md, which is passed to each spawned subagent. Classification authority lives in the subagent; the parent only does cheap structural decisions (ledger filter, dedupe, grouping hypothesis). - Add scripts/find-existing-pr.sh for cheap PR-dedupe lookups during triage, so the parent does not re-open PRs that already exist for a shortId. - Update CLAUDE.md Troubleshooting section to point at the new locations.
* `validateBasepathAlignment` * Stripe custom domain protocol * Test * Add changelog entry
## Summary - Adds per-file ledger rows for docs YAML parser Sentry issues that are already covered by merged fixes. - Records shipped dispositions and links each short ID to the merged PR that addressed its call site. ## Test plan - Verified referenced PRs #15698 and #15937 are merged. - Verified no open `fix/cli-sentry-triage/*` PRs have ledger-file collisions. - Pre-commit filename check passed. Made with [Cursor](https://cursor.com)
Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
* fix(cli): CLI-3R handle Posthog ID storage errors Keep CLI telemetry non-blocking when a user environment prevents persisting the Posthog distinct ID. * chore(internal): record CLI-3R triage PR Link the shipped Sentry triage ledger row to its pull request.
* fix(cli): CLI-4P classify undefined server env refs Treat invalid REST endpoint server references as validation errors so user-authored environment mismatches are not reported to Sentry as internal conversion failures. Co-authored-by: Cursor <cursoragent@cursor.com> * chore(cli): record CLI-4P triage PR Record the PR URL in the CLI-4P Sentry triage ledger row now that the fix is open. Co-authored-by: Cursor <cursoragent@cursor.com> --------- Co-authored-by: Cursor <cursoragent@cursor.com>
* fix(cli): CLI-4M swallow cli-v2 EPIPE stream errors Treat stdout/stderr EPIPE events as pipe-boundary noise in the cli-v2 terminal logger so Unix pipe closures do not reach Sentry as uncaught internal errors. Co-authored-by: Cursor <cursoragent@cursor.com> * chore(cli): CLI-4M update Sentry triage ledger Record the cli-v2 EPIPE stream boundary fix and link the PR for the shipped Sentry triage row. Co-authored-by: Cursor <cursoragent@cursor.com> --------- Co-authored-by: Cursor <cursoragent@cursor.com>
…eHttp\ClientInterface` (#16006) Co-authored-by: will.kendall@buildwithfern.com <wpk235@gmail.com> Co-authored-by: Niels Swimberghe <3382717+Swimburger@users.noreply.github.com>
Co-authored-by: Swimburger <3382717+Swimburger@users.noreply.github.com>
Co-authored-by: dsinghvi <10870189+dsinghvi@users.noreply.github.com>
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
5 participants
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.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )