Skip to content

feat(migrate-email): attachments for Mailjet - #519

Draft
Silthus wants to merge 26 commits into
feat/migrate-email-mailjetfrom
feat/migrate-email-mailjet-attachments
Draft

Silthus wants to merge 26 commits into
feat/migrate-email-mailjetfrom
feat/migrate-email-mailjet-attachments

Conversation

@Silthus

@Silthus Silthus commented Nov 13, 2026 •

Copy link
Copy Markdown
Contributor

Parked until after 2026-11-25. Michael chose SendGrid as the first migrate-email provider on 2026-11-14; this PR stays a draft and resumes after that date, with the slim pass from research/2026-11-14-review-bloat-retro before its next review round.

Problem

The Mailjet variant of migrate-email (#466) keeps every send that sets Attachments or InlinedAttachments on Mailjet, because PostHog's send didn't take files. The PostHog SDKs now send files from code, and #510 teaches the shared steps how. This PR maps Mailjet's own file fields onto them, so a send with an invoice, a receipt or an inline logo can move too. It also rechecks #466's claims about how each Mailjet SDK reports errors, sets timeouts, picks its Send API version and turns off its request. Those claims rested on SDK source read past Fleet's Git allowlist and one npm read, not on Mailjet's own pages.

Important

Stacked on #510 (Resend attachments), which is stacked on #486. The base is feat/migrate-email-mailjet (#466), so the diff includes #486 and #510 until its ancestors land and it is retargeted to main. Only references/mailjet/ is this PR's change; it merges #510's head 41e37f1. Merge order: #472, the providers, #486, #510, then this one.

Impact

Moved sends that carry files and arrive with migratedFrom: 'mailjet' show whether sites with files now move off Mailjet. Read it 14 days after the Wizard runs migrate as a family with this variant.

Warning

🔴 Merge risk: high · two-way door until the next context-mill release ships the skill; one-way for each app once an agent runs it, because a migration's changes persist in that app's code

  • Tier: critical: the rules decide how each moved send's errors, timeouts and Send API version are handled in apps the agent changes.
  • The diff changes only references/mailjet/mapping.md and sdk-reference.md. Until the skill ships, nobody runs it, so it changes no running code.
  • Once it ships, a site with files that stayed on Mailjet moves when Step 3 "Files" lets it. The failure path is a moved email whose files arrive differently, such as an inline image whose content ID came from its Filename. Step 8's check email sends one email with files before cutover, and a field_not_accepted puts those sites back.
  • Uncovered: the rechecked error, timeout, version and turn-off rules. Where Mailjet's pages don't say what an SDK does, the agent now reads the SDK client installed in the app instead of this file, and could misread it. A wrong read changes a moved site's error handling silently: a refused send that used to raise could be logged and skipped, or the other way round. Step 8's check email doesn't exercise an error, so the owed live run, with the fixtures listed below, is what covers this path.
  • Uncovered: no agent run of the Mailjet variant with files, and no real send of an inline file through PostHog. feat(migrate-email): move a Resend send's attachments to posthog-node #510's real send covered a file the email carries, from Resend.
  • Switch-off: revert this PR, which keeps every site with files on Mailjet again and puts feat(skills): move Mailjet sends to PostHog #466's rules back, as feat(skills): move Mailjet sends to PostHog #466 has them.

Changes

  • mailjet/mapping.md, "Fields": the Attachments and InlinedAttachments rows move both lists into PostHog's attachments, pointing to Step 3 "Files".
  • mailjet/mapping.md, new "Attachments", each field with how it maps:
    • Filename becomes the filename, as it is. Mailjet requires one.
    • ContentType (v3 Content-type, or Content-Type in Ruby's sample) becomes the content type, as it is; a type with parameters follows feat(migrate-email): move a Resend send's attachments to posthog-node #510's rule and is never stripped.
    • Base64Content (v3 Content in the reference, content in the v3 guide's samples) becomes the content, as the same Base64 string where the SDK reads one, or decoded where the SDK takes bytes only.
    • ContentID of an inline file becomes the content ID, the bare ID the HTML shows with cid:.
    • An inline file without ContentID, and every v3 inline file, takes its Filename as the content ID, since the HTML shows it with cid:<Filename>; it must keep PostHog's content ID rules from Step 3.
    • Disposition follows the list: a file in Attachments carries no content ID, and an inline file stays inline.
    • Files in Globals are added to each message's.
    • Limits: Mailjet takes a request of up to 15 MB, files included, with no file count or refused type in its reference. PostHog takes 40 MB and 10 files, inline files included, and refuses the extensions Step 3 lists.
    • Mailjet fetches no file, and a stored template holds none. A site with files that the person wants on a template made in PostHog stays (a template in PostHog takes no files).
  • mailjet/mapping.md, "The fields": Attachments and InlinedAttachments, with Globals' files, become one attachments list.
  • Corrects feat(skills): move Mailjet sends to PostHog #466's claims that rested on SDK source read past the guard or on the npm read, in its own commit (763e989). What Mailjet's pages say stays, re-cited; the rest is softened or becomes an installed-client rule. A site the installed client doesn't settle stays with the new reason mailjet client not checked, which replaces mailjet-rest version not checked and mailjet client version not checked.
    • sdk-reference.md:
      • The laravel-mailjet env names are softened to "framework packages use their own names, such as …".
      • The 400 answer carrying Messages with Status: "error" is softened: a refused message comes back in Messages with Errors[].StatusCode, a request-level error has no Messages, and the docs don't give the HTTP status of the whole call.
      • New: before the rewrite, read the installed client (node_modules, the virtualenv, vendor, the bundle, the Go module cache, NuGet) and name the file in the plan row.
      • Node.js: .request() answering { body, response }, throwing on 400 or more and on network errors, and the error's attributes are softened to result.body and the samples' err.statusCode; the rest is installed-client. The constructor is corrected to new Client and apiConnect; config host and version, the per-call config winning, v3 as the default and .request(…, false) are re-cited. The 3.x connect options and perform_api_call are installed-client. options.timeout reaching axios is re-cited to the Node.js page (30000 ms by default since v7); maxRetries and retryDelay are dropped.
      • Python: the version bands (before 1.7.0, 1.7.x, from 1.8.0), MailjetApiError and its subclasses, the three retries and ApiRateLimitError are dropped. They're replaced by the Python page's text: an HTTP error such as 400 answers a requests.Response, TimeoutError and CriticalApiError for network errors, retries on 429 and 5xx. version defaulting to v3, timeout= on the client or per call and dry_run are re-cited, without versions. api_url becomes a search hint.
      • Ruby: v3 as the default and attributes[:messages] are re-cited. end_point, per-call version:, CommunicationError, Unauthorized, BadRequest with code, the v3.1 invalid-address case and perform_api_call are installed-client.
      • PHP: the response methods are re-cited (getCount added, getBody dropped), and so is the PSR-18 transport since 2.0. "Lets Guzzle's exceptions through", the 'call' option and the 'url' host option are installed-client.
      • Go: (*ResultsV31, error), APIFeedbackErrorsV31, ErrorInfoV31, the result's message-id path, AdvanceErrorHandling and the ReplyTo/Sender types are installed-client; only what the samples show stays, including SandboxMode. SendMail and SetClient are re-cited; SendMailSMTP and the third NewMailjetClient argument become search hints.
      • .NET: TransactionalEmailResponse, MailjetServerException with HttpCode, isSandboxMode, SendTransactionalEmailsAsync and the builder's other With… names are installed-client. SendV31.Resource is re-cited as Send.Resource with ApiVersion.V3_1; MailjetResponse's members (with GetErrorInfo()), the 5 documented With… methods and the HttpClientHandler argument are re-cited.
      • US setup: only Node's host is re-cited; every other client's host option becomes a search hint in the installed client.
    • mapping.md:
      • The intro's "every SDK sends them as they are" is softened.
      • Turn-off: the three documented ways are re-cited; perform_api_call, PHP's 'call' and .NET's sandbox argument are installed-client, and a PHP false client stays unless the installed client shows the post's options send it.
      • Calls rows: Ruby per-call version:, SendV31.Resource and SendTransactionalEmailsAsync are removed, and v3 as the default is re-cited. A version the installed client decides but doesn't settle stays as can't tell which Mailjet Send API it calls.
      • "Code around the send" no longer says which SDK throws: it names what the samples show and sends the agent to the installed client.
      • Catch rows: the Node attribute names and the Go type names are softened.
      • HTTP: Python's timeout= is re-cited without "from 1.7.0"; PHP setTimeout and addRequestOption, Go WithContext and the gem's read_timeout and open_timeout are installed-client; the axios claim is re-cited to the Node.js page; the Python 60 s and PHP 15 s and 2 s defaults are dropped, and node-mailjet's 30 s is re-cited; Python's retries are re-cited without the count.
      • Errors bullets: Ruby (including the v3.1 invalid-address rule), Python from 1.8.0, Python before 1.8.0 with PHP and PostAsync, .NET SendTransactionalEmailAsync, Go, ".NET, every client" and "A site that read no result" become conditional on what the installed client does. Python's catches ApiRateLimitError becomes catches a Mailjet error its client never raised. "As Mailjet's Node.js SDK does" is dropped from the raw-HTTP bullet.

Live-run fixtures: files

The live run sends each of these through the migrated app and checks the received email, since no wording test can show that bytes and content IDs arrive intact:

  1. A v3.1 send with one Attachments file: the same bytes, filename and content type arrive.
  2. A v3.1 send with an InlinedAttachments image and a ContentID that the HTML shows with cid:: the image renders inline.
  3. An inline file without ContentID, whose HTML shows cid:<Filename>: the image renders inline.
  4. A send with files in Globals and in the message: every file arrives.
  5. A v3 send with Attachments and Inline_attachments, in the spelling the app's SDK sample uses.
  6. A content type with parameters, such as text/calendar; method=REQUEST: the site stays until PostHog takes it, as feat(migrate-email): move a Resend send's attachments to posthog-node #510 says.

Live-run fixtures: installed-client rules

Only a live run tests the agent's read of an installed client. Each rule says what to read and what decides the site; when the client isn't there or doesn't settle it, the site stays as mailjet client not checked.

  1. Node node-mailjet: which statuses and network errors reject .request().
  2. Node 3.x connect(key, secret, options): whether the options set .post's version.
  3. Node 3.x: a turn-off switch such as perform_api_call.
  4. Node 3.x: how a timeout is taken, and whether it reaches axios.
  5. Node: any retry option, counted with a site's own deadline.
  6. Python mailjet_rest: which statuses raise, with which class.
  7. Python: the retry count and statuses.
  8. Python: what timeout= limits, and whether a (connect, read) pair reaches requests as it is.
  9. Ruby gem: the error class, its subclasses and the status attribute; whether a network failure comes as the HTTP library's error.
  10. Ruby: refused sends answered in the body instead of raised, such as a v3.1 invalid address.
  11. Ruby: whether Send.create takes version:.
  12. Ruby: the host setting and perform_api_call.
  13. Ruby: read_timeout and open_timeout on a connection the code builds, and whether the installed version reads them.
  14. PHP vendor and composer.lock: what a network failure lets through, Guzzle or PSR-18.
  15. PHP: whether post options such as 'call' override a false client.
  16. PHP: the host option, and 1.x setTimeout and setConnectionTimeout.
  17. Go module: the error types and the statuses each stands for.
  18. Go: where the result holds the message id, field names beyond the samples, and a send context such as WithContext.
  19. .NET Mailjet.Api: whether SendTransactionalEmailAsync returns, throws, or splits by Messages.
  20. .NET: a sandbox argument and a multi-send method.
  21. .NET: which Send API each send resource calls from 2.0.
  22. .NET: whether MailjetClient lets HttpRequestException and TaskCanceledException through or wraps them.
  23. .NET: builder With… names beyond the 5 documented.
  24. Every client: the host option for Mailjet's US setup.

How did you test this code?

  • Lane gate on 2eb48c6: vitest run scripts passes 344 tests, and node scripts/build.js builds every skill, migrate-email-mailjet included.
  • Sources for the file fields, all Mailjet's own pages: the Send API v3.1 reference (postsendv31: Attachments and InlinedAttachments of { ContentType, Filename, Base64Content }, optional unique ContentID, Globals, a 15 MB request), the v3 reference (postsendv3: Attachments and Inline_attachments of { Content-type, Filename, Content }), the v3.1 guide "Send attached files" (cid: images), and the template content reference (text part, HTML part, MJML and headers, no files).
  • Sources for the corrected feat(skills): move Mailjet sends to PostHog #466 claims, all on dev.mailjet.com: the SDK pages for Node.js, Python, Ruby, PHP, Go, C# and Java; the v3.1 and v3 send guides (basic send, global payload, attached files, sandbox mode, Send API errors); and the status codes page.
  • The SDKs' source wasn't read: the mailjet GitHub org isn't on Fleet's Git allowlist, so the claims rest on the pages above only. No package from a registry is cited.
  • Left as they were, unconfirmed by the live pages: the api.us.mailjet.com host (no live page names it; the rule reads whatever host the app names), the MonitoringCategory row (always keeps the site), and the framework packages and in.mailjet.com, which aren't SDK source.
  • Owed proof: a live run of the variant with files and the fixtures above, after the ancestors land; the gate and ReviewHog run after the retarget.

Decisions

Question Answer Who Where
Attachments for every provider A follow-up PR per provider off its provider PR, merged after #510 👤 Human this PR
Sources for the file fields Mailjet's own API reference and docs pages only; SDK source not read, since the mailjet org isn't on Fleet's allowlist 👤 Human this PR
#466's claims resting on SDK source read past the guard or on npm #466 lands as it is; corrected here against dev.mailjet.com in a separate commit 👤 Human this PR
SDK behaviour Mailjet's pages don't describe The agent reads the installed client in the app and names the file; the site stays only when that doesn't settle it, with mailjet client not checked 👤 Human this PR
An inline file without ContentID, and v3 inline files The content ID is the Filename, as Mailjet's cid: rule says, held to PostHog's content ID rules 🤖 Agent this PR
Python's error rules Mailjet's current Python page says 400 and 404 answer a response; the version bands are gone and the installed client decides the rest 🤖 Agent this PR
Merge-risk tier Critical, as #466: the rechecked rules decide moved sites' error handling, uncovered until the live run 🤖 Agent this PR

Involvement: the attachments mapping and the recheck of #466's claims were written by agents (Claude Opus 5.5) against Mailjet's docs pages. Cross-family review (GPT-6.1 Sol) with fleet proof review --scope fixes from the merge of #510: round 1 raised two findings, the v3 file content's other spelling (fixed in 2eb48c6) and an outside-in trial of sends with files (answered as the owed live run, with the file fixtures above). Owed proofs recorded: live run, prod shape and shadow diff, for the gate after the retarget.

🤖 Generated with Claude Code

Silthus and others added 25 commits November 9, 2026 12:29
…opens_and_clicks

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…_and_clicks

PostHog never tracks clicks on a code send, so click tracking that is off needs nothing.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Replace track_opens_and_clicks with tracking in the rewrite step and
every SDK's rewrite file. A provider's open tracking that is off turns
off the opens switch only, so engagement events stay on. The skill
never turns on click tracking, because a link can carry a token, and
it notes sites whose provider tracked clicks for the report.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ates

Use the Go, Rust and .NET names for tracking. A site that moves to a
template made in PostHog sends no tracking, because the template uses
its own setting, so the report asks the person to check it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…o sensitive

A code send takes an optional sensitive flag, and its clicks follow it
unless tracking sets them. The skill marks a send sensitive when the old
call turned off click tracking for that email or marked it sensitive. It
never marks a send as not sensitive, and drops the claim that clicks are
always off by default for code sends.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A code send that leaves sensitive out takes the setting of a PostHog
template with the same key. The skill can't see the project's templates
or tell whether a link carries a token, so a key that matched a template
without protection would start rewriting a reset link. Pin the flag on
every code send, and say so in the report.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ack-opens-and-clicks

Keeps the base's error-handling rules, setup and write-down additions,
and Elixir's named-instance send, with this branch's tracking and
sensitive rules on top. Step 7 now turns opens off from the plan note
instead of waiting for the person's yes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A site whose emails had no open pixel, or whose provider's open tracking
nobody can confirm, now moves with the opens switch off instead of
staying or waiting for the person's yes. The plan notes it as opens off
with its reason, and the report lists those sites, the clicks PostHog no
longer counts, and that every code send is marked sensitive.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Resend's attachments map to the send's attachments in posthog-node:
filename, content, content type and inline content ID. A file with a
path, no filename, a refused extension, or more than 10 files keeps the
site on Resend, as do sites outside JavaScript and TypeScript. Step 8
sends an email with files when a moved site has them, and puts those
sites back when PostHog doesn't take files from the project yet.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Step 3 decides when a site with files stays, whatever the provider, and
lists every extension PostHog refuses. Resend's mapping keeps only its
own file fields. The report says what would let a staying site move.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…nd-clicks' into feat/migrate-email-resend-attachments

# Conflicts:
#	context/skills/migrate-email/references/9-report.md
#	context/skills/migrate-email/references/resend/mapping.md
Step 7 says what every SDK's code send does with files: the 10-file and
40 MB limits, the upload before the send, and its errors. Each rewrite
file names its SDK's field and the form its content takes, since some
take only bytes and some read any text string as Base64. The bundled
api.md may still call attachments unavailable, so the steps win for
files.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… list

A provider with no suppression list of its own, such as a mailbox
provider behind an SMTP host, has no list that grows while sites stay.
Step 5 writes that into the plan, and the report then leaves out the
weekly re-import ask.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A run of migrate-email-resend on an app with a calendar invite showed
where the steps fell short. They now cover:

- preflight when the MCP sees another project, or the app already
  sends code emails
- a PostHog key under the app's own name, or in the hosting platform's
  environment
- code and docs around the sends: provider-key switches, counts and
  limits, promises in legal docs and specs, and the app's own PostHog
  sends, whose engagement setting moved sends follow
- a send moved into a runtime the SDK runs in, such as a Convex
  "use node" action
- a deadline that now limits each request of a send with files
- an idempotency key built from a hash of the request body
- tests of sends with files: the upload requests, and hashing under a
  faked clock

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- preflight: an app that already sends code emails wins over an MCP
  that can't see the project; suppressions never import into another
  project
- Step 3 reads the rewrite file's send for the files check, and counts
  the release Step 7 would install
- the email client splits a shared config function, and goes in the
  file of the runtime the send runs in
- one template key for a site that sends several kinds of email
- a used-up quota that the old code retried as a 429 is noted
- tests: answer at once under a faked clock, answer the app's own
  PostHog capture, assert on the added fields, and keep the Node digest
  stub in a setup file outside Convex's folder
- the report's notes placeholder closes where it should

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…pp's own distinct ID helper

Also reads Step 5's MCP check from what Step 2 found, not what it recorded.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… a legal text

Run 4 worked around both by hand within Step 8.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ce PostHog takes them

The real send on prod-eu refused `text/calendar; charset=utf-8;
method=REQUEST` with `not_mime_type`: PostHog takes a bare type only.
Taking `method` out makes a mail app show a calendar invite as a file.
Step 3 marks such a site, Step 8's check email decides, and a refusal
puts the site back on the provider rather than stripping the
parameters.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…nt ID in Step 3

A filename takes at most 255 characters and no path separator or control
character (unsafe_filename), a content type at most 78 characters, and a
content ID at most 78 characters and no angle bracket or control character
(unsafe_content_id), as code_send_fields.py on PostHog's master refuses them.
A site whose value breaks one stays on its provider with a reason, so each
provider's attachments follow-up points here instead of restating them.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… content cell

Run 5 (Steps 1 to 3 on a fixture with three Resend sends with files) held
a user-built filename and passed a fixed one, as the header rules mean, but
also held `contentId: "<logo>"`, which Resend's mapping already turns into
the bare `logo` the HTML shows. The rules now hold for the value the send
passes after the mapping. The re-run moved that site and still held the
user-built filename. Each file of a moving site now goes in the plan row's
content cell, where both runs had to guess.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ailjet-attachments

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Attachments and InlinedAttachments (v3: Attachments, Inline_attachments)
become PostHog's attachments: Filename, ContentType and the Base64 content
as they are, and an inline file's ContentID, or its Filename where it has
none, as the content ID. Step 3's Files rules decide what stays; a template
made in PostHog takes no files. Sources: Mailjet's Send API v3.1 and v3
reference pages.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…read the installed client

The Mailjet references carried error, timeout, version and turn-off rules
that rested on SDK source read past Fleet's Git allowlist and on one npm
read. Each now cites dev.mailjet.com, is softened to what Mailjet's pages
say, or tells the migrating agent to read the SDK client installed in the
person's app and name the file it read. A site the installed client
doesn't settle stays with the reason `mailjet client not checked`.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown

🧙 Wizard CI

Run the Wizard CI and test your changes against wizard-workbench example apps by replying with a GitHub comment using one of the following commands:

Test all apps:

  • /wizard-ci all

Test all apps in a directory:

  • /wizard-ci ai-observability
  • /wizard-ci basic-integration
  • /wizard-ci feature-flags
  • /wizard-ci mcp-analytics
  • /wizard-ci replay-vision
  • /wizard-ci revenue
  • /wizard-ci self-driving
  • /wizard-ci warehouse
  • /wizard-ci warehouse-seeded

Test an individual app:

  • /wizard-ci ai-observability/anthropic
  • /wizard-ci ai-observability/google-adk
  • /wizard-ci ai-observability/groq
Show more apps
  • /wizard-ci ai-observability/manual-capture
  • /wizard-ci ai-observability/openai
  • /wizard-ci ai-observability/openai-agents
  • /wizard-ci ai-observability/opentelemetry
  • /wizard-ci ai-observability/vercel-ai
  • /wizard-ci basic-integration/android
  • /wizard-ci basic-integration/angular
  • /wizard-ci basic-integration/astro
  • /wizard-ci basic-integration/django
  • /wizard-ci basic-integration/fastapi
  • /wizard-ci basic-integration/flask
  • /wizard-ci basic-integration/flutter
  • /wizard-ci basic-integration/javascript-node
  • /wizard-ci basic-integration/javascript-web
  • /wizard-ci basic-integration/laravel
  • /wizard-ci basic-integration/next-js
  • /wizard-ci basic-integration/nuxt
  • /wizard-ci basic-integration/python
  • /wizard-ci basic-integration/rails
  • /wizard-ci basic-integration/react-native
  • /wizard-ci basic-integration/react-router
  • /wizard-ci basic-integration/sveltekit
  • /wizard-ci basic-integration/swift
  • /wizard-ci basic-integration/tanstack-router
  • /wizard-ci basic-integration/tanstack-start
  • /wizard-ci basic-integration/vue
  • /wizard-ci feature-flags/django
  • /wizard-ci feature-flags/next-js
  • /wizard-ci mcp-analytics/custom-dispatcher
  • /wizard-ci mcp-analytics/go-sdk
  • /wizard-ci mcp-analytics/python-sdk
  • /wizard-ci mcp-analytics/ruby-sdk
  • /wizard-ci mcp-analytics/rust-sdk
  • /wizard-ci mcp-analytics/typescript-sdk
  • /wizard-ci replay-vision/javascript-node
  • /wizard-ci replay-vision/next-js
  • /wizard-ci replay-vision/react-vite
  • /wizard-ci revenue/stripe
  • /wizard-ci self-driving/astro
  • /wizard-ci self-driving/fastapi
  • /wizard-ci self-driving/nuxt
  • /wizard-ci self-driving/react-router
  • /wizard-ci self-driving/sveltekit
  • /wizard-ci warehouse/monorepo-env
  • /wizard-ci warehouse/multi-source-next
  • /wizard-ci warehouse/stripe-node
  • /wizard-ci warehouse/zero-source
  • /wizard-ci warehouse-seeded/next-stripe
  • /wizard-ci warehouse-seeded/next-stripe-declined

Test against a wizard branch:

  • /wizard-ci all wizard:my-branch

Add wizard:<branch> to any command above to pin the wizard branch. It defaults to main.

Results will be posted here when complete.

… file's fields

Mailjet's v3 reference names a file's content `Content`, while its v3
guide's samples use `content`, Ruby's `Content-Type` and
`inline-attachments`, and Go's struct `ContentType` and `Content`. The
mapping now treats each spelling as the same field.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant