-
Notifications
You must be signed in to change notification settings - Fork 87
Comparing changes
Open a pull request
base repository: opennextjs/opennextjs-netlify
base: v5.8.1
head repository: opennextjs/opennextjs-netlify
compare: v5.9.0
- 11 commits
- 40 files changed
- 6 contributors
Commits on Oct 21, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 729e605 - Browse repository at this point
Copy the full SHA 729e605View commit details -
fix(deps): update dependency @netlify/plugin-nextjs to ^5.8.1 (#2689)
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 83abe67 - Browse repository at this point
Copy the full SHA 83abe67View commit details -
Configuration menu - View commit details
-
Copy full SHA for e9fa325 - Browse repository at this point
Copy the full SHA e9fa325View commit details
Commits on Oct 22, 2024
-
chore(deps): update dependency @netlify/build to ^29.55.4 (#2691)
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 603e24e - Browse repository at this point
Copy the full SHA 603e24eView commit details -
Configuration menu - View commit details
-
Copy full SHA for eba1610 - Browse repository at this point
Copy the full SHA eba1610View commit details
Commits on Oct 23, 2024
-
chore: handle repo rename (#2696)
Co-authored-by: Philippe Serhal <philippe.serhal@netlify.com>
Configuration menu - View commit details
-
Copy full SHA for c1a20f7 - Browse repository at this point
Copy the full SHA c1a20f7View commit details
Commits on Oct 24, 2024
-
test: skip reporting CanaryOnly failures for stable version tests (#2698
) * ci: decrease number of shards when running Vercel tests * test: use PWD instead of hardcoded repo directory * test: collect build logs in Vercel e2e tests (like we do in our own e2e tests) * test: skip esm-externals-false tests (they are just checking CLI output) * ci: skip reporting about tests that use canary only features when testing stable * test: fix typo when setting _cliOutput
Configuration menu - View commit details
-
Copy full SHA for 3e745e4 - Browse repository at this point
Copy the full SHA 3e745e4View commit details
Commits on Oct 29, 2024
-
ci: add deploy cleanup step for Vercel tests (#2699)
* test: add deploy cleanup step for Vercel tests * test: increase timeout for Vercel tests * test: bump timeout * ci: allow using test results from runs triggered by pull_request when deploying e2e report using branch results
Configuration menu - View commit details
-
Copy full SHA for d3d2fb5 - Browse repository at this point
Copy the full SHA d3d2fb5View commit details
Commits on Nov 1, 2024
-
fix: add data request query param to the cache key (#2701)
* fix: vary cache key on __nextDataReq query param * test: update header tests to check for new vary param
Configuration menu - View commit details
-
Copy full SHA for 00e3a4b - Browse repository at this point
Copy the full SHA 00e3a4bView commit details
Commits on Dec 9, 2024
-
* test: upgrade deno used in tests * test: e2e simple next/after test * feat: support waitUntil * use already existing trackBackgroundWork helper from request context to handle next/after * test: increase timeout for one of smoke tests due to team-wide extensions installation time making it timeout * test: move test to dedicated fixture * chore: update outdated comment * chore: clarify awaiting backgroundWorkPromise * test: update assertion for next >=15.0.4-canary.18 * fix: support changed shape of getRequestHandlers return --------- Co-authored-by: Matt Kane <matt.kane@netlify.com>
Configuration menu - View commit details
-
Copy full SHA for 51e5373 - Browse repository at this point
Copy the full SHA 51e5373View commit details -
Configuration menu - View commit details
-
Copy full SHA for 0a6cc37 - Browse repository at this point
Copy the full SHA 0a6cc37View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v5.8.1...v5.9.0