Skip to content

[Snyk] Upgrade axios from 0.25.0 to 0.27.2#8

Closed
ekaterinamishina wants to merge 1 commit into
mainfrom
snyk-upgrade-ea2ab200ee3185ad38c55f399da94cf6
Closed

[Snyk] Upgrade axios from 0.25.0 to 0.27.2#8
ekaterinamishina wants to merge 1 commit into
mainfrom
snyk-upgrade-ea2ab200ee3185ad38c55f399da94cf6

Conversation

@ekaterinamishina
Copy link
Copy Markdown
Contributor

@ekaterinamishina ekaterinamishina commented Feb 28, 2024

Snyk has created this PR to upgrade axios from 0.25.0 to 0.27.2.

As this is a private repository, Snyk-bot does not have access. Therefore, this PR has been created automatically, but appears to have been created by a real user.

✨ Snyk has automatically assigned this pull request, set who gets assigned.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

  • The recommended version is 5 versions ahead of your current version.
  • The recommended version was released 2 years ago, on 2022-04-27.
Release notes
Package name: axios
  • 0.27.2 - 2022-04-27

    Fixes and Functionality:

    • Fixed FormData posting in browser environment by reverting #3785 (#4640)
    • Enhanced protocol parsing implementation (#4639)
    • Fixed bundle size
  • 0.27.1 - 2022-04-26

    Fixes and Functionality:

    • Removed import of url module in browser build due to huge size overhead and builds being broken (#4594)
    • Bumped follow-redirects to ^1.14.9 (#4615)
  • 0.27.0 - 2022-04-25

    Breaking changes:

    • New toFormData helper function that allows the implementor to pass an object and allow axios to convert it to FormData (#3757)
    • Removed functionality that removed the the Content-Type request header when passing FormData (#3785)
    • (*) Refactored error handling implementing AxiosError as a constructor, this is a large change to error handling on the whole (#3645)
    • Separated responsibility for FormData instantiation between transformRequest and toFormData (#4470)
    • (*) Improved and fixed multiple issues with FormData support (#4448)

    QOL and DevX improvements:

    • Added a multipart/form-data testing playground allowing contributors to debug changes easily (#4465)

    Fixes and Functionality:

    • Refactored project file structure to avoid circular imports (#4515) & (#4516)
    • Bumped follow-redirects to ^1.14.9 (#4562)

    Internal and Tests:

    • Updated dev dependencies to latest version

    Documentation:

    • Fixing incorrect link in changelog (#4551)

    Notes:

    • (*) Please read these pull requests before updating, these changes are very impactful and far reaching.
  • 0.26.1 - 2022-03-09

    Fixes and Functionality:

    • Refactored project file structure to avoid circular imports (#4220)
  • 0.26.0 - 2022-02-13

    Fixes and Functionality:

    • Fixed The timeoutErrorMessage property in config not work with Node.js (#3581)
    • Added errors to be displayed when the query parsing process itself fails (#3961)
    • Fix/remove url required (#4426)
    • Update follow-redirects dependency due to Vulnerability (#4462)
    • Bump karma from 6.3.11 to 6.3.14 (#4461)
    • Bump follow-redirects from 1.14.7 to 1.14.8 (#4473)
  • 0.25.0 - 2022-01-18

    Breaking changes:

    • Fixing maxBodyLength enforcement (#3786)
    • Don't rely on strict mode behaviour for arguments (#3470)
    • Adding error handling when missing url (#3791)
    • Update isAbsoluteURL.js removing escaping of non-special characters (#3809)
    • Use native Array.isArray() in utils.js (#3836)
    • Adding error handling inside stream end callback (#3967)

    Fixes and Functionality:

    • Added aborted even handler (#3916)
    • Header types expanded allowing boolean and number types (#4144)
    • Fix cancel signature allowing cancel message to be undefined (#3153)
    • Updated type checks to be formulated better (#3342)
    • Avoid unnecessary buffer allocations (#3321)
    • Adding a socket handler to keep TCP connection live when processing long living requests (#3422)
    • Added toFormData helper function (#3757)
    • Adding responseEncoding prop type in AxiosRequestConfig (#3918)

    Internal and Tests:

    • Adding axios-test-instance to ecosystem (#3786)
    • Optimize the logic of isAxiosError (#3546)
    • Add tests and documentation to display how multiple inceptors work (#3564)
    • Updating follow-redirects to version 1.14.7 (#4379)

    Documentation:

    • Fixing changelog to show corrext pull request (#4219)
    • Update upgrade guide for https proxy setting (#3604)

    Huge thanks to everyone who contributed to this release via code (authors listed below) or via reviews and triaging on GitHub:

from axios GitHub release notes
Commit messages
Package name: axios
  • bc733fe Releasing v0.27.2
  • b9e9fb4 Enhanced protocol parsing implementation to fix #4633; (#4639)
  • 76432c1 Fixed FormData posting in browser environment by reverting #3785; (#4640)
  • 82fd15f Combined build process and cleaned it up a bit
  • 1d82af1 Fixing issues with bundle sizes
  • bcb166e Fixed incorrect date in changelog
  • 838f53b Merge branch 'master' of github.com:axios/axios
  • cb9c534 Releasing v0.27.1
  • 91d21fc Releasing v0.72.1
  • 167cb8b Remove eslint-g package as this seems have been added in error
  • 4f7e3e3 Removed import of url module in browser build due to significant size overhead; (#4594)
  • cdd7add Fixed date on chnagelog
  • f94dda9 Bump async from 2.6.3 to 2.6.4 (#4615)
  • 008dd9d Releaseing version 0.27.0
  • ee151a7 Revert some changes that are only required when we actually release
  • 499d3be follow-redirects to ^1.14.9 (#4562)
  • d24ce8e Updated a number of out of date dev packages
  • 5b0d492 Bump minimist from 1.2.5 to 1.2.6 (#4574)
  • cdda1ad Merge branch 'carpben-env-form-data'
  • 3e0954d Fixed merge conflicts
  • a3dd603 Merge branch 'Tivix-fix#1603'
  • 9b8e004 Merge branch 'fix#1603' of https://github.com/Tivix/axios into Tivix-fix#1603
  • 1f13dd7 Fixed some imports that were not correct
  • 8699891 Fixed merge conflicts

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

👩‍💻 Set who automatically gets assigned

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@rbuergi rbuergi closed this Oct 7, 2024
@rbuergi rbuergi deleted the snyk-upgrade-ea2ab200ee3185ad38c55f399da94cf6 branch October 7, 2024 16:59
rbuergi added a commit that referenced this pull request May 5, 2026
@rbuergi @claude
fix(graph): NodeTypeContractHandler short-circuits ONLY when LatestRe…
c6de4cd 
…leasePath is set

Tasks #6, #7, #8, #9, #10, #11, #12, #13, #14 from the failing-tests list
share one root cause: NodeTypeContractHandler.Handle was short-circuiting
on node.AssemblyLocation alone. For freshly-created dynamic NodeTypes
(NodeType=NodeType, Content=NodeTypeDefinition), NodeTypeService
.EnrichWithNodeType propagates the STATIC "NodeType" type's framework DLL
(MeshWeaver.Graph.dll) onto the new node's AssemblyLocation through its
fast-path ApplyEntry. The handler then opened MeshWeaver.Graph.dll,
found no MeshNodeProvider for the new hub's path, and silently returned
Success=true with empty NodeTypeConfigurations — so:

- CompileFailsWhenSourceCodeIsInvalid sees Success=true (compile never
  actually ran).
- CompileWithMultipleSourceLocationsPullsInExternalCode misses the
  external Profile type for the same reason.
- CompileActivityLogTest.* never produces an activity log because the
  Roslyn compile never ran.
- LinkedIn* tests can't render their NodeType-bound layout areas.
- MeshPluginTest broken-NodeType tests don't see the compile error
  because no compile happened.

Fix: only take the short-circuit path when def.LatestReleasePath is
non-empty. A populated LatestReleasePath means StartCompile (or a
release publish) has actually emitted an assembly for THIS NodeType;
only then is AssemblyLocation a real release DLL. Otherwise fall through
to compilationService.CompileAndGetConfigurations, which runs Roslyn,
returns the real Success/Failed shape, and lets the cluster behave.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@rbuergi rbuergi mentioned this pull request May 10, 2026
Open
10 tasks
rbuergi added a commit that referenced this pull request May 10, 2026
@rbuergi @claude
test(threading,thread-exec): batch C — stable lifecycle assertions + …
eea8ed1 
…ThreadExecution stability fixes

ThreadExecution.cs (already in commit 478fdaa — recapping here for the
review-item index):
  - RecoverStaleExecutingThread: drop the 2-minute "fresh execution"
    window in favour of a structural check (skip when PendingUserMessage
    + ActiveMessageId are still set, i.e. the thread is an
    auto-execute candidate WatchForExecution will pick up). Closes the
    "long-running agent crashed at minute 5 → IsExecuting=true forever"
    gap; the time-based heuristic contradicted commit 6dc436b's
    "no time limits" stance.
  - Subject<StreamingSnapshot>: declare with `using var` so the
    Subject itself disposes alongside its subscription. Minor leak
    per execution previously.
  - HandleSubmitMessage: pre-allocate the per-round
    CancellationTokenSource and store it on the thread hub BEFORE
    posting SubmitMessageResponse — closes the race where an early
    Stop click between IsExecuting=true and ExecuteMessageAsync's
    `parentHub.Set(executionCts)` found a null CTS slot and
    silently no-op'd. ExecuteMessageAsync now reuses the
    pre-allocated CTS (with a fallback for the auto-execute path
    that bypasses HandleSubmitMessage).

IsExecutingLifecycleTest.cs:
  - Migrate the response-text wait from text-pattern matching
    (skipping placeholders "Allocating agent..." etc.) to
    `ThreadMessage.CompletedAt is not null`, which
    ExecuteMessageAsync sets only on the terminal
    PushToResponseMessage call. Same pattern adopted in
    ChatHistoryTest in commit ab3af8b.
  - Add a regression assertion that final
    ThreadMessage.Status == Completed. The terminal-status guard in
    PushToResponseMessage prevents the late Sample(100ms)-flushed
    Streaming push from regressing the cell from Completed back to
    Streaming; this assertion catches any future regression of that
    guard.

Addresses PR #95 review items #5, #6, #7, #8, #10.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
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

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@ekaterinamishina @rbuergi @akravets-sm @snyk-bot