Skip to content

Version Packages#60

Merged
jdevalk merged 2 commits into
mainfrom
changeset-release/main
Jul 7, 2026
Merged

Version Packages#60
jdevalk merged 2 commits into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@jdevalk/astro-seo-graph@2.1.0

Minor Changes

  • 110fc2b: Incremental IndexNow submission via a published content-hash manifest.

    The indexNow integration option submitted every URL on the site on every
    build. The IndexNow spec asks senders to submit only added/updated/deleted
    URLs, and full resubmits can trip per-host rate limits (HTTP 429).

    New opt-in indexNow.incremental (true or an options object). When enabled,
    each build hashes every eligible page into a manifest, fetches the previously
    published manifest from the live site, diffs them, and submits only the URLs
    that changed (added + updated + deleted) — then writes the new manifest into
    the build output so it ships with the deploy and becomes the next baseline.

    The previous state lives on the live site, so this works identically whether
    you build locally or in CI and needs no external store. A clean 404 is
    treated as a first run (baseline); any other fetch/parse failure is handled by
    onError ('skip' by default, so a transient blip can't trigger a full
    resubmit; 'full' to fall back to submitting everything). A normalize hook
    lets you strip per-build volatile markup (nonces, timestamps) before hashing.

    Default behavior is unchanged — without incremental, the integration still
    submits the full set.

    Also exports the underlying pure helpers (buildUrlManifest, diffManifests,
    changedUrls, hashContent, serializeManifest, parseManifest) for callers
    who want to compute the changed set themselves.

Patch Changes

  • 497a720: Fix validateImageAlt false-positives on alt="" after HTML minification.

    Astro's build pipeline (via Vite's HTML minifier) implements HTML5 §2.3.2 and drops the value from empty boolean-form attributes, so <img alt=""> in source becomes <img ... alt ...> in the rendered output. The previous regex (/\balt\s*=/i) required a literal =, so it missed the minified form and warned on every decorative image marked with alt="" — defeating the documented decorative-image escape hatch for any consumer using astro:assets.

    The new regex (/\salt(?:\s*=|\s|\/?>|$)/i) accepts both alt="..." and bare-boolean alt. The leading whitespace anchor also closes a latent false-skip on attribute names like data-alt (which the old regex matched as an alt attribute).

  • 3d510e2: Embed TypeScript sources into emitted .js.map files via inlineSources: true. Without this, the published maps reference ../src/*.ts paths that aren't included in the npm tarball (files: ["dist", ...]), causing Vite to warn Sourcemap for ... points to missing source files on every dev start in consumer projects. Inlining the sources keeps sourcemaps usable for debugging without shipping the src/ directory.

  • Updated dependencies [973a74d]

  • Updated dependencies [973a74d]

  • Updated dependencies [3d510e2]

    • @jdevalk/seo-graph-core@0.7.0

@jdevalk/seo-graph-core@0.7.0

Minor Changes

  • 973a74d: buildArticle now accepts an array for isPartOf.

    ArticleInput.isPartOf was typed as a single Reference, but the shipped
    "Personal blog" recipe in AGENTS.md links a posting to both its WebPage
    and the Blog via isPartOf: [{ '@id': webPage }, { '@id': blog }]. The
    builder already emitted the value verbatim at runtime, so the array worked —
    but the type rejected it, forcing callers to add an as cast.

    The input type is now Reference | Reference[]. No runtime change; existing
    single-reference callers are unaffected.

  • 973a74d: Piece builders now return GraphEntity instead of Record<string, unknown>.

    assembleGraph<T extends GraphEntity>(pieces) requires each piece to be a
    GraphEntity, whose @type is required. The builders (buildWebSite,
    buildWebPage, buildArticle, buildBreadcrumbList, buildImageObject,
    buildVideoObject, buildSiteNavigationElement, buildPiece) were declared
    to return Record<string, unknown>, which lacks @type — so the documented
    pattern assembleGraph([buildWebSite(...), buildArticle(...)]) failed tsc /
    astro check under strict mode and forced callers to cast as GraphEntity[].

    Every builder already produces an object with a literal @type, so the return
    type is widened to GraphEntity with no runtime change. Builder results — and
    the arrays returned by aggregate/createSchemaEndpoint mappers — now compose
    with assembleGraph without a cast.

Patch Changes

  • 3d510e2: Embed TypeScript sources into emitted .js.map files via inlineSources: true. Without this, the published maps reference ../src/*.ts paths that aren't included in the npm tarball (files: ["dist", ...]), causing Vite to warn Sourcemap for ... points to missing source files on every dev start in consumer projects. Inlining the sources keeps sourcemaps usable for debugging without shipping the src/ directory.

@jdevalk/seo-graph-scanner@0.0.3

Patch Changes

  • 3d510e2: Embed TypeScript sources into emitted .js.map files via inlineSources: true. Without this, the published maps reference ../src/*.ts paths that aren't included in the npm tarball (files: ["dist", ...]), causing Vite to warn Sourcemap for ... points to missing source files on every dev start in consumer projects. Inlining the sources keeps sourcemaps usable for debugging without shipping the src/ directory.
  • Updated dependencies [973a74d]
  • Updated dependencies [973a74d]
  • Updated dependencies [3d510e2]
    • @jdevalk/seo-graph-core@0.7.0

@github-actions
github-actions Bot force-pushed the changeset-release/main branch 4 times, most recently from cd8772c to 6224a38 Compare July 7, 2026 08:56
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 6224a38 to e12884f Compare July 7, 2026 08:57
@jdevalk
jdevalk merged commit e40de0e into main Jul 7, 2026
1 check passed
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