-
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.0.0
head repository: opennextjs/opennextjs-netlify
compare: v5.1.0
- 9 commits
- 33 files changed
- 6 contributors
Commits on Apr 2, 2024
-
chore: annotate all skipped tests (#378)
* chore: annotate all skipped tests * chore: generate test config from JSON file * chore: generate JSON results * chore: more annotation * chore: add more test explanations * chore: more test config * chore: more test config * chore: use reason --------- Co-authored-by: Michal Piechowiak <misiek.piechowiak@gmail.com>
Configuration menu - View commit details
-
Copy full SHA for 8c8faa0 - Browse repository at this point
Copy the full SHA 8c8faa0View commit details
Commits on Apr 3, 2024
-
chore: use separate GHA job for smoke tests (#393)
* chore: use separate GHA job for smoke tests * chore: upgrade vitest * chore: install deno for smoke tests job * chore: actually run smoke tests in smoke tests job --------- Co-authored-by: Rob Stanford <me@robstanford.com>
1Configuration menu - View commit details
-
Copy full SHA for 035d0cc - Browse repository at this point
Copy the full SHA 035d0ccView commit details -
test: add integration tests for pages router custom 404 (#379)
* test: add integration tests for pages router custom 404 * test: more detailed test name and some extra comments explaining locale assertions * test: add assertion failure messages to provide more contextual information
Configuration menu - View commit details
-
Copy full SHA for 3578bf1 - Browse repository at this point
Copy the full SHA 3578bf1View commit details
Commits on Apr 8, 2024
-
feat: add cdn-cache-control headers to cacheable route handler respon…
…ses (#399) * test: add test cases for cacheable route handlers * refactor: add cache related types modules and adjust ROUTE variant to match our current usage * feat: add cdn-cache-control headers to cacheable route handler responses * fix: set revalidate setting on request context for Route responses and set cdn-cache-control header based on that * chore: format with prettier * chore: pass just revalidate time not entire meta --------- Co-authored-by: pieh <pieh@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for f4c588c - Browse repository at this point
Copy the full SHA f4c588cView commit details
Commits on Apr 10, 2024
-
Configuration menu - View commit details
-
Copy full SHA for db5d451 - Browse repository at this point
Copy the full SHA db5d451View commit details
Commits on Apr 12, 2024
-
Configuration menu - View commit details
-
Copy full SHA for de18110 - Browse repository at this point
Copy the full SHA de18110View commit details -
test: update e2e skipped tests (#406)
* update skipped testt * moved skipped test
Configuration menu - View commit details
-
Copy full SHA for 9445b79 - Browse repository at this point
Copy the full SHA 9445b79View commit details
Commits on Apr 16, 2024
-
feat: fail the build when advanced api routes are used (#403)
* test: add advanced routes fixture * feat: fail the build when advanced api routes are used * chore: update failBuild message with mention of migration and link to example * test: add integration test for build failing error message when advanced api routes are used * chore: drop console.logs inherited from v4 advanced api routes handling code * fix: lint * chore: use shortened link for migration example * test: update assertion * test: unrelated smoke test update
Configuration menu - View commit details
-
Copy full SHA for 275f488 - Browse repository at this point
Copy the full SHA 275f488View commit details -
chore(main): release 5.1.0 (#401)
Co-authored-by: token-generator-app[bot] <82042599+token-generator-app[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for e087bf7 - Browse repository at this point
Copy the full SHA e087bf7View 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.0.0...v5.1.0