chore(deps): bump astro from 7.2.0 to 7.3.5 in the minor-and-patch group across 1 directory

[dependabot]

Bumps the minor-and-patch group with 1 update in the / directory: astro.

Updates astro from 7.2.0 to 7.3.5

Release notes

Sourced from astro's releases.

astro@7.3.5

Patch Changes

• #17736 2b8b2e8 Thanks @​ematipico! - Adds a new container function called renderComponent(), which renders Astro components with inlined styles and scripts.

  Users must import the component with the new ?container query string:

  import { experimental_AstroContainer } from "astro/container";
  import TodoList from "../components/TodoList.astro?container";
  const container = await experimental_AstroContainer.create();
  const _string = container.renderComponent(TodoList);

astro@7.3.4

Patch Changes

• #18063 40896ac Thanks @​adamchal! - Fixes incremental builds repeatedly rendering unchanged pages when modules or compiled CSS reference bundled assets.

• #18053 cf5d72f Thanks @​Princesseuh! - Improves the astro check error shown for TypeScript 7. The command now explains that TypeScript 7 is not currently supported and provides instructions for experimentally type-checking Astro files with TypeScript 7.1 and @astrojs/ts-content-mapper.

• #18086 795a7e4 Thanks @​ump45nose! - Fix double-escaped ampersands in Markdown image alt and title attributes. The __ASTRO_IMAGE_ round-trip now decodes the numeric (&) and named (&) character references the Markdown processors emit, so an & in an alt or title is escaped exactly once in the final HTML instead of twice.

• #18074 0429805 Thanks @​SurefireStudios! - Fix three error names that did not match their documented reference. MissingLocale, MissingIndexForInternationalization and NoManifestAvailable reported names ending in Error in the dev overlay, while their error reference pages are published under the unsuffixed names, so the name shown to users could not be found in the docs.

• #18007 2245837 Thanks @​L4XB! - Fixes the dev server re-evaluating the whole server module graph on every request. The astro:head-metadata plugin invalidated its component metadata virtual module from its own transform hook, so each evaluation of that module scheduled the next one. Adapters that run requests outside Vite's module runner, such as @astrojs/cloudflare, paid for a full re-evaluation of the server graph on every request for the lifetime of the process.

• #18096 43657c4 Thanks @​matthewp! - Fixes domain-based i18n routing to respect security.allowedDomains when selecting a locale from request host headers

• #18043 8a53a8b Thanks @​astro-factory! - Fixes image.responsiveStyles emitting invalid object-position CSS values for same-axis keyword pairs (top bottom, left right, etc.)

• #18029 c08252d Thanks @​matthewp! - Runs astro dev and astro preview in the foreground when an AI agent is detected on Windows, allowing the agent to manage the process lifetime. Pass --background explicitly to request an Astro-managed background process. Agent-inferred backgrounding remains enabled on other platforms.

• Updated dependencies [3fd16ee, 8358d59]:

  • @​astrojs/markdown-satteri@​0.4.2

astro@7.3.3

Patch Changes

• #17651 504333c Thanks @​sxzz! - Refactors internal version handling to use a smaller, ESM-native dependency

• #17942 0bc5715 Thanks @​matthewp! - Returns appropriate 400 and 404 responses from the image endpoint for invalid and missing local image paths

• #17700 b2222fc Thanks @​winklemad! - Fixes Astro.preferredLocaleList returning an empty list when a locale is configured with the object form ({ path, codes }) and the browser sends the code with different casing or an underscore, such as en-US matching a configured en-us

• #17941 394ff79 Thanks @​matthewp! - Fixes astro preview --ignore-lock (and astro dev --ignore-lock) being refused when run from an AI agent environment. The flag now starts the server in the foreground instead of erroring, since agent detection only inferred background mode and was never explicitly requested. An explicit --background combined with --ignore-lock still errors.

• #17928 3277927 Thanks @​ArmandPhilippot! - Fixes TypeScript autocompletion for getImage() to suggest all available predefined options.

... (truncated)

Changelog

Sourced from astro's changelog.

7.3.5

Patch Changes

• #17736 2b8b2e8 Thanks @​ematipico! - Adds a new container function called renderComponent(), which renders Astro components with inlined styles and scripts.

  Users must import the component with the new ?container query string:

  import { experimental_AstroContainer } from "astro/container";
  import TodoList from "../components/TodoList.astro?container";
  const container = await experimental_AstroContainer.create();
  const _string = container.renderComponent(TodoList);

7.3.4

Patch Changes

• #18063 40896ac Thanks @​adamchal! - Fixes incremental builds repeatedly rendering unchanged pages when modules or compiled CSS reference bundled assets.

• #18053 cf5d72f Thanks @​Princesseuh! - Improves the astro check error shown for TypeScript 7. The command now explains that TypeScript 7 is not currently supported and provides instructions for experimentally type-checking Astro files with TypeScript 7.1 and @astrojs/ts-content-mapper.

• #18086 795a7e4 Thanks @​ump45nose! - Fix double-escaped ampersands in Markdown image alt and title attributes. The __ASTRO_IMAGE_ round-trip now decodes the numeric (&) and named (&) character references the Markdown processors emit, so an & in an alt or title is escaped exactly once in the final HTML instead of twice.

• #18074 0429805 Thanks @​SurefireStudios! - Fix three error names that did not match their documented reference. MissingLocale, MissingIndexForInternationalization and NoManifestAvailable reported names ending in Error in the dev overlay, while their error reference pages are published under the unsuffixed names, so the name shown to users could not be found in the docs.

• #18007 2245837 Thanks @​L4XB! - Fixes the dev server re-evaluating the whole server module graph on every request. The astro:head-metadata plugin invalidated its component metadata virtual module from its own transform hook, so each evaluation of that module scheduled the next one. Adapters that run requests outside Vite's module runner, such as @astrojs/cloudflare, paid for a full re-evaluation of the server graph on every request for the lifetime of the process.

• #18096 43657c4 Thanks @​matthewp! - Fixes domain-based i18n routing to respect security.allowedDomains when selecting a locale from request host headers

• #18043 8a53a8b Thanks @​astro-factory! - Fixes image.responsiveStyles emitting invalid object-position CSS values for same-axis keyword pairs (top bottom, left right, etc.)

• #18029 c08252d Thanks @​matthewp! - Runs astro dev and astro preview in the foreground when an AI agent is detected on Windows, allowing the agent to manage the process lifetime. Pass --background explicitly to request an Astro-managed background process. Agent-inferred backgrounding remains enabled on other platforms.

• Updated dependencies [3fd16ee, 8358d59]:

  • @​astrojs/markdown-satteri@​0.4.2

7.3.3

Patch Changes

• #17651 504333c Thanks @​sxzz! - Refactors internal version handling to use a smaller, ESM-native dependency

• #17942 0bc5715 Thanks @​matthewp! - Returns appropriate 400 and 404 responses from the image endpoint for invalid and missing local image paths

• #17700 b2222fc Thanks @​winklemad! - Fixes Astro.preferredLocaleList returning an empty list when a locale is configured with the object form ({ path, codes }) and the browser sends the code with different casing or an underscore, such as en-US matching a configured en-us

• #17941 394ff79 Thanks @​matthewp! - Fixes astro preview --ignore-lock (and astro dev --ignore-lock) being refused when run from an AI agent environment. The flag now starts the server in the foreground instead of erroring, since agent detection only inferred background mode and was never explicitly requested. An explicit --background combined with --ignore-lock still errors.

... (truncated)

Commits

• c2e0164 [ci] release (#18113)
• 2b8b2e8 feat: add render component (#17736)
• 790c6f7 [ci] release (#18035)
• 9d17bf1 Update dependency obug to v3 (#18100)
• 43657c4 Fix i18n domain host validation (#18096)
• 00393ff Update dependency vitest [SECURITY] (#18026)
• 40896ac fix(incremental): resolve asset placeholders in modules or compiled CSS (#18063)
• 0429805 fix(errors): align three error names with their documented reference (#18074)
• 3eab954 [ci] format
• 795a7e4 Fix double-escaped ampersands in Markdown image alt and title attributes (#18...
• Additional commits viewable in compare view

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
uplbtools-me	Ready	Preview	Oct 5, 2026 7:25am UTC

[smmariquit]

sweep: leaving open — the deploy check is failing on this PR (In a non-interactive environment, it's necessary to set a CLOUDFLARE_API_TOKEN environment variable for wrangler to work). This looks pre-existing/environmental (Dependabot PRs don't get access to repo secrets like CLOUDFLARE_API_TOKEN) rather than caused by the astro 7.2.0→7.3.2 bump itself, which is otherwise a clean minor-and-patch, lockfile-only change. Will keep watching; may need a maintainer to confirm secret access for Dependabot runs or re-trigger after merge.

---

Generated by Claude Code

[smmariquit]

sweep: weekly re-check, same conclusion — leaving open. The deploy check is still failing (CLOUDFLARE_API_TOKEN not available in the Dependabot run context) — same pre-existing/infra issue as the other action-pin PRs in this repo, unrelated to the astro 7.2.0→7.3.2 bump itself. The version bump is a clean minor-and-patch, lockfile-only change; safe to merge once the deploy check environment issue is resolved (e.g. a maintainer reruns the check with secrets available, or the workflow is adjusted to skip that step for Dependabot PRs).

---

Generated by Claude Code

[smmariquit]

sweep: weekly re-check, same conclusion — leaving open. Bump itself (astro 7.2.0→7.3.2) is a clean minor-and-patch, lockfile/manifest-only change (package.json + package-lock.json). The deploy check is still failing with CLOUDFLARE_API_TOKEN not set — confirmed in the job log, same pre-existing/environmental issue (Dependabot runs don't get repo secrets), unrelated to this bump. Safe to merge once that secret-access gap is addressed for Dependabot runs.

---

Generated by Claude Code