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.

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

Fix release, beta and canary scenarios #259

Merged
merged 1 commit into from
Aug 16, 2023

Conversation

bertdeblock
Copy link
Contributor

No description provided.

Copy link
Member

@mansona mansona left a comment

Choose a reason for hiding this comment

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

Looks good 🎉

@knownasilya knownasilya added the breaking this will be a breaking change, and a new major version should be released label Aug 16, 2023
@knownasilya knownasilya merged commit 80f812c into ember-cli:master Aug 16, 2023
18 checks passed
@bertdeblock
Copy link
Contributor Author

@knownasilya Don't think these changes should be labelled as breaking.

@knownasilya
Copy link
Contributor

You did update the node version and some of the import paths, I think those are breaking. I might be wrong..

@bertdeblock
Copy link
Contributor Author

I only updated the pinned Node version using Volta to make CI happy (I did not update engines).
The other changes were only for the docs and test-app apps.

@knownasilya knownasilya added Cleanup and removed breaking this will be a breaking change, and a new major version should be released labels Aug 16, 2023
@NullVoxPopuli
Copy link
Contributor

si, this is a browser-only v2 addon, so node version has no impact on consumers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants