✅ Deploy Preview for v3-meteor-api-docs ready!

Name	Link
🔨 Latest commit	363403f
🔍 Latest deploy log	https://app.netlify.com/projects/v3-meteor-api-docs/deploys/686bfac4436e000008ad39c6
😎 Deploy Preview	https://deploy-preview-13840.docs.meteor.com
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

✅ Deploy Preview for v3-migration-docs canceled.

We need to discuss the location of the CSS. Right now it is in the accounts-ui-unstyled and then imported only if accounts-ui is present. Honestly it makes no sense to me and I would like to move it to accounts-ui (after testing that it still works as intended).

@italojs v3.3.1? Probably not a bad choice that I think about it. This might be a sexy things to have on the changelog to draw people in.

@StorytellerCZ i'm sorry, what do you mean? it will be in the change logs anyway
but if you prefer, we could move it for release 3.4, but it will take a while to be published

3.3.1 is a fine for release.

I’m not sure this belongs in a patch. If I’m right, it introduces visual breaking changes for production apps. All developers using the current Accounts UI would suddenly see styling updates in a patch. This needs its own breaking‐change or migration notes. I’d prefer to include and announce it in Meteor 3.4.

@nachocodoner I agree. That is why I was surprised when @italojs targeted the 3.3.1 branch. Moved everything to 3.4.0 branch target.

I'm keeping an eye on this PR for a later Meteor 3.4 beta, since it includes an UI breaking change. Together with another update on my side that could cause some issues (though no breaking changes expected), I prefer to include them in a later round of 3.4 beta releases.