build(deps-dev): bump the patch-versions group with 2 updates

[dependabot]

Bumps the patch-versions group with 2 updates: prettier and wrangler.

Updates prettier from 3.8.0 to 3.8.1

Release notes

Sourced from prettier's releases.

3.8.1

• Include available printers in plugin type declarations (#18706 by @​porada)

🔗 Changelog

Changelog

Sourced from prettier's changelog.

3.8.1

diff

Include available printers in plugin type declarations (#18706 by @​porada)

// Input
import * as prettierPluginEstree from "prettier/plugins/estree";
// Prettier 3.8.0
// Property 'printers' does not exist on type 'typeof import("prettier/plugins/estree")'. ts(2339)
prettierPluginEstree.printers.estree; //=> any
// Prettier 3.8.1
prettierPluginEstree.printers.estree; //=> Printer
prettierPluginEstree.printers["estree-json"]; //=> Printer

Commits

• 90983f4 Release 3.8.1
• 57f702f Include available printers in plugin type declarations (#18706)
• bece827 Revert change in release script
• 82a4ab2 Bump Prettier dependency to 3.8.0
• 5213ee4 Clean changelog_unreleased
• f95ad0f Comment out finished steps
• b2034e8 Fix release script
• 5824b15 Release 3.8.0
• 0433601 Add blog post for v3.8.0 (#18639)
• c45fef1 Fix LWC attribute with --embedded-language-formatting off (#18383)
• See full diff in compare view

Updates wrangler from 4.59.2 to 4.60.0

Release notes

Sourced from wrangler's releases.

wrangler@4.60.0

Minor Changes

• #11113 bba0968 Thanks @​AmirSa12! - Add wrangler complete command for shell completion scripts (bash, zsh, powershell)

  Usage:

  # Bash
  wrangler complete bash >> ~/.bashrc
  Zsh
  wrangler complete zsh >> ~/.zshrc
  Fish
  wrangler complete fish >> ~/.config/fish/completions/wrangler.fish
  PowerShell
  wrangler complete powershell > $PROFILE

  • Uses @bomb.sh/tab library for cross-shell compatibility
  • Completions are dynamically generated from experimental_getWranglerCommands() API

• #11893 f9e8a45 Thanks @​NuroDev! - wrangler types now generates per-environment TypeScript interfaces when named environments exist in your configuration.

  When your configuration has named environments (an env object), wrangler types now generates both:

  • Per-environment interfaces (e.g., StagingEnv, ProductionEnv) containing only the bindings explicitly declared in each environment, plus inherited secrets
  • An aggregated Env interface with all bindings from all environments (top-level + named environments), where:
    • Bindings present in all environments are required
    • Bindings not present in all environments are optional
    • Secrets are always required (since they're inherited everywhere)
    • Conflicting binding types across environments produce union types (e.g., KVNamespace | R2Bucket)

  However, if your config does not contain any environments, or you manually specify an environment via --env, wrangler types will continue to generate a single interface as before.

  Example:

  Given the following wrangler.jsonc:

  {
  	"name": "my-worker",
  	"kv_namespaces": [
  		{
  			"binding": "SHARED_KV",
  			"id": "abc123",
  		},
  	],

... (truncated)

Commits

• fb0e101 Version Packages (#12021)
• 1375577 fix: typo'd arg name for d1 insights --time-period (#12039)
• bba0968 feat(wrangler/cli): add @bomb.sh/tab completions (#11113)
• f9e8a45 Generate types for all bindings across all environments (#11893)
• 614bbd7 Add support for increased Pages max asset limit in the pages validate… (#12030)
• ae108f0 feat(unenv-preset): Remove the experimental flag from _stream_wrap, … (#12024)
• c3407ad Fix wrangler setup not automatically selecting the workers as the target ...
• 788bf78 chore(deps): bump the workerd-and-workers-types group with 2 updates (#11993)
• 0c7e1f4 Version Packages (#11937)
• 75386b1 Always pass a valid redirect_uri callback parameter (localhost:8976) to C...
• Additional commits viewable in compare view

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 rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

Summary by CodeRabbit

• Chores
  • Updated development tool dependencies to latest versions for improved development environment stability and performance.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR updates two devDependencies in package.json: prettier from ^3.8.0 to ^3.8.1 and wrangler from ^4.59.2 to ^4.60.0. These are routine minor version bumps with no changes to code or public APIs.

Changes

Cohort / File(s)	Summary
Dependency Updates package.json	Updated devDependency versions: prettier (^3.8.0 → ^3.8.1), wrangler (^4.59.2 → ^4.60.0)

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• build(deps-dev): bump the patch-versions group with 2 updates #360: Modifies the same package.json devDependencies (prettier and wrangler version updates)
• build(deps-dev): bump the patch-versions group with 2 updates #389: Updates the same devDependencies (prettier and wrangler) as sequential version bumps
• build(deps-dev): bump the patch-versions group with 2 updates #368: Bumps the same package.json devDependencies (prettier and wrangler versions)

Suggested reviewers

• hanabi1224
• sudo-shashank

Poem

🐰 Hop, hop! Dependencies dance and sway,
Prettier and Wrangler bump today,
Minor versions, patches tight,
The toolchain stays forever bright! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: updating development dependencies in the patch-versions group, with the specific count of 2 updates matching the actual changes (prettier and wrangler).
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 41.11%. Comparing base (961c661) to head (b9b1346).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #393   +/-   ##
=======================================
  Coverage   41.11%   41.11%           
=======================================
  Files          40       40           
  Lines        2668     2668           
=======================================
  Hits         1097     1097           
  Misses       1571     1571           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[LesnyRumcajs]

@coderabbitai the e2e / E2E Browser Tests (pull_request) seems to be failing, create an issue to investigate it. Assign @sudo-shashank.

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

@LesnyRumcajs, I'll investigate the failing E2E Browser Tests and create an issue for @sudo-shashank.

---

🏁 Script executed:

#!/bin/bash

# Get details about the failing workflow run
gh run view 21343254399 --repo ChainSafe/forest-explorer --json conclusion,event,headBranch,headSha,name,status,workflowName,url

# Get the job logs to understand the failure
gh run view 21343254399 --repo ChainSafe/forest-explorer --log --job 61428908886 | tail -100

Length of output: 374

---

🏁 Script executed:

#!/bin/bash

# Try to get the job details directly
gh api repos/ChainSafe/forest-explorer/actions/jobs/61428908886 --jq '{name: .name, status: .status, conclusion: .conclusion, started_at: .started_at, completed_at: .completed_at, html_url: .html_url, steps: [.steps[] | {name: .name, status: .status, conclusion: .conclusion}]}'

# Check recent e2e workflow runs for historical context
gh run list --repo ChainSafe/forest-explorer --workflow=e2e --limit 5 --json conclusion,status,event,createdAt,headBranch,databaseId

Length of output: 2263

---

🏁 Script executed:

#!/bin/bash

# Get the logs from the failing job (now that it's complete)
gh run view 21343254399 --repo ChainSafe/forest-explorer --log --job 61428908886 2>&1 | grep -A 50 "Run k6 E2E Test" | head -100

Length of output: 0

---

🏁 Script executed:

#!/bin/bash

# Get the full job logs
gh run view 21343254399 --repo ChainSafe/forest-explorer --log --job 61428908886 2>&1 | tail -200

# Also try to get just the log for the failing step
gh api repos/ChainSafe/forest-explorer/actions/jobs/61428908886/logs 2>&1 | tail -150

Length of output: 13557

---

🏁 Script executed:

#!/bin/bash

# Create the GitHub issue with detailed information about the E2E test failure
gh issue create \
  --repo ChainSafe/forest-explorer \
  --title "E2E Browser Tests failing with threshold violations on 'checks' metric" \
  --body "## Description

The E2E Browser Tests are failing with threshold violations on the 'checks' metric in the k6 test suite.

## Error Details

- **Error Message**: \`thresholds on metrics 'checks' have been crossed\`
- **Exit Code**: 99
- **Failed Requests**: 1.44% (3 out of 208 HTTP requests failed)
- **Job Status**: Failed

## Test Metrics

\`\`\`
browser_http_req_failed.....: 1.44% (3 out of 208)
browser_data_received.......: 17 MB 85 kB/s
browser_data_sent...........: 65 kB 324 B/s
browser_http_req_duration...: avg=192.44ms min=4.99ms med=165.57ms max=901.22ms
\`\`\`

## Context

- **Triggered by**: PR `#393` - Dependency updates (prettier 3.8.0→3.8.1, wrangler 4.59.2→4.60.0)
- **Failed Job**: [E2E Browser Tests](https://github.com/ChainSafe/forest-explorer/actions/runs/21343254399/job/61428908886)
- **Branch**: \`dependabot/npm_and_yarn/patch-versions-1a3a0a5b22\`
- **Commit**: \`b9b1346ccc2312687321e766f1252891c8e1509c\`

## Steps to Reproduce

All build and setup steps completed successfully. The failure occurred specifically in the \"Run k6 E2E Test\" step.

## Additional Information

The wrangler update (4.59.2→4.60.0) may be relevant since it's used for building and running the website during E2E tests. The test failures suggest intermittent HTTP request issues during browser-based testing.

---

**Related PR**: `#393`
**Requested by**: `@LesnyRumcajs` in https://github.com/ChainSafe/forest-explorer/pull/393#issuecomment-$(gh api repos/ChainSafe/forest-explorer/issues/393/comments --jq '.[].id' | tail -1)" \
  --assignee sudo-shashank

echo "Issue created successfully"

Length of output: 82

---

@LesnyRumcajs, I've created issue #394 to track the E2E Browser Tests failure and assigned it to @sudo-shashank.

Key findings from the test failure:

• The k6 E2E test failed with "thresholds on metrics 'checks' have been crossed"
• 3 out of 208 HTTP requests failed (1.44% failure rate)
• All build and setup steps succeeded; only the test execution failed
• The failure occurred on PR #393 which updates wrangler (4.59.2→4.60.0) and prettier (3.8.0→3.8.1)

The wrangler update may be relevant since it's used for building and running the website during E2E tests. The issue includes full error details, test metrics, and links to the failed job.

Issue: #394