-
Notifications
You must be signed in to change notification settings - Fork 16
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
[React18] upgrade to react 18 #142
Conversation
Hi, when can i except this to be released to a new version in npm registry? |
We are planning on publishing a v18 and v19 versions as part of the next release cycle with v3.3.6 of Application Insights, this will include pinning the existing v17 and the v18 to 3.3.6 (to avoid the ITelemetryPlugin issue we keep hitting with update). While v18 will still be The release process will start in the first week of March, so all going well I would expect v18 and v19 versions to be available by March 7th, failing that it would be in the week of March 10th. |
Now that we have created the 17.3.x branch, please also update the version.json |
RELEASES.md
Outdated
@@ -1,5 +1,14 @@ | |||
# Releases | |||
|
|||
## 18.3.6 (March 12th, 2025) | |||
|
|||
Version 17.x is now being maintained / released from the [release17.x branch](https://github.com/microsoft/applicationinsights-react-js/tree/release17.3.x) as |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not quite, I listed the correct branches in the main readme.
Lets just say that this release is targeting React 18 and is using Application Insights 3.3.6 and that we are bumping the major version number to match the framework, basically following the same numbering as outlined here microsoft/applicationinsights-angularplugin-js#57
Including the branch names here is going to become outdated quickly, maybe just link to the compatibility matrix instead.
No description provided.