Repository navigation
chore(deps): bump semver from 7.7.4 to 7.8.5 in the npm-minor-and-patch group - #61
Closed
dependabot[bot] wants to merge 1 commit into
Closed
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps the npm-minor-and-patch group with 1 update: [semver](https://github.com/npm/node-semver). Updates `semver` from 7.7.4 to 7.8.5 - [Release notes](https://github.com/npm/node-semver/releases) - [Changelog](https://github.com/npm/node-semver/blob/main/CHANGELOG.md) - [Commits](npm/node-semver@v7.7.4...v7.8.5) --- updated-dependencies: - dependency-name: semver dependency-version: 7.8.5 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: npm-minor-and-patch ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
status: needs-triage
Contributor
Author
|
Looks like semver is updatable in another way, so this is no longer needed. |
dependabot
Bot
deleted the
dependabot/npm_and_yarn/npm-minor-and-patch-38d9abce04
branch
November 9, 2026 05:21
GFean
added a commit
that referenced
this pull request
Nov 9, 2026
Successful CLI uploads now include `success`, `projectId`, `channelId`, and the actual upload `serverUrl` in `bundle-drop-result.json`, alongside the existing result fields. Older backends retain null IDs; failed uploads report null IDs and their upload endpoint. The server URL comes from the endpoint used by the CLI, rather than response metadata. Adds coverage for successful/failed uploads, older backend responses, staging/production endpoints, and untrusted response server URLs. Only the CLI source and tests change; no README, dependency, version, native runtime, or fingerprint baseline changes. Validation: `yarn verify:quick` on Node 22.13.0 passed: 105 suites / 2,237 tests, with 1 suite / 5 existing skips; coverage gate, frozen fingerprint contract, 12 Expo plugin checks, and 362-file package inspection passed. GitHub CI will run the platform and packaged CLI matrix. Dependabot #61 remains separate because its semver update requires review against the frozen fingerprint contract.
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 npm-minor-and-patch group with 1 update: semver.
Updates
semverfrom 7.7.4 to 7.8.5Release notes
Sourced from semver's releases.
Changelog
Sourced from semver's changelog.
Commits
6e05b76chore: release 7.8.5 (#879)9c8692afix: include prereleases in tilde range lower bound with includePrerelease (#...8640bd6chore: release 7.8.4 (#875)e583226fix: reject numeric segments after x-ranges6b77aa8chore: release 7.8.3 (#873)3485ddachore: bump@npmcli/eslint-configfrom 6.0.1 to 7.0.0 (#866)046da7ffix: align caret includePrerelease lower bounds (#872)efafcf8chore: release 7.8.2 (#871)bea6028fix: increment dotted prerelease identifiers (#870)7641608chore: release 7.8.1 (#868)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions