Our packages should support you now, or soon.
The latest version of @atlaskit/focus-ring, @atlaskit/button, @atlaskit/css-reset, and a host of others don’t support React 18 and require the developer to force override peer dependencies in order to build. I do not understand how you can recommend that developers upgrade to a version of React that your basic button component does not support.
@atlaskit/analytics-next is a transitive dependency of pretty much the whole Atlassian UI Toolkit, and throws console errors because childContextTypes is deprecated in React 18 and totally prevents migration to React 19. Please take your own advice and address deprecations in your toolkit code.
I also do not understand why you are asking your developer partners to open bug reports for basic package hygiene in Atlaskit. Unless you’re opening up atlaskit to open source contributions, it is not incumbent on the community to validate your code for you.
We are working hard to enhance the functionality of Atlassian products with our partner products, and value our relationship with Atlassian, but this RFC makes no sense unless and until building Atlassian UI projects for React 18 is fully supported with no glaring console errors and without overriding peer dependencies at the very least.