Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Upgrade to open-next v3 #182

Open
bestickley opened this issue Dec 8, 2023 · 5 comments · May be fixed by #234
Open

Upgrade to open-next v3 #182

bestickley opened this issue Dec 8, 2023 · 5 comments · May be fixed by #234
Milestone
v5

Comments

@bestickley
Copy link
Contributor

Upgrade to open-next v3!
See: sst/sst#3567
@bestickley bestickley mentioned this issue Dec 15, 2023
Open
@bestickley bestickley added this to the v5 milestone Dec 15, 2023
@clemsonfan101
Copy link

Is there any sort of expected timeline or roadmap for this one? Only asking as it might change how I plan around deployments in the future.

@coryasilva
Copy link

I would like to help, do you have a plan of attack for moving to open next v3?

@bestickley
Copy link
Contributor Author

@clemsonfan101, I do not have any timeline or roadmap for v3.
@coryasilva, I do not have a plan of attack for moving to open next v3. Please feel free to take it on!

@clemsonfan101
Copy link

@coryasilva im also happy to help out

@coryasilva
Copy link

Moving to discussion

@jadenv jadenv linked a pull request Nov 12, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
v5
Development

Successfully merging a pull request may close this issue.

feat: add support for open-next v3 jadenv/cdk-nextjs
3 participants
@coryasilva @bestickley @clemsonfan101