Commit graph

493 commits

Author SHA1 Message Date
vercel-release-bot
57da10beea v14.2.0-canary.29 2024-03-18 19:47:03 +00:00
vercel-release-bot
8b9e18503c v14.2.0-canary.28 2024-03-18 10:01:02 +00:00
vercel-release-bot
8d5e9178f9 v14.2.0-canary.27 2024-03-17 23:23:04 +00:00
vercel-release-bot
f1a999ee73 v14.2.0-canary.26 2024-03-16 22:31:13 +00:00
vercel-release-bot
3b6b04ae2c v14.2.0-canary.25 2024-03-16 20:06:26 +00:00
vercel-release-bot
fd692b61e0 v14.2.0-canary.24 2024-03-15 23:22:11 +00:00
vercel-release-bot
39a8429ac4 v14.2.0-canary.23 2024-03-14 23:21:31 +00:00
vercel-release-bot
847b340180 v14.2.0-canary.22 2024-03-14 12:45:30 +00:00
vercel-release-bot
768a92b15b v14.2.0-canary.21 2024-03-13 23:21:44 +00:00
vercel-release-bot
9d601afb08 v14.2.0-canary.20 2024-03-13 17:25:13 +00:00
vercel-release-bot
ca10b73cd5 v14.2.0-canary.19 2024-03-12 23:22:31 +00:00
vercel-release-bot
c1daa769f6 v14.2.0-canary.18 2024-03-12 17:31:06 +00:00
vercel-release-bot
0e9baea77f v14.2.0-canary.17 2024-03-12 15:10:31 +00:00
vercel-release-bot
d4069559f2 v14.2.0-canary.16 2024-03-11 23:23:31 +00:00
vercel-release-bot
6d0d1fe347 v14.2.0-canary.15 2024-03-11 22:00:55 +00:00
vercel-release-bot
da72b60e37 v14.2.0-canary.14 2024-03-11 20:51:37 +00:00
vercel-release-bot
6fee6b271b v14.2.0-canary.13 2024-03-10 23:23:45 +00:00
vercel-release-bot
fff9ddc204 v14.2.0-canary.12 2024-03-09 23:23:12 +00:00
vercel-release-bot
a2457c979b v14.2.0-canary.11 2024-03-08 23:24:43 +00:00
vercel-release-bot
5482940dd9 v14.2.0-canary.10 2024-03-08 15:19:20 +00:00
vercel-release-bot
af5b4db98a v14.2.0-canary.9 2024-03-08 08:29:26 +00:00
vercel-release-bot
ea5b23c870 v14.2.0-canary.8 2024-03-07 23:24:26 +00:00
vercel-release-bot
0b679a0fed v14.2.0-canary.7 2024-03-07 21:37:05 +00:00
vercel-release-bot
dd6cfd9882 v14.2.0-canary.6 2024-03-06 23:22:59 +00:00
vercel-release-bot
e28be5377f v14.2.0-canary.5 2024-03-06 19:57:27 +00:00
vercel-release-bot
1ad3963d44 v14.2.0-canary.4 2024-03-06 12:03:01 +00:00
vercel-release-bot
6e8a859bca v14.2.0-canary.3 2024-03-06 09:51:39 +00:00
vercel-release-bot
6045048b26 v14.2.0-canary.2 2024-03-05 23:25:45 +00:00
vercel-release-bot
d0b30787e2 v14.2.0-canary.1 2024-03-05 20:48:05 +00:00
vercel-release-bot
07e5b60a03 v14.2.0-canary.0 2024-03-05 01:09:36 +00:00
JJ Kasper
eeb2369a5d
Update to latest version (#62850)
Updates our version to match the last backport for canaries.

Closes NEXT-2699
2024-03-04 16:04:21 -08:00
vercel-release-bot
a1c9c3b9d4 v14.1.2-canary.7 2024-03-04 23:22:19 +00:00
vercel-release-bot
91a84b3ee2 v14.1.2-canary.6 2024-03-04 21:47:40 +00:00
vercel-release-bot
b80d388032 v14.1.2-canary.5 2024-03-04 16:11:11 +00:00
vercel-release-bot
330b04ff55 v14.1.2-canary.4 2024-03-04 12:29:28 +00:00
vercel-release-bot
9fb18e6739 v14.1.2-canary.3 2024-03-03 23:21:56 +00:00
vercel-release-bot
f2d4d04ff8 v14.1.2-canary.2 2024-03-02 23:21:32 +00:00
vercel-release-bot
d70a554032 v14.1.2-canary.1 2024-03-01 23:17:20 +00:00
vercel-release-bot
2f7721a632 v14.1.2-canary.0 2024-03-01 21:49:46 +00:00
JJ Kasper
8562680f23
Update version from backport (#62745)
Ensures new canaries start from correct version as we did a backport for
`v14.1.1`

Closes NEXT-2663
2024-03-01 21:35:18 +00:00
vercel-release-bot
c77454a02a v14.1.1-canary.82 2024-02-29 23:21:48 +00:00
vercel-release-bot
603b3771ce v14.1.1-canary.81 2024-02-29 16:38:01 +00:00
vercel-release-bot
f0461abff0 v14.1.1-canary.80 2024-02-28 23:23:19 +00:00
vercel-release-bot
6a7a0da737 v14.1.1-canary.79 2024-02-28 22:42:21 +00:00
vercel-release-bot
6b6575ce48 v14.1.1-canary.78 2024-02-28 12:09:02 +00:00
vercel-release-bot
b0fcd44e13 v14.1.1-canary.77 2024-02-27 23:20:54 +00:00
vercel-release-bot
036a4f60fc v14.1.1-canary.76 2024-02-27 18:20:06 +00:00
vercel-release-bot
36dde3c37e v14.1.1-canary.75 2024-02-27 17:21:46 +00:00
vercel-release-bot
eb6867fdad v14.1.1-canary.74 2024-02-26 23:22:03 +00:00
nhducit
0fe68736ce
Fix typo in the GTM URL (#62436)
<!-- Thanks for opening a PR! Your contribution is much appreciated.
To make sure your PR is handled as smoothly as possible we request that
you follow the checklist sections below.
Choose the right checklist for the change(s) that you're making:

## For Contributors

### Improving Documentation

- Run `pnpm prettier-fix` to fix formatting issues before opening the
PR.
- Read the Docs Contribution Guide to ensure your contribution follows
the docs guidelines:
https://nextjs.org/docs/community/contribution-guide

### Adding or Updating Examples

- The "examples guidelines" are followed from our contributing doc
https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md
- Make sure the linting passes by running `pnpm build && pnpm lint`. See
https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md

### Fixing a bug

- Related issues linked using `fixes #number`
- Tests added. See:
https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md

### Adding a feature

- Implements an existing feature request or RFC. Make sure the feature
request has been accepted for implementation before opening a PR. (A
discussion must be opened, see
https://github.com/vercel/next.js/discussions/new?category=ideas)
- Related issues/discussions are linked using `fixes #number`
- e2e tests added
(https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs)
- Documentation added
- Telemetry added. In case of a feature if it's used or not.
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md


## For Maintainers

- Minimal description (aim for explaining to someone not on the team to
understand the PR)
- When linking to a Slack thread, you might want to share details of the
conclusion
- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
- Add review comments if necessary to explain to the reviewer the logic
behind a change

### What?

### Why?

### How?

Closes NEXT-
Fixes #

-->
TODO: update description

Co-authored-by: JJ Kasper <jj@jjsweb.site>
2024-02-26 18:21:12 +00:00