Skip to content

Conversation

conico974
Copy link
Contributor

This should be enough changes to move the repo to @opennextjs/opennextjs-aws and everything should work

Copy link

changeset-bot bot commented Sep 26, 2024

⚠️ No Changeset found

Latest commit: 96ee510

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link

vercel bot commented Sep 26, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
open-next ✅ Ready (Inspect) Visit Preview 💬 Add feedback Sep 26, 2024 1:44pm

"name": "@opennextjs/aws",
"version": "3.1.3",
"bin": {
"open-next": "./dist/index.js"
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we want to keep it as open-next or do we want to change that as well ?

@thdxr thdxr merged commit 94d8fe1 into opennextjs:main Sep 27, 2024
3 checks passed
@conico974 conico974 deleted the chores/migrate-new-repo branch October 29, 2024 10:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants