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

build(deps): upgrades to ember-composability-tools@~1.0.3. #1261

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

matthewhartstonge
Copy link
Contributor

Helps to removes some deprecations

@mansona
Copy link
Collaborator

mansona commented Oct 15, 2024

so ember composability tools is a major breaking change 😞 this is going to be a hard one to remove. This was the motivation for #1254 so that I could migrate away for the need for it one component at a time

@matthewhartstonge
Copy link
Contributor Author

matthewhartstonge commented Oct 15, 2024

Ah, interesting...

We can't just bump our way to victory? i.e. v1.1.0 jumps to ember 4 support, v1.2.0 ember 5...

What issues does it cause?

@matthewhartstonge
Copy link
Contributor Author

matthewhartstonge commented Oct 15, 2024

As an FYI I'm starting to merge PRs into a fork in the need to move fast as conflicts are and have already become a pain. (and run integration tests!)

Do you have any suggestions? Dependencies will obviously be the worst.

I'm trying my best to keep things from not diverging as much as possible to give back.

I'm thinking the best will be to use atomic PRs stacked PRs that merge on top of one another?

Enables me to go back and fix things as I go, but keep moving forwards?

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