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.

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

prepare 5.1.0 release #98

Merged
merged 281 commits into from
Mar 19, 2024
Merged

prepare 5.1.0 release #98

merged 281 commits into from
Mar 19, 2024

Conversation

LaunchDarklyReleaseBot
Copy link
Contributor

[5.1.0] - 2024-03-19

Changed:

  • Redact anonymous attributes within feature events
  • Always inline contexts for feature events

Fixed:

  • Pin dev version of node to compatible types.

Removed:

  • HTTP fallback ping

remove unused Rollup plugins, update dependencies
(1) use new test helpers + misc test cleanup
…-types

clearer way to model the config option defaults/types
…pper

# Conflicts:
#	src/EventProcessor.js
#	src/EventSender.js
#	src/Stream.js
#	src/__tests__/EventSender-test.js
#	src/configuration.js
#	typings.d.ts
…-wrapper

# Conflicts:
#	src/EventProcessor.js
#	src/EventSender.js
#	src/__tests__/EventSender-test.js
yusinto and others added 26 commits November 30, 2022 14:36
…dk-for-u2c-release

[sc-178313] Replace instances of user for release
[sc-178324] Merge u2c changes for major release
This pull request was auto generated by the Launchdarkly Github
Standards automation platform.

* Add default CODEOWNERS file
The `httpFallbackPing` has been broken for many years because it's
incorrectly appending the fallback image url to the events url. Upon
investigation the relevant parts of the sdk which deals with this
fallback mechanism are outdated and no longer valid. They were used at a
time when some browsers don't support XMLHttpRequest.

Now we can remove usePost and consequently httpFallbackPing . I think
this is safe because according to
[this](https://caniuse.com/?search=XMLHttpRequest) all the major
browsers we support support XMLHttpRequest. IE10 & 11 don't support JSON
as response type but:

1. We're not processing the response body. we send content-type as json,
and then we process the response status and header.
2. IE is no longer supported by Microsoft as of Feb 2023, so we're
following suit.

See slack
[thread](https://launchdarkly.slack.com/archives/CA3KD877U/p1689592583516489).
We got feedback from a customer that they were confused by the "goals"
language in our SDK docs, which we now call "metrics." This clarifies
that goals = metrics and A/B testing = Experimentation.

Story details: https://app.shortcut.com/launchdarkly/story/213100
This pins the dev typings of node to allow the typescript check to pass.

This is temporary to keep this code working until it is replaced by a
TypeScript implementation.
@LaunchDarklyReleaseBot LaunchDarklyReleaseBot merged commit 93ac9dd into main Mar 19, 2024
1 check passed
@LaunchDarklyReleaseBot LaunchDarklyReleaseBot deleted the release-5.1.0 branch March 19, 2024 18:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.