Skip to content

Bump follow-redirects from 1.14.7 to 1.14.9 - #2

Closed
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/follow-redirects-1.14.9
Closed

dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/follow-redirects-1.14.9

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Feb 26, 2022

Copy link
Copy Markdown

Bumps follow-redirects from 1.14.7 to 1.14.9.

Commits
  • 13136e9 Release version 1.14.9 of the npm package.
  • 2ec9b0b Keep headers when upgrading from HTTP to HTTPS.
  • 5fc74dd Reduce nesting.
  • 3d81dc3 Release version 1.14.8 of the npm package.
  • 62e546a Drop confidential headers across schemes.
  • See full diff 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 use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

Bumps [follow-redirects](https://github.com/follow-redirects/follow-redirects) from 1.14.7 to 1.14.9.
- [Release notes](https://github.com/follow-redirects/follow-redirects/releases)
- [Commits](follow-redirects/follow-redirects@v1.14.7...v1.14.9)

---
updated-dependencies:
- dependency-name: follow-redirects
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label Feb 26, 2022
@dependabot @github

dependabot Bot commented on behalf of github Apr 20, 2022

Copy link
Copy Markdown
Author

Looks like follow-redirects is up-to-date now, so this is no longer needed.

@dependabot dependabot Bot closed this Apr 20, 2022
@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/follow-redirects-1.14.9 branch April 20, 2022 04:37
pull Bot pushed a commit that referenced this pull request Oct 16, 2025
…lessAggressive`

This test is intermittently failing with the following error:

  [ RUN      ] DomainBlockTest.NoInterstitialUnlessAggressive
  [806484:806484:1015/131900.057034:FATAL:content/public/test/browser_test_utils.cc:1627] Check failed: is_ok(). Can't ExtractString() because the script encountered a problem: a JavaScript error: "RenderFrame deleted."
  #0 0x652c37727912 base::debug::CollectStackTrace() [../../base/debug/stack_trace_posix.cc:1052:7]
  #1 0x652c3770f131 base::debug::StackTrace::StackTrace() [../../base/debug/stack_trace.cc:279:20]
  #2 0x652c376067da logging::LogMessage::Flush() [../../base/logging.cc:705:29]
  #3 0x652c3760669d logging::LogMessage::~LogMessage() [../../base/logging.cc:694:3]
  #4 0x652c375ec212 logging::(anonymous namespace)::CheckLogMessage::~CheckLogMessage() [../../base/check.cc:164:3]
  #5 0x652c375ebefb logging::CheckNoreturnError::~CheckNoreturnError() [../../base/check.cc:321:16]
  #6 0x652c3ffd799c content::EvalJsResult::ExtractString() [../../content/public/test/browser_test_utils.cc:1627:3]
  #7 0x652c3ffdb53e content::WaitForRenderFrameReady() [../../content/public/test/browser_test_utils.cc:2300:12]
  #8 0x652c2db6534a DomainBlockTestBase::NavigateTo() [../../brave/browser/brave_shields/domain_block_page_browsertest.cc:61:5]
  #9 0x652c2db68e30 DomainBlockTest_NoInterstitialUnlessAggressive_Test::RunTestOnMainThread() [../../brave/browser/brave_shields/domain_block_page_browsertest.cc:359:3]
  #10 0x652c3ffd2b4e content::BrowserTestBase::ProxyRunTestOnMainThreadLoop() [../../content/public/test/browser_test_base.cc:974:9]
  #11 0x652c2db7e811 base::OnceCallback<>::Run() [../../base/functional/callback.h:155:12]
  #12 0x652c328fb0a1 content::BrowserMainRunnerImpl::Run() [../../content/browser/browser_main_runner_impl.cc:150:15]
  #13 0x652c328f4dd0 content::BrowserMain() [../../content/browser/browser_main.cc:32:28]
  #14 0x652c34e3c272 content::RunBrowserProcessMain() [../../content/app/content_main_runner_impl.cc:702:10]
  #15 0x652c34e3ebda content::ContentMainRunnerImpl::RunBrowser() [../../content/app/content_main_runner_impl.cc:1289:10]
  #16 0x652c34e3e3b4 content::ContentMainRunnerImpl::Run() [../../content/app/content_main_runner_impl.cc:1128:12]
  #17 0x652c34e3ac6b content::RunContentProcess() [../../content/app/content_main.cc:346:36]
  #18 0x652c34e3add4 content::ContentMain() [../../content/app/content_main.cc:359:10]
  #19 0x652c3ffd19a7 content::BrowserTestBase::SetUp() [../../content/public/test/browser_test_base.cc:609:3]
  #20 0x652c36e01e58 InProcessBrowserTest::SetUp() [../../chrome/test/base/in_process_browser_test.cc:535:20]
  #21 0x652c2db6a806 DomainBlockTestBase::SetUp() [../../brave/browser/brave_shields/domain_block_page_browsertest.cc:47:25]
  #22 0x652c35ad79f0 testing::Test::Run() [../../third_party/googletest/src/googletest/src/gtest.cc:5267:3]
  #23 0x652c35ad8852 testing::TestInfo::Run() [../../third_party/googletest/src/googletest/src/gtest.cc:2892:11]
  #24 0x652c35ad9467 testing::TestSuite::Run() [../../third_party/googletest/src/googletest/src/gtest.cc:3070:30]
  #25 0x652c35ae71c7 testing::internal::UnitTestImpl::RunAllTests() [../../third_party/googletest/src/googletest/src/gtest.cc:6062:44]
  #26 0x652c35ae69af testing::UnitTest::Run() [../../third_party/googletest/src/googletest/src/gtest.cc:5267:3]
  #27 0x652c3ff5c1ba base::TestSuite::Run() [../../base/test/test_suite.cc:438:16]
  #28 0x652c36dfffa6 ChromeTestSuiteRunner::RunTestSuite() [../../chrome/test/base/chrome_test_launcher.cc:102:22]
  #29 0x652c36e002df ChromeTestLauncherDelegate::RunTestSuite() [../../chrome/test/base/chrome_test_launcher.cc:156:19]
  #30 0x652c3fffdf44 content::LaunchTestsInternal() [../../content/public/test/test_launcher.cc:424:31]
  #31 0x652c3fffe555 content::LaunchTests() [../../content/public/test/test_launcher.cc:519:10]
  #32 0x652c36e0058b LaunchChromeTests() [../../chrome/test/base/chrome_test_launcher.cc:357:10]
  #33 0x652c35cacfc5 main [../../brave/test/base/browser_tests_main.cc:66:10]
  #34 0x781a84a29d90 (/usr/lib/x86_64-linux-gnu/libc.so.6+0x29d8f)
  #35 0x781a84a29e40 __libc_start_main
  #36 0x652c2dafe02a _start

There doesn't seem to be an actual need to wait for the render frame in that
utility method, so I removed it and verified that all tests pass.
pull Bot pushed a commit that referenced this pull request Mar 27, 2026
Chromium changes:
https://chromium.googlesource.com/chromium/src/+/b3f1b6b71c7b8c6587f4788d009574d7e47f9409

commit b3f1b6b71c7b8c6587f4788d009574d7e47f9409
Author: Aishwarya Rajesh <[email protected]>
Date:   Fri Feb 13 15:04:51 2026 -0800

    [MIR] Cleanup moveTabs* APIs

    See updated bug description for rationale on updates in this CL.

    At the end of this CL, we will have 3 APIs to move tabs to a window:

    1. moveTabsToNewWindow(): Moves tabs to a brand new window. This will
    show a message at instance limit.
    2. moveTabsToWindowByIdChecked(): Moves tabs to an active instance or
    creates a new activity for an inactive instance or an active instance
    that has its activity destroyed. This API will fail if the id provided
    does not have persisted state.
    3. moveTabsToOtherWindow(): Gives the user a chance to select a window
    from the TargetSelectorDialog to move the tabs to. This implicitly
    invokes #2 for a window selected from the dialog and #1 if we have
    exactly one eligible window running currently.

    Bug: 476106567
    Change-Id: I701f46a1090220d4f9db705cb4df803b30ac284a
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7564470
    Commit-Queue: Aishwarya Rajesh <[email protected]>
    Reviewed-by: Sirisha Kavuluru <[email protected]>
    Cr-Commit-Position: refs/heads/main@{#1584943}
pull Bot pushed a commit that referenced this pull request Jun 17, 2026
Fix PermissionLifetimeManagerTest.ExternalContentSettingChange:
PermissionDecided stores expirations under the type returned by
GeolocationContentSettingsType() — which is GEOLOCATION_WITH_OPTIONS on
Android — while SetContentSettingDefaultScope fires notifications for plain
GEOLOCATION. OnContentSettingChanged found nothing in expirations keyed
under GEOLOCATION_WITH_OPTIONS and returned early without stopping the timer.
Using GEOLOCATION_WITH_OPTIONS directly in the test also crashes: it is
registered only in PermissionSettingsRegistry::Init(), never through
ContentSettingsRegistry::Register(), so GetContentSetting() hits NOTREACHED
via CheckContentTypeRegistration → ContentSettingsRegistry::Get().
Fix: switch ExternalContentSettingChange to ContentSettingsType::NOTIFICATIONS
which has no platform-specific aliasing and tests the same PLM observer
behaviour end-to-end.

Fix PermissionLifetimeManagerTest.DifferentTypePermissions:
Same root cause — GEOLOCATION maps to GEOLOCATION_WITH_OPTIONS on Android,
causing a pref key mismatch ("geolocation-with-options" vs "geolocation") and
a CHECK crash in ResetPermission when the expiration timer fires:
SetContentSettingDefaultScope CHECKs the type is in ContentSettingsRegistry
but GEOLOCATION_WITH_OPTIONS is not.
Fix: replace GEOLOCATION with ContentSettingsType::MEDIASTREAM_MIC (pref name
"media-stream-mic"), which has no Android aliasing and is in
ContentSettingsRegistry.

Chromium change #1:
https://source.chromium.org/chromium/chromium/src/+/96d8c5eb0773a93cf85aeb73e97c822c379c8d26

commit 96d8c5eb0773a93cf85aeb73e97c822c379c8d26
Author: Antonio Sartori <[email protected]>
Date:   Thu May 7 10:48:35 2026 -0700

    [permissions] Enable kApproximateGeolocationPermission on Android

    Bug: b:385175104
    Change-Id: Ic2ec4f1aede76b77a6e7439716680d72c79a5ebf
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7817479
    Commit-Queue: Antonio Sartori <[email protected]>
    Reviewed-by: Christian Dullweber <[email protected]>
    Cr-Commit-Position: refs/heads/main@{#1627060}

Chromium change #2:
https://source.chromium.org/chromium/chromium/src/+/a5ecb6cb4578e057fc3ab9b2b025284f92a9c61d

commit a5ecb6cb4578e057fc3ab9b2b025284f92a9c61d
Author: Antonio Sartori <[email protected]>
Date:   Mon Jan 26 03:22:47 2026 -0800

    [permissions] Use GeolocationContentSettingsType in request_type

    This is a small no-op refactoring that uses the newly added
    GeolocationContentSettingsType() to simplify the code in
    //components/permissions/request_type.cc.

    Bug: 476929911
    Change-Id: Ifd8e8a2a1f91f1ac5335d87f1090b19719e87e27
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7510627
    Reviewed-by: Christian Dullweber <[email protected]>
    Commit-Queue: Christian Dullweber <[email protected]>
    Auto-Submit: Antonio Sartori <[email protected]>
    Cr-Commit-Position: refs/heads/main@{#1574428}

AI-assisted commit
pull Bot pushed a commit that referenced this pull request Jun 17, 2026
Chromium change #1:
https://source.chromium.org/chromium/chromium/src/+/f1eaa36019a8307c3a922ee44e957a9bc9330520

commit f1eaa36019a8307c3a922ee44e957a9bc9330520
Author: Xuehui Chen <[email protected]>
Date:   Wed May 27 09:11:57 2026 -0700

    Reland "[SplitCompatService][1/4] Fork SplitCompatService to base module"

    This is a reland of commit bbee16fd6c12bc296ad65aed569be9a21076a4a5

    With modification of moving Clank dependencies back to service_java.
    This `uncleaned` split situation is due to Clank repo won't have
    service_impl_java visible to it until this change is merged. In a follow
    up with Clank update, we need two more cls to 1: Add service_impl_java
    to clank's dependency 2. Move dependencies back to service_impl_java

    Original change's description:
    > [SplitCompatService][1/4] Fork SplitCompatService to base module
    >
    > SplitCompatService allows services to reside inside dynamic feature
    > modules (splits) while exposing a thin shell service in the base module
    > so the Android framework can discover and bind them.
    >
    > Previously, the SplitCompatService base class resided in the chrome
    > module (org.chromium.chrome.browser.base.SplitCompatService). As a
    > result, declaring these services as standard Android Services in the
    > base module forced their direct and transitive dependencies to be
    > packaged into the base split, causing base module binary size increase
    > whenever new service dependencies were added.
    >
    > This CL forks SplitCompatService to the base module as
    > org.chromium.base.SplitCompatService, making it accessible to
    > chrome/clank modules, and deprecates the original chrome-specific
    > version so that future service migrations can transition to the base
    > version. The new SplitCompatService directly uses BundleUtils instead of
    > SplitCompatUtils to load class and starts to accept splitName as
    > parameter.
    >
    > Additionally, this CL migrates PaymentDetailsUpdateService in components
    > payments to use the base SplitCompatService. The service is split into a
    > thin shell residing in the base module and the real
    > implementation(PaymentDetailsUpdateServiceImpl) in the chrome split
    > module.
    >
    > Bug: b:507013097
    > Test: binary size check passed with expected size reduction
    > Change-Id: I8b4df71d2b567c2953352d754e336471023283cd
    > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7864043
    > Owners-Override: Andrew Grieve <[email protected]>
    > Reviewed-by: Andrew Grieve <[email protected]>
    > Reviewed-by: Slobodan Pejic <[email protected]>
    > Commit-Queue: Xuehui Chen <[email protected]>
    > Cr-Commit-Position: refs/heads/main@{#1635767}

    Bug: b:507013097
    Change-Id: Ief96c145cc1e5eece1947c1ec2065430df0544e0
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7873579
    Reviewed-by: Andrew Grieve <[email protected]>
    Reviewed-by: Slobodan Pejic <[email protected]>
    Commit-Queue: Andrew Grieve <[email protected]>
    Owners-Override: Andrew Grieve <[email protected]>
    Cr-Commit-Position: refs/heads/main@{#1637005}

Chromium change #2:
https://source.chromium.org/chromium/chromium/src/+/288ae652477f2d1a83a00ce26d2e63d716b05a3f

commit 288ae652477f2d1a83a00ce26d2e63d716b05a3f
Author: Xuehui Chen <[email protected]>
Date:   Mon Jun 1 09:03:31 2026 -0700

    [SplitCompatService][4/4] Remove deprecated SplitCompatService and clean

    up dependencies

    This change removes the deprecated SplitCompatService from the chrome
    base module in favor of the implementation in //base.

    Additionally, it cleans up build dependencies in the payments component
    since internal Clank now depend on the service_impl_java target. This
    moves implementation-specific sources and dependencies from service_java
    to service_impl_java.

    Bug: b:507013097
    Change-Id: I4be6b11750778cf726c5105dff555452a509fdf4
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7880330
    Reviewed-by: Andrew Grieve <[email protected]>
    Commit-Queue: Xuehui Chen <[email protected]>
    Reviewed-by: Slobodan Pejic <[email protected]>
    Cr-Commit-Position: refs/heads/main@{#1639438}
pull Bot pushed a commit that referenced this pull request Jul 15, 2026
AI-assisted commit.

Always exclude the shared Brave bundles. Brave's cr_elements
overrides (e.g. cr_button) import these from chrome://resources/brave/,
which is a separately-built shared resource and must be treated as
external rather than inlined into every bundle. The matching
external_paths are added unconditionally, so the excludes have to be
added unconditionally too (direct bundle_js() callers don't go through
BUNDLE_JS_EXCLUDES).

Chromium change:
https://source.chromium.org/chromium/chromium/src/+/6e7741f7685746e77948b9d7cbef302116388adb

commit 6e7741f7685746e77948b9d7cbef302116388adb
Author: Moe Ahmadi <[email protected]>
Date:   Mon Jun 29 18:20:10 2026 -0700

    Reland "Package AIM eligibility WebUI in a component extension"

    This reverts commit e6f2341d618f1986ab20bcf54b32020c1d4ad795.

    Reason for revert: Fixed Linux Chromium OS ASan LSan Tests
    https://chromium-review.git.corp.google.com/c/chromium/src/+/8016355/1..2

    Original change's description:
    > Revert "Package AIM eligibility WebUI in a component extension"
    >
    > This reverts commit 0da20f56cd961295426ad21bba896042b4c3c736.
    >
    > Reason for revert:
    > Newly added test AimEligibilityExtensionBrowserTest.UiParity fails on Linux Chromium OS ASan LSan Tests (1)
    >
    > Bot link with this changelist and that shows the failure:
    > https://ci.chromium.org/ui/p/chromium/builders/ci/Linux%20Chromium%20OS%20ASan%20LSan%20Tests%20(1)/69997/overview
    >
    > summary of failure:
    > external_metrics.cc(234): ASan stack-use-after-return
    >
    > longer paste of part of failure message:
    > ==2594501==ERROR: AddressSanitizer: stack-use-after-return on address 0x73cfa669f060 at pc 0x574ca824804a bp 0x7ffcdcffc2a0 sp 0x7ffcdcffc298
    > READ of size 1 at 0x73cfa669f060 thread T0 (browser_tests)
    > 2026-06-29T20:51:04.048035Z ERROR browser_tests[2594501:2594626]: [chrome/browser/ash/external_metrics/external_metrics.cc:234] Failed to create DirReaderPosix. Cannot read early per-pid uma files.
    > 2026-06-29T20:51:04.048220Z ERROR browser_tests[2594501:2594626]: [chrome/browser/ash/external_metrics/external_metrics.cc:251] Failed to create DirReaderPosix. Cannot read per-pid uma files.
    >     #0 0x574ca8248049 in bool std::__Cr::__function::__policy_func<bool ()>::__call_func<extensions::AimEligibilityExtensionBrowserTest_UiParity_Test::RunTestOnMainThread()::$_0>(std::__Cr::__function::__policy_storage const*) chrome/browser/ui/webui/omnibox/aim_eligibility/extension/aim_eligibility_extension_browsertest.cc:147:12
    >     #1 0x574ca1921588 in testing::internal::FunctionMocker<bool ()>::PerformAction(void const*, std::__Cr::tuple<>&&, std::__Cr::basic_string<char, std::__Cr::char_traits<char>, std::__Cr::allocator<char>> const&) const third_party/libc++/src/include/__functional/function.h:502:12
    >     #2 0x574ca192105b in testing::internal::FunctionMocker<bool ()>::InvokeWith(std::__Cr::tuple<>&&) third_party/googletest/src/googlemock/include/gmock/gmock-spec-builders.h:1869:12
    > ...
    >
    > Original change's description:
    > > Package AIM eligibility WebUI in a component extension
    > >
    > > Embeds the AIM eligibility debug page chrome://omnibox/aim-eligibility
    > > into a private component extension as a proof of concept with the goal
    > > of reusing existing WebUI frontend and backend logic within an extension
    > > context without significant duplication or boilerplate.
    > >
    > > A new keyed service, AimEligibilityExtensionBridge, serves as a direct
    > > Mojo IPC bridge between the extension and the backend. This bridge
    > > manages AimEligibilityPageHandler instances, bypassing the need for
    > > standard dictionary-based extension API serialization.
    > >
    > > To support this implementation, the extension is allowlisted to enable
    > > V8 Mojo bindings within the renderer.
    > >
    > > Additionally, the build process uses the bundle_js to bundle the extension's JS resources. This automatically resolves and maps shared
    > > WebUI dependencies to absolute chrome:// URLs, ensuring the extension
    > > complies with Manifest V3 CSP requirements while reusing WebUI
    > > resources.
    > >
    > > http://screen/6KR4HmEsuVVWMxF
    > >
    > > Bug: b:524201650
    > >
    > > Change-Id: Ie69aa43abe5822a6eb40c31fd37bdb28bed3e032
    > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7921547
    > > Reviewed-by: Devlin Cronin <[email protected]>
    > > Reviewed-by: Colin Blundell <[email protected]>
    > > Commit-Queue: Moe Ahmadi <[email protected]>
    > > Cr-Commit-Position: refs/heads/main@{#1654190}
    >
    > Bug: b:524201650
    > No-Presubmit: true
    > No-Tree-Checks: true
    > No-Try: true
    > Change-Id: I29afb352b9de95a2bd48b71d98bf40d6324c0016
    > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8020996
    > Bot-Commit: [email protected] <[email protected]>
    > Commit-Queue: Mark Pearson <[email protected]>
    > Owners-Override: Mark Pearson <[email protected]>
    > Cr-Commit-Position: refs/heads/main@{#1654424}

    Bug: b:524201650
    Change-Id: I85808ab703dfc807b16debc87238d9ddbd699923
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8016355
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CI/run-audit-deps dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants