Repository navigation
chore(deps-dev): bump @eslint/js from 9.8.0 to 9.39.5 - #46
Closed
dependabot[bot] wants to merge 1 commit into
Closed
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [@eslint/js](https://github.com/eslint/eslint/tree/HEAD/packages/js) from 9.8.0 to 9.39.5. - [Release notes](https://github.com/eslint/eslint/releases) - [Commits](https://github.com/eslint/eslint/commits/v9.39.5/packages/js) --- updated-dependencies: - dependency-name: "@eslint/js" dependency-version: 9.39.5 dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
Bot
added
dependencies
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Merged
10 of 12 tasks
ephbaum
added a commit
that referenced
this pull request
Sep 21, 2026
…ettier-plugin-astro 1.0) (#78) * chore(deps): roll up 11 green Dependabot bumps Consolidates the Dependabot PRs whose CI was already green into a single lockfile update, so one build gates the lot instead of eleven: zod 4.4.3 -> 4.6.5 (#77) vite 8.2.1 -> 8.3.0 (#73) @iconify-json/logos 1.2.12 -> 1.2.14 (#71) globals 17.11.0 -> 17.12.0 (#69) @typescript-eslint/parser 8.66.0 -> 8.70.0 (#68) @astrojs/sitemap 3.7.3 -> 3.7.4 (#66) sharp 0.35.3 -> 0.35.4 (#63) satori 0.29.0 -> 0.33.4 (#60) typescript 5.9.3 -> 6.0.3 (#57) @eslint/js 9.8.0 -> 9.39.5 (#46) unocss / @unocss/astro / @unocss/reset 66.7.5 -> 66.10.2 (#74) Dependabot raised only @unocss/reset; the three unocss packages share a release train and have to move together, so the other two ride along. Verified with pnpm run lint, format:check, and build — 215 pages, no astro check errors under TypeScript 6. Co-Authored-By: Claude Opus 5 <[email protected]> Claude-Session: https://claude.ai/code/session_01G214G6mJBeVBZ3CbukkNRu * chore(deps): bump astro from 7.2.1 to 7.3.2 (#76) Raised on its own (#76) this bump failed `astro check` with 20 errors — every `post.data` access reported as `unknown`. The cause is zod, not Astro: 7.3 infers a collection's `data` type through the schema's `.transform()`, and zod 4.4.3's output types defeat that inference. With the zod 4.6.5 bump from the previous commit in place, `astro check` reports zero errors, which is why this rides along here instead. The range resolves to 7.3.3, the current patch. Co-Authored-By: Claude Opus 5 <[email protected]> Claude-Session: https://claude.ai/code/session_01G214G6mJBeVBZ3CbukkNRu * chore(deps-dev): bump prettier-plugin-astro from 0.14.1 to 1.0.0 (#75) 1.0.0 changes how it breaks JSX-ish expressions in .astro files, so the bump alone left 11 files failing `format:check` — that is why #75 is red. This commit carries the reformat with it. Two things worth knowing about the new output: - It is not idempotent on the first pass. One `pnpm run format` turns `{cond && <script ... />}` in BaseHead.astro into a form it then wants to rewrite again as `{cond && (<script ... />)}`, so a single `check:fix` can still leave CI red. Run it twice; the tree here has converged and a third pass is a no-op. - Rendered HTML is unchanged except for one construct: `<Button>← Back to blog</Button>` in BlogContent.astro now breaks across lines, which adds collapsing whitespace either side of the label inside the anchor. Diffed all 215 built pages against a 7.3.3 build of the previous formatting; that anchor is the only difference once the per-build random font-fallback ids and brutal-ui colours are normalised out. Co-Authored-By: Claude Opus 5 <[email protected]> Claude-Session: https://claude.ai/code/session_01G214G6mJBeVBZ3CbukkNRu * docs: note the prettier-plugin-astro self-closing script gotcha The plugin's 1.0.x printer is not idempotent for a self-closing `<script />` inside a `{cond && …}` expression that has to wrap: one `format` pass emits output that fails `format:check`, and a second pass converges. Records the shape to avoid and, more usefully, what the confusing CI failure means when it happens. Co-Authored-By: Claude Opus 5 <[email protected]> Claude-Session: https://claude.ai/code/session_01G214G6mJBeVBZ3CbukkNRu * docs: widen the prettier-plugin-astro note to the style-comment bug Two corrections to the note added a moment ago. It pinned the behaviour to 1.0.1 when what is actually known is that it is a 1.0.x regression — 0.14.1 was stable — so a future reader should not assume moving off 1.0.1 clears it. It also missed the worse of the two bugs: multi-line CSS comments in a `<style>` block gain two spaces of indentation on every run and never reach a fixed point, so `format:check` cannot pass at all. Verified against upstream issue 487's repro on our install (7 -> 9 -> 11 -> 13 spaces). No `<style>` block here carries a comment today, which is why CI is green; adding one to BlogContent, BaseFooter, or SummaryCard would strand it. Co-Authored-By: Claude Opus 5 <[email protected]> Claude-Session: https://claude.ai/code/session_01G214G6mJBeVBZ3CbukkNRu --------- Co-authored-by: Claude <[email protected]>
Merged
9 of 12 tasks
Owner
|
Closing as stale: Generated by Claude Code |
Author
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
This branch was successfully deployed
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.
Bumps @eslint/js from 9.8.0 to 9.39.5.
Release notes
Sourced from @eslint/js's releases.
... (truncated)
Commits
202117bchore: package.json update for@eslint/jsrelease71b2f6bchore: package.json update for@eslint/jsrelease9ceef92chore: package.json update for@eslint/jsreleasec43ce24chore: package.json update for@eslint/jsreleasec7ebefcchore: package.json update for@eslint/jsrelease2375a6dchore: package.json update for@eslint/jsrelease9e7fad4chore: add script to auto-generate eslint:recommended configuration (#20208)25d0e33chore: package.json update for@eslint/jsreleaseabee4cachore: package.json update for@eslint/jsrelease90a71bfdocs: updateREADMEfiles to add badge and instructions (#20115)You can trigger a rebase of this PR 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)