Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

vercel / next.js Public

Notifications You must be signed in to change notification settings
Fork 26.9k
Star 127k

Code
Issues 3k
Pull requests 598
Discussions
Actions
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Discussions
Actions
Security
Insights

Fix `revalidateTag()` behaviour when invoked in server components #39369

Sign in to view logs

Sign in to view logs

Fix `revalidateTag()` behaviour when invoked in server components

Fix `revalidateTag()` behaviour when invoked in server components #39369

Summary
Jobs
- Graphite CI Optimizer
- Determine changes
- build
- build
- validate-docs-links
- build
- build
- build
- build
- build
- Test
- build
- build
- ast-grep lint
- Run devlow benchmarks
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- test next-swc wasi
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- Test new tests when deployed
- report test results to datadog
- thank you, next
Run details
- Usage
- Workflow file

Usage Workflow file

Annotations

1 error

Run /bin/bash -c "__NEXT_EXPERIMENTAL_PPR=true NEXT_EXTERNAL_TESTS_FILTERS="test/ppr-tests-manifest.json" NEXT_TEST_MODE=dev node run-tests.js --timings -g 4/4 -c ${TEST_CONCURRENCY} --type development"

Process completed with exit code 1.

test ppr dev (4/4) / build

test ppr dev (4/4) / build

failed Sep 30, 2024 in 4m 57s. View latest attempt.

Loading

Re-running jobs...

You can’t perform that action at this time.