houmark

Changelog is still very little useful. Issues should not be closed until the changelog meets standards developers can expect it to meet.

Still an issue, should not be closed!

We also see failed builds. On the second failed one today (none have succeeded). Deploy seems to fail with error: > [ERROR]: Failed to deploy Looking at the logs again...

@hloriana thanks. What's the preferred email to use for sending app ID and more information?

@hloriana Our app ID is: `d27sbj90esrqdg`. Build failed in both master and develop consistently, every time. It's quite embarrassing for AWS that it's now 21 days since this report, which...

Thank you @hloriana — I can confirm that we were able to build and deploy without issues on our development branch. Obviously curious to know what was the reason for...

I also see this error in the latest wrangler 2.1.8 (and all recent versions before I tested).

@ryanflorence If the goal was to slow down user adoption of v6 and have people look for alternative routers, then that goal has certainly been reached with a breaking approach...

The solution outlined by @RandScullard in https://github.com/remix-run/react-router/issues/7634#issuecomment-1006997643 seems like a very simple and low-risk change, that will keep current functionality while also introducing better backward compatibility without breaking any existing...

Of course this also raises the question about non-core modules and their labels. How do they make it in? Do they need their own place in the central repository or...