Repository navigation
deps(deps): bump the major group across 1 directory with 2 updates - #259
Merged
Merged
Conversation
Contributor
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
All alerts resolved. Learn more about Socket for GitHub. This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored. |
Bumps the major group with 2 updates in the / directory: [@alpacahq/alpaca-trade-api](https://github.com/alpacahq/alpaca-trade-api-js) and [framer-motion](https://github.com/motiondivision/motion). Updates `@alpacahq/alpaca-trade-api` from 4.0.4 to 5.0.0 - [Release notes](https://github.com/alpacahq/alpaca-trade-api-js/releases) - [Changelog](https://github.com/alpacahq/alpaca-trade-api-js/blob/master/CHANGELOG.md) - [Commits](alpacahq/alpaca-trade-api-js@v4.0.4...v5.0.0) Updates `framer-motion` from 13.4.4 to 14.0.0 - [Changelog](https://github.com/motiondivision/motion/blob/main/CHANGELOG.md) - [Commits](motiondivision/motion@v13.4.4...v14.0.0) --- updated-dependencies: - dependency-name: "@alpacahq/alpaca-trade-api" dependency-version: 5.0.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: major - dependency-name: framer-motion dependency-version: 14.0.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/major-c28a26aef0
branch
from
October 6, 2026 00:22
7e2391b to
d9e5e52
Compare
ralyodio
added a commit
that referenced
this pull request
Oct 6, 2026
The expired and self-signed fetchUpstream cases reached expired.badssl.com and self-signed.badssl.com. When the runner could not reach them both failed with "fetch failed", which blocked Dependabot PR #259 although nothing it bumped is involved. They now run against HTTPS servers on 127.0.0.1 with certificates the openssl CLI mints at run time (no committed private keys). The expired cert comes from `openssl ca -selfsign` with past dates, which works on OpenSSL 3.0. Each case also asserts the certificate-fallback warning, so a 200 from the strict agent alone would fail; disabling the fallback fails both. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ralyodio
added a commit
that referenced
this pull request
Oct 6, 2026
…om (#260) The expired and self-signed fetchUpstream cases reached expired.badssl.com and self-signed.badssl.com. When the runner could not reach them both failed with "fetch failed", which blocked Dependabot PR #259 although nothing it bumped is involved. They now run against HTTPS servers on 127.0.0.1 with certificates the openssl CLI mints at run time (no committed private keys). The expired cert comes from `openssl ca -selfsign` with past dates, which works on OpenSSL 3.0. Each case also asserts the certificate-fallback warning, so a 200 from the strict agent alone would fail; disabling the fallback fails both. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps the major group with 2 updates in the / directory: @alpacahq/alpaca-trade-api and framer-motion.
Updates
@alpacahq/alpaca-trade-apifrom 4.0.4 to 5.0.0Release notes
Sourced from @alpacahq/alpaca-trade-api's releases.
Changelog
Sourced from @alpacahq/alpaca-trade-api's changelog.
Commits
b361187chore: version packages (#343)82f27d9feat: regenerate SDK for v5 with typed SSE support (#340)f72dbc8Bump image-size from 2.0.2 to 2.0.4 in /docs (#338)Updates
framer-motionfrom 13.4.4 to 14.0.0Changelog
Sourced from framer-motion's changelog.
... (truncated)
Commits
f5838cev14.0.0351f7d0Updating changelog5da7dcdMerge pull request #3889 from motiondivision/cursor/v14-remove-shims-4e790897128Remove 13.5.1 compatibility shims for framer-motion 13.0–13.4d4638eav13.5.143cd77eUpdating changelog7005965Merge pull request #3888 from motiondivision/cursor/restore-observe-timeline-...7bf77e9Merge pull request #3884 from motiondivision/cursor/sort-node-position-unmoun...c0495b0Merge pull request #3887 from motiondivision/cursor/exact-internal-deps-4e799a16751Honour deprecated rangeStart/rangeEnd in attachTimeline