Skip to content

chore(deps): bump astro to 7.4.x and rebuild its patch - #6435

Merged
daggerstuff merged 1 commit into
stagingfrom
churn/astro-742
Oct 30, 2026
Merged

daggerstuff merged 1 commit into
stagingfrom
churn/astro-742

Conversation

@daggerstuff

@daggerstuff daggerstuff commented Oct 30, 2026 •

Copy link
Copy Markdown
Owner

Summary

Bumps astro to 7.4.x on top of the vite 8 workspace (#6434) and rebuilds the astro patch for the new upstream layout.

  • astro 7.4 imports transformWithOxc from vite, so it requires the vite 8 migration that just landed on staging.
  • astro 7.4 reformatted dist/core/build/plugins/plugin-manifest.js (tabs + shifted hunk offsets), so the existing versionless patches/astro.patch no longer applies (ERR_PNPM_PATCH_FAILED). The patch is rebuilt against 7.4 with the same two guards (missing PAGE_SCRIPT_ID entry).

Why

This is the unblocker for dependabot #6419 (dev-deps group), which cannot install or build until staging is on astro 7.4 with a matching patch.

Verification

  • pnpm install --frozen-lockfile applies the rebuilt patch (new patch_hash recorded in the lockfile); pnpm install --lockfile-only --frozen-lockfile passes.
  • pnpm run build completes locally under node 24 with astro 7.4.4 + vite 8.3.5.
  • Full CI on this PR is the authoritative gate.

Summary by Sourcery

Upgrade Astro to 7.4.x and rebuild its patch for the updated upstream distribution layout.

Bug Fixes:

  • Update the Astro patch so dependency installation succeeds with the Astro 7.4 package layout while preserving the existing manifest guard behavior.

Enhancements:

  • Upgrade Astro to the 7.4.x release line and refresh the lockfile for compatibility with the Vite 8 workspace.

astro 7.4 imports transformWithOxc from vite, so it needs the vite 8
workspace from the migration PR. 7.4 also reformatted
dist/core/build/plugins/plugin-manifest.js (tabs), so the existing
versionless astro patch no longer applies; rebuild it against 7.4 with
the same two guards (missing PAGE_SCRIPT_ID entry).
@vercel

vercel Bot commented Oct 30, 2026 •

Copy link
Copy Markdown
Contributor

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

Project Deployment Actions Updated
pixelated Ready Ready Preview Oct 30, 2026 2:54am UTC

Request Review

@sourcery-ai

sourcery-ai Bot commented Oct 30, 2026 •

Copy link
Copy Markdown
Contributor
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR upgrades Astro to 7.4.2 for compatibility with the Vite 8 workspace, rebuilds its patch against the changed upstream layout without altering the two existing PAGE_SCRIPT_ID safeguards, and refreshes lockfile resolutions and patch metadata. Review the patch semantics, lockfile consistency, and installation/build verification in CI.

File-Level Changes

Change Details Files
Upgrade Astro to the 7.4.x line and refresh the dependency lock metadata for the Vite 8 workspace.
  • Raise the Astro development dependency from 7.3.5 to 7.4.2.
  • Update resolved packages and patch metadata in the lockfile to match the new dependency graph and rebuilt patch.
package.json
pnpm-lock.yaml
Rebuild the Astro patch against the 7.4 upstream distribution layout while preserving the existing compatibility guards.
  • Regenerate the versionless patch after Astro reformatted the manifest plugin output.
  • Retain both guards for a missing PAGE_SCRIPT_ID entry.
  • Record the new patch content and hash so frozen installs apply successfully.
patches/astro.patch

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@github-actions

Copy link
Copy Markdown

px Advisor Review

Risk: unknown

No summary available

No findings.

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've found 1 issue

Prompt for AI Agents
Please address the comments from this code review:

## Individual Comments

### Comment 1
<location path="package.json" line_range="475" />
<code_context>
     "@vitest/eslint-plugin": "^1.6.27",
     "agents": "^0.28.1",
-    "astro": "^7.3.5",
+    "astro": "^7.4.2",
     "astro-eslint-parser": "^3.2.0",
     "astro-robots-txt": "^1.0.0",
</code_context>
<issue_to_address>
**Astro stack guidance becomes stale**

When the updated dependency and lockfile are used, the dependency now resolves to Astro 7 while the repository records Astro 6 as its frontend stack, so maintainers following that guidance get an outdated platform description.

Update the Astro version in the corresponding repository knowledge entry to reflect the new stack.
</issue_to_address>

Fix all in Cursor

Sourcery assessment

Approved.


Sourcery is free for open source - if you like our reviews please consider sharing them ✨

Comment thread package.json
"@vitest/eslint-plugin": "^1.6.27",
"agents": "^0.28.1",
"astro": "^7.3.5",
"astro": "^7.4.2",

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚪ Low · Astro stack guidance becomes stale

When the updated dependency and lockfile are used, the dependency now resolves to Astro 7 while the repository records Astro 6 as its frontend stack, so maintainers following that guidance get an outdated platform description.

Update the Astro version in the corresponding repository knowledge entry to reflect the new stack.

Prompt for AI agents
In `package.json` at line 475:

**Astro stack guidance becomes stale**

When the updated dependency and lockfile are used, the dependency now resolves to Astro 7 while the repository records Astro 6 as its frontend stack, so maintainers following that guidance get an outdated platform description.

Update the Astro version in the corresponding repository knowledge entry to reflect the new stack.

From AGENTS.md L92:

- **Frontend / SSR**: Astro 6 + React 19 (TypeScript, Tailwind CSS)

Fix in Cursor

@github-actions

Copy link
Copy Markdown

Lighthouse CI Results

Routes audited: /, /dashboard?perf=1, /training-session

Thresholds: Performance ≥90 | Accessibility ≥90 | Best Practices ≥85

Reports

  • lhr-1793328886837
  • lhr-1793328899427
  • lhr-1793328911580
  • lhr-1793328922844
  • lhr-1793328934054
  • lhr-1793328945231
  • lhr-1793328956472
  • lhr-1793328967742
  • lhr-1793328978909

Reports are also available as workflow artifacts

@daggerstuff
daggerstuff merged commit b624bd2 into staging Oct 30, 2026
40 of 44 checks passed
@daggerstuff
daggerstuff deleted the churn/astro-742 branch October 30, 2026 02:59
@linear-code

linear-code Bot commented Oct 30, 2026

Copy link
Copy Markdown
Contributor

PIX-4815

This branch was successfully deployed

1 active deployment
Preview — 492d7fc1 Deployed Oct 30, 2026 by vercel[bot]
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