build(deps): bump astro from 4.16.19 to 7.0.4 in /site#14
build(deps): bump astro from 4.16.19 to 7.0.4 in /site#14dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [astro](https://github.com/withastro/astro/tree/HEAD/packages/astro) from 4.16.19 to 7.0.4. - [Release notes](https://github.com/withastro/astro/releases) - [Changelog](https://github.com/withastro/astro/blob/main/packages/astro/CHANGELOG.md) - [Commits](https://github.com/withastro/astro/commits/astro@7.0.4/packages/astro) --- updated-dependencies: - dependency-name: astro dependency-version: 7.0.4 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
Code Review SummaryStatus: No Issues Found | Recommendation: Merge This is a single-line Dependabot version bump ( Files Reviewed (1 file)
Reviewed by minimax-m3 · Input: 34.6K · Output: 2K · Cached: 155.2K |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 454ea83bf3
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| "@iconify-json/simple-icons": "^1.2.30", | ||
| "@lobehub/icons": "^1.49.0", | ||
| "astro": "^4.16.18", | ||
| "astro": "^7.0.4", |
There was a problem hiding this comment.
Update the site lockfile with the Astro bump
The Pages workflow's Build landing site step runs cd site && bun install --frozen-lockfile && bun run build (.github/workflows/pages.yml line 198), and bun install --help says --frozen-lockfile disallows lockfile changes. This manifest now asks for astro@^7.0.4, but site/bun.lock still records astro: ^4.16.18 and resolves astro@4.16.19, so every landing-site deploy/install with the committed lockfile has to rewrite the lockfile before it can install the new Astro version and will fail under the frozen install. Please regenerate and commit site/bun.lock with this dependency bump.
Useful? React with 👍 / 👎.
| "@iconify-json/simple-icons": "^1.2.30", | ||
| "@lobehub/icons": "^1.49.0", | ||
| "astro": "^4.16.18", | ||
| "astro": "^7.0.4", |
There was a problem hiding this comment.
Upgrade the Astro integrations with the major bump
Even after the lockfile is regenerated, this Astro 7 upgrade leaves the required Tailwind integration on @astrojs/tailwind@^5.1.5; the committed package metadata for that version declares a peer range of astro@^3.0.0 || ^4.0.0 || ^5.0.0 (site/bun.lock line 58), and site/astro.config.mjs still loads tailwind() during every site build. Installs/builds that enforce peer compatibility or exercise that integration will be running an unsupported Astro/Tailwind combination, so the migration should update or replace the integration along with the Astro major.
Useful? React with 👍 / 👎.
Bumps astro from 4.16.19 to 7.0.4.
Release notes
Sourced from astro's releases.
... (truncated)
Changelog
Sourced from astro's changelog.
... (truncated)
Commits
5978993[ci] release (#17213)b1c9d41chore(seo): remove redundant twitter metadata tags (#17179)799e5cdchore: bump compiler to latest (#17184)734739d[ci] formatd5fbee8chore(deps): update sharp to v0.35 (#17234)23f9446FIx: inverted logic in a11y-no-redundant-roles rule (#17067)2bfb179chore: simpler package.json types (#17229)7ba0bb1Harden transition directive attribute rendering (#17212)2f39a99Document route cache invalidation behavior (#17215)efd16e9Stabilize client prerender prefetch E2E test (#17219)Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for astro since your current version.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)