-
Notifications
You must be signed in to change notification settings - Fork 26
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: launchdarkly/js-core
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: jest-v0.1.6
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: launchdarkly/js-core
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: jest-v0.1.7
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 4 commits
- 35 files changed
- 6 contributors
Commits on May 21, 2025
-
chore(deps): bump next from 14.2.21 to 14.2.26 in /packages/sdk/verce…
…l/examples/complete (#855) Bumps [next](https://github.com/vercel/next.js) from 14.2.21 to 14.2.26. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/vercel/next.js/releases">next's releases</a>.</em></p> <blockquote> <h2>v14.2.26</h2> <blockquote> <p>[!NOTE]<br /> This release is backporting bug fixes. It does <strong>not</strong> include all pending features/changes on canary.</p> </blockquote> <h3>Core Changes</h3> <ul> <li>Match subrequest handling for edge and node (<a href="https://redirect.github.com/vercel/next.js/issues/77476">#77476</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/vercel/next.js/commit/10a042cdca294fd1c6852b320954bc6ccc6064e7"><code>10a042c</code></a> v14.2.26</li> <li><a href="https://github.com/vercel/next.js/commit/8a511d6a22d38132c79b8f70ee29713d42225802"><code>8a511d6</code></a> Match subrequest handling for edge and node (<a href="https://redirect.github.com/vercel/next.js/issues/77476">#77476</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/d36a1f3c3547b0cb807f30c14aa6250a932349c8"><code>d36a1f3</code></a> v14.2.25</li> <li><a href="https://github.com/vercel/next.js/commit/5fd3ae8f8542677c6294f32d18022731eab6fe48"><code>5fd3ae8</code></a> [backport] Update middleware request header (<a href="https://redirect.github.com/vercel/next.js/issues/77202">#77202</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/756be15c4cfecb6fae1c69cae7cfaf336423b6cf"><code>756be15</code></a> v14.2.24</li> <li><a href="https://github.com/vercel/next.js/commit/ba6453d5efbb1dcb282c39d372b48d60de59fa2c"><code>ba6453d</code></a> fix corepack keys</li> <li><a href="https://github.com/vercel/next.js/commit/c482c2072f6eb3f7bd656bc05e100ed54dce3636"><code>c482c20</code></a> [backport v14] fix: ensure lint worker errors aren't silenced (<a href="https://redirect.github.com/vercel/next.js/issues/75766">#75766</a>) (<a href="https://redirect.github.com/vercel/next.js/issues/75779">#75779</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/5791cb677808df1cea625057d6aff95fbf5cd3a0"><code>5791cb6</code></a> [Backport v14] add additional x-middleware-set-cookie filtering (<a href="https://redirect.github.com/vercel/next.js/issues/75561">#75561</a>) (<a href="https://redirect.github.com/vercel/next.js/issues/75">#75</a>...</li> <li><a href="https://github.com/vercel/next.js/commit/8129a6188096c23c68d4151256acbe6d86d2eed3"><code>8129a61</code></a> test: fix eslint plugin test (<a href="https://redirect.github.com/vercel/next.js/issues/75687">#75687</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/f27ce02b6785a1c7c8f88daf1d2112b5a2e1f34a"><code>f27ce02</code></a> v14.2.23</li> <li>Additional commits viewable in <a href="https://github.com/vercel/next.js/compare/v14.2.21...v14.2.26">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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 show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@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) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/launchdarkly/js-core/network/alerts). </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 4ac8196 - Browse repository at this point
Copy the full SHA 4ac8196View commit details
Commits on May 22, 2025
-
chore: now utilizes FDv2 basis param and supports FDv1 fallback (#849)
Co-authored-by: Todd Anderson <tanderson@Todds-MacBook-Pro.local>
Configuration menu - View commit details
-
Copy full SHA for 0b50153 - Browse repository at this point
Copy the full SHA 0b50153View commit details -
fix: Requestor initialized with wrong withReasons and useReport config (
#869) **Requirements** - [ ] I have added test coverage for new or changed functionality - [ ] I have followed the repository's [pull request submission guidelines](../blob/main/CONTRIBUTING.md#submitting-pull-requests) - [ ] I have validated my changes against all supported platform versions **Related issues** #868 **Describe the solution you've provided** Provides Requestor configuration in correct order. **Describe alternatives you've considered** None. **Additional context** Fixes #868 Edit: in functions with many arguments, consider arguments with an object, so that it's more clear what values are assigned to which keys. --------- Co-authored-by: Ryan Lamb <4955475+kinyoklion@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 2e095c5 - Browse repository at this point
Copy the full SHA 2e095c5View commit details -
🤖 I have created a release *beep* *boop* --- <details><summary>jest: 0.1.7</summary> ## [0.1.7](jest-v0.1.6...jest-v0.1.7) (2025-05-22) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/react-native-client-sdk bumped from ~10.10.1 to ~10.10.2 </details> <details><summary>react-native-client-sdk: 10.10.2</summary> ## [10.10.2](react-native-client-sdk-v10.10.1...react-native-client-sdk-v10.10.2) (2025-05-22) ### Bug Fixes * Requestor initialized with wrong withReasons and useReport config ([#869](#869)) ([2e095c5](2e095c5)) </details> --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for ea02136 - Browse repository at this point
Copy the full SHA ea02136View commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff jest-v0.1.6...jest-v0.1.7