jordanjay29 [deleted] I'm glad you figured this out already! Did you use a certain tool or just an educated guess?
[deleted] jordanjay29 Did you use a certain tool or just an educated guess? Educated guess, based on previous upgrade encounters 🙂
rob006 [deleted] Educated guess, based on previous upgrade encounters 🙂 There is a command for that™: $ composer why-not flarum/core v0.1.0-beta.10 kilowhat/flarum-ext-mailing 0.1.1 requires flarum/core (>= 0.1.0-beta.8 < 0.1.0-beta.10)
[deleted] Ralkage No problems. I posted originally in the announcement, then deleted that after reading about posting here. I figured I'd take a chance and it paid off 🙂
[deleted] rob006 Ok, but that would only manifest itself after changing https://discuss.flarum.org/d/21352-issues-upgrading-from-beta-9-to-beta-10/2
jordanjay29 rob006 That is the command I was going to suggest, but mcutting's sharp mind was too fast for that.
rob006 [deleted] I used composer.json from first post (I removed only recache extension). This will explain why composer update does not update Flarum to beta 10, there is no need to change anything in composer.json.
[deleted] rob006 True, but this is still broke, so it would still have failed "kilowhat/flarum-ext-mailing": "^0.1.0" You'd either have to remove it, or it'd keep failing.
jordanjay29 [deleted] the composer why-not is just a diagnostic tool, you're correct that you would need to also use composer remove or manually delete the line to resolve the issue without resorting to a brute-force method of upgrading.
rob006 [deleted] You'd either have to remove it, or it'd keep failing. Yeah, but you don't need to guess anymore, you have exact reason why update was blocked.
jordanjay29 rob006 And now the issue is resolved, and we're all aware of composer why-not. Let's let this discussion be Solved.
jvloo Encountered the same issue and fortunately I found your post.. so not need to repost the same issue and waiting for answer.. Thanks 😃 @[deleted]
