Version Packages#60
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
4 times, most recently
from
July 7, 2026 08:56
cd8772c to
6224a38
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
July 7, 2026 08:57
6224a38 to
e12884f
Compare
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.
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
indexNowintegration option submitted every URL on the site on everybuild. 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(trueor 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
404istreated 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 fullresubmit;
'full'to fall back to submitting everything). Anormalizehooklets you strip per-build volatile markup (nonces, timestamps) before hashing.
Default behavior is unchanged — without
incremental, the integration stillsubmits the full set.
Also exports the underlying pure helpers (
buildUrlManifest,diffManifests,changedUrls,hashContent,serializeManifest,parseManifest) for callerswho want to compute the changed set themselves.
Patch Changes
497a720: Fix
validateImageAltfalse-positives onalt=""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 withalt=""— defeating the documented decorative-image escape hatch for any consumer usingastro:assets.The new regex (
/\salt(?:\s*=|\s|\/?>|$)/i) accepts bothalt="..."and bare-booleanalt. The leading whitespace anchor also closes a latent false-skip on attribute names likedata-alt(which the old regex matched as analtattribute).3d510e2: Embed TypeScript sources into emitted
.js.mapfiles viainlineSources: true. Without this, the published maps reference../src/*.tspaths that aren't included in the npm tarball (files: ["dist", ...]), causing Vite to warnSourcemap for ... points to missing source fileson every dev start in consumer projects. Inlining the sources keeps sourcemaps usable for debugging without shipping thesrc/directory.Updated dependencies [973a74d]
Updated dependencies [973a74d]
Updated dependencies [3d510e2]
@jdevalk/seo-graph-core@0.7.0
Minor Changes
973a74d:
buildArticlenow accepts an array forisPartOf.ArticleInput.isPartOfwas typed as a singleReference, but the shipped"Personal blog" recipe in
AGENTS.mdlinks a posting to both itsWebPageand the
BlogviaisPartOf: [{ '@id': webPage }, { '@id': blog }]. Thebuilder already emitted the value verbatim at runtime, so the array worked —
but the type rejected it, forcing callers to add an
ascast.The input type is now
Reference | Reference[]. No runtime change; existingsingle-reference callers are unaffected.
973a74d: Piece builders now return
GraphEntityinstead ofRecord<string, unknown>.assembleGraph<T extends GraphEntity>(pieces)requires each piece to be aGraphEntity, whose@typeis required. The builders (buildWebSite,buildWebPage,buildArticle,buildBreadcrumbList,buildImageObject,buildVideoObject,buildSiteNavigationElement,buildPiece) were declaredto return
Record<string, unknown>, which lacks@type— so the documentedpattern
assembleGraph([buildWebSite(...), buildArticle(...)])failedtsc/astro checkunder strict mode and forced callers to castas GraphEntity[].Every builder already produces an object with a literal
@type, so the returntype is widened to
GraphEntitywith no runtime change. Builder results — andthe arrays returned by
aggregate/createSchemaEndpointmappers — now composewith
assembleGraphwithout a cast.Patch Changes
.js.mapfiles viainlineSources: true. Without this, the published maps reference../src/*.tspaths that aren't included in the npm tarball (files: ["dist", ...]), causing Vite to warnSourcemap for ... points to missing source fileson every dev start in consumer projects. Inlining the sources keeps sourcemaps usable for debugging without shipping thesrc/directory.@jdevalk/seo-graph-scanner@0.0.3
Patch Changes
.js.mapfiles viainlineSources: true. Without this, the published maps reference../src/*.tspaths that aren't included in the npm tarball (files: ["dist", ...]), causing Vite to warnSourcemap for ... points to missing source fileson every dev start in consumer projects. Inlining the sources keeps sourcemaps usable for debugging without shipping thesrc/directory.