-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #15523 from newrelic-forks/add-browser-agent-v1.249.0
Browser Agent v1.249.0 Release Notes
- Loading branch information
Showing
1 changed file
with
34 additions
and
0 deletions.
There are no files selected for viewing
34 changes: 34 additions & 0 deletions
34
...ic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.249.0.mdx
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,34 @@ | ||
--- | ||
subject: Browser agent | ||
releaseDate: "2023-12-14" | ||
version: 1.249.0 | ||
features: ["Allow empty string for Session Replay masking value"] | ||
bugs: ["loader missing sub-resource integrity hashes","Fix API Warning Messages","traceids not random when using `webcrypto`"] | ||
security: [] | ||
--- | ||
|
||
## v1.249.0 | ||
|
||
### Features | ||
|
||
#### Allow empty string for session replay masking value | ||
Allow empty strings to be provided for session replay masking values, which helps the UI/API provide sane fallbacks for never-set values. | ||
|
||
### Bug fixes | ||
|
||
#### loader missing sub-resource integrity hashes | ||
Sub-resource integrity hashes were not being properly generated and included in the loader for async chunks related to session replay. This would cause a warning to appear in the browser console, but would not block those chunks from loading. This would have only affected customers taking part in the session replay limited preview. | ||
|
||
#### Fix API warning messages | ||
Fix warning messages given by API calls made before the agent has initialized. | ||
|
||
#### Traceids not random when using `webcrypto` | ||
Fix non-random hexadecimal generation when using the webcrypto api, which in turn creates non-random traceIds, that always end in 00. | ||
|
||
## Support statement: | ||
|
||
New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. We no longer support older releases when they reach [end-of-life](https://docs.newrelic.com/docs/browser/browser-monitoring/getting-started/browser-agent-eol-policy/). Release dates are reflective of the original publish date of the agent version. | ||
|
||
New Browser Agent releases roll out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this [status dashboard](https://newrelic.github.io/newrelic-browser-agent-release/) for more information. | ||
|
||
Consistent with our [browser support policy](https://docs.newrelic.com/docs/browser/new-relic-browser/getting-started/compatibility-requirements-browser-monitoring/#browser-types), v1.249.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 110-119, Edge 110-118, Safari 15-16, and Firefox 110-119. For mobile devices, v1.249.0 was built and tested for Android Chrome 100-119 and iOS Safari 15.5-16.2. |