Skip to content
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.

Sign up for GitHub

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

Jump to bottom

build(deps): bump @microsoft/applicationinsights-web from 2.8.9 to 3.0.0 #759

Closed
wants to merge 1 commit into from
Closed

build(deps): bump @microsoft/applicationinsights-web from 2.8.9 to 3.0.0 #759

wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Apr 13, 2023 •
edited
Loading

Bumps @microsoft/applicationinsights-web from 2.8.9 to 3.0.0.

Release notes

Sourced from @​microsoft/applicationinsights-web's releases.

3.0.0

Major release with breaking changes from v2.x see v3.x Breaking Changes for details.

Maintained from the main branch, v2.x is in maintenance mode on the master branch

Changelog

  • All code from 2.8.12 has been merged into the main branch and therefore this release

Major Changes

  • Removed ES3 (IE8) Support

  • Enabled dynamic config changes after initialization

    • #1427 Dynamically updating config (for extensions in my case)

  • Too many individual commits to include as most revolve around the breaking changes and enabling dynamic configuration support for each extension

    • All Extensions now share the same configuration object core.config in previous releases each component maintained their own copy with their own default values, now all defaults and configuration values are exposed on the shared config.
    • By default the config object passed in during initialization is NOT the same object as that used as the shared config. Any previous assumptions around this being the same object will now be broken as this was a previously unsupported scenario.
    • All properties of the config object are now using get/set functions (via Object.defineProperty) to allow listeners to be registered (core.onCfgChange and internally onConfigChange) so that the callback function will be called if any referenced config property is changed. Yes, this means you can register your own configuration listener via core.onCfgChange see the AISku Manual Test for an example.
    • All properties present during initialization are converted into dynamic properties and may be monitored, properties added "after" creation (initialization) are not. This is to continue to support IE which does not support Proxy implementation which also means we are not using the Proxy class.
    • Extensions are now responsible for listening and responding to the configuration changes that they want to support
    • Updating the config extensions and channels is NOT supported, you must use the individual plugin add / remove functions if you want to dynamically add / remove extensions / channels
    • Support for parallel channels was removed from the Core and SKU's and extracted to the new TeeChannel, if you require this support you will need to use npm and include this module.

  • v2.x Extension support.

    • While the basic API and support for Backward compatibility for the v2.x extension (plugin) API was maintained, due to the breaking changes (specifically the removal of the namespaced helpers) this will only support self contained components (without recompiling). Any npm module that attempts to import and use a removed helper function will potentially break and will need to be updated to use the newer or replacement helper functions (see the v3.x Breaking Changes for details), if you find an issue and are not able to work around please raise an issue.

What's Changed

... (truncated)

Changelog

Sourced from @​microsoft/applicationinsights-web's changelog.

3.0.0 (Apr 12th, 2023)

Major release with breaking changes from v2.x see v3.x Breaking Changes for details.

Maintained from the main branch, v2.x is in maintenance mode on the master branch

Changelog

  • All code from 2.8.12 has been merged into the main branch and therefore this release

Major Changes

  • Removed ES3 (IE8) Support

  • Enabled dynamic config changes after initialization

    • #1427 Dynamically updating config (for extensions in my case)

  • Too many individual commits to include as most revolve around the breaking changes and enabling dynamic configuration support for each extension

    • All Extensions now share the same configuration object core.config in previous releases each component maintained their own copy with their own default values, now all defaults and configuration values are exposed on the shared config.
    • By default the config object passed in during initialization is NOT the same object as that used as the shared config. Any previous assumptions around this being the same object will now be broken as this was a previously unsupported scenario.
    • All properties of the config object are now using get/set functions (via Object.defineProperty) to allow listeners to be registered (core.onCfgChange and internally onConfigChange) so that the callback function will be called if any referenced config property is changed. Yes, this means you can register your own configuration listener via core.onCfgChange see the AISku Manual Test for an example.
    • All properties present during initialization are converted into dynamic properties and may be monitored, properties added "after" creation (initialization) are not. This is to continue to support IE which does not support Proxy implementation which also means we are not using the Proxy class.
    • Extensions are now responsible for listening and responding to the configuration changes that they want to support
    • Updating the config extensions and channels is NOT supported, you must use the individual plugin add / remove functions if you want to dynamically add / remove extensions / channels
    • Support for parallel channels was removed from the Core and SKU's and extracted to the new TeeChannel, if you require this support you will need to use npm and include this module.

  • v2.x Extension support.

    • While the basic API and support for Backward compatibility for the v2.x extension (plugin) API was maintained, due to the breaking changes (specifically the removal of the namespaced helpers) this will only support self contained components (without recompiling). Any npm module that attempts to import and use a removed helper function will potentially break and will need to be updated to use the newer or replacement helper functions (see the v3.x Breaking Changes for details), if you find an issue and are not able to work around please raise an issue.

2.8.12 (Apr, 11th, 2023)

Changelog

  • #2014 [BUG] The documentation for enableDebug is incorrect, it should reference enableDebugExceptions
  • #2027 [BUG] SDK LOAD Failure reporting not working
  • #2034 [BUG] Failed XHR request after ever tracked item when gathered logs exceed maxBatchSizeInBytes while offline
  • #2037 [Master] Add local storage-based implementation #1419
    • Add support for user provided storage option for Sender
  • #2029 [Master] Add npm-pack and npm-publish tasks
  • #2026 [Master] Fix examples, Throttle tests and export dependency types from Sku

2.8.11 (Mar 8th, 2023)

Changelog

  • #1996 [BUG] SharedWorker does not Instrument fetch correctly
  • #1995 [BUG] App Insights not auto-capturing from a Web Worker
    • Stops logging that workers can emit the PageView Performance event
  • #1792 [BUG] Documentation should clarify that node apps should use applicationinsights, not this package
  • #1794 [BUG] link on AISKULight goes to not found page
  • #1990 Field 'assembly' on type 'StackFrame' is too long. Expected: 1024 characters [BUG]
  • Update documentation and tests to replace instrumentationKey usage with connectionString

... (truncated)

Commits
  • 053a8a0 [Release] Increase version to 3.0.0 (#2048)
  • cd07499 [Master] Merge latest main to master (#2047)
  • 53f6c86 [Main] Update to support tests that don't pass in a core instance (#2044)
  • 45de8a0 [Rollup-ES5 Release] Increase version to 1.0.2 (#2043)
  • 3175210 [Main][BUG] Don't attempt to send message batch when known to be offline #203...
  • 5a71f82 More nightly CDN publishing fixes (#2040)
  • 59bb263 Fix CDN Publishing location (#2039)
  • 2fd5118 [Main] Add npm-pack and npm-publish tasks (#2033)
  • f90f593 [BUG] The documentation for enableDebug is incorrect, it should reference ena...
  • 034e895 Add support to tag objects to force or block dynamic conversion (#2020)
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot dependabot bot added the ⛓️ dependencies Pull requests that update a dependency file label Apr 13, 2023
@dependabot dependabot bot mentioned this pull request Apr 13, 2023
Closed
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/microsoft/applicationinsights-web-3.0.0 branch from 46c88d4 to 0f89bf6 Compare April 16, 2023 21:05
@dependabot
build(deps): bump @microsoft/applicationinsights-web from 2.8.9 to 3.0.0
54e846a 
Bumps [@microsoft/applicationinsights-web](https://github.com/microsoft/ApplicationInsights-JS) from 2.8.9 to 3.0.0.
- [Release notes](https://github.com/microsoft/ApplicationInsights-JS/releases)
- [Changelog](https://github.com/microsoft/ApplicationInsights-JS/blob/main/RELEASES.md)
- [Commits](microsoft/ApplicationInsights-JS@2.8.9...3.0.0)

---
updated-dependencies:
- dependency-name: "@microsoft/applicationinsights-web"
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/microsoft/applicationinsights-web-3.0.0 branch from 0f89bf6 to 54e846a Compare April 16, 2023 21:06
@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github May 2, 2023

Superseded by #832.

@dependabot dependabot bot closed this May 2, 2023
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/microsoft/applicationinsights-web-3.0.0 branch May 2, 2023 18:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
⛓️ dependencies Pull requests that update a dependency file
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
0 participants