Skip to content

v0.7.0 — More AI bots + integration converter

Choose a tag to compare

View all tags
@aagarwal1012 aagarwal1012 released this 20 May 19:05
· 69 commits to main since this release
v0.7.0
e048a2c
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Highlights

Two features land together in this release:

  • Broader AI bot coverage — the crawler registry now detects DeepSeek, Anthropic's new Claude-SearchBot and Claude-User, Meta's ExternalFetcher, and Perplexity-User. If any of these hit your site, they now get the markdown twin instead of HTML soup.
  • integrationConverter — a new built-in converter for marketplace-style "Connect X to Y" pages (vendor, categories, capabilities, optional setup, pricing, requirements). Drop converter: "integration" into an Astro or Next.js collection and integration pages get the same battle-tested markdown layout as blog posts.

No breaking changes. Drop-in upgrade from 0.6.x.

What's new

@dualmark/core@0.7.0

  • Extend the AI Agent Registry with 5 new bots (6155878):
    • DeepSeekBot (DeepSeek)
    • Claude-SearchBot (Anthropic — search-time fetcher)
    • Claude-User (Anthropic — claude.ai on-demand fetch)
    • Meta-ExternalFetcher (Meta — user-action fetch from Meta AI)
    • Perplexity-User (Perplexity — user-action fetch)
  • Tighten the Meta-ExternalFetcher UA pattern to avoid false positives (0377a0e) and classify its purpose as user-action rather than training (951f373) — matches Meta's published bot semantics.
  • AEO spec AI Agent Registry table is synced with the new entries.

@dualmark/converters@0.7.0

  • New: integrationConverter (dbd8ef4) for marketplace integration pages. Handles:
    • Vendor and integration metadata
    • Categories + capabilities
    • Optional setup steps, pricing, and requirements blocks
    • Same brand-footer + breadcrumb conventions as the other converters
  • Registered as the built-in integration resolver in both @dualmark/astro and @dualmark/nextjs — no config beyond converter: "integration".
  • Refactor: integration categories are now a structured field with a brandFooter test (42cc5f8).

@dualmark/astro@0.7.0, @dualmark/nextjs@0.7.0, @dualmark/cli@0.7.0, @dualmark/cloudflare@0.7.0

Version bumps to pick up the new core + converters (and the integration resolver registration in astro / nextjs). No API changes.

Upgrade

# Astro
bun add @dualmark/astro@^0.7.0

# Next.js
bun add @dualmark/nextjs@^0.7.0

# Cloudflare
bun add @dualmark/cloudflare@^0.7.0

# CLI
bun add -g @dualmark/cli@^0.7.0

To use the new integration converter:

// astro.config.mjs
dualmark({
  siteUrl: "https://yourcompany.com",
  collections: {
    integrations: { converter: "integration" },  // ← new
  },
});

Verified

  • ✅ All 313 tests pass across @dualmark/* packages
  • ✅ Typecheck clean
  • ✅ Conformance E2E: examples/astro-cloudflare-full still 125/125, examples/nextjs-app-router 120/125

Full changelogs

Full diff: v0.6.0...v0.7.0

Assets 2
Loading