chore(deps): bump expo-camera from 57.0.0 to 57.0.1 - #292
Merged
Conversation
dependabot
Bot
added
dependencies
Bumps [expo-camera](https://github.com/expo/expo/tree/HEAD/packages/expo-camera) from 57.0.0 to 57.0.1. - [Changelog](https://github.com/expo/expo/blob/main/CHANGELOG.md) - [Commits](https://github.com/expo/expo/commits/HEAD/packages/expo-camera) --- updated-dependencies: - dependency-name: expo-camera dependency-version: 57.0.1 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
RonenMars
force-pushed
the
dependabot/npm_and_yarn/expo-camera-57.0.1
branch
from
July 12, 2026 11:04
caa68c1 to
66f8a38
Compare
RonenMars
added a commit
that referenced
this pull request
Aug 1, 2026
…pped (#487) The doc existed only as an untracked working-tree file and still described the 2026-07-25 state, in which both stacks were open and unmerged. tb-mobile #419–#423 were all closed unmerged and the work reached `land/integration-prep` as five direct commits instead, tb-streamer #292–#294 all merged, issue #424 is closed, and four of the five dependabot PRs are gone. The base it named, `integration-merge-354-355-376`, does not exist on origin — the branch that does is `integration-merge-354-355-376-v2`. Resolved items keep their reasoning rather than being deleted, since that reasoning is why the decisions went the way they did. Two things got worse rather than better: the Expo issue draft for ITMS-90863 is gone with the `/private/tmp/` scratchpad that held it, and both docs branches are still unpushed, leaving the runbook inside a local worktree only.
RonenMars
added a commit
that referenced
this pull request
Aug 1, 2026
…pped (#487) The doc existed only as an untracked working-tree file and still described the 2026-07-25 state, in which both stacks were open and unmerged. tb-mobile #419–#423 were all closed unmerged and the work reached `land/integration-prep` as five direct commits instead, tb-streamer #292–#294 all merged, issue #424 is closed, and four of the five dependabot PRs are gone. The base it named, `integration-merge-354-355-376`, does not exist on origin — the branch that does is `integration-merge-354-355-376-v2`. Resolved items keep their reasoning rather than being deleted, since that reasoning is why the decisions went the way they did. Two things got worse rather than better: the Expo issue draft for ITMS-90863 is gone with the `/private/tmp/` scratchpad that held it, and both docs branches are still unpushed, leaving the runbook inside a local worktree only.
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
1 participant
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 expo-camera from 57.0.0 to 57.0.1.
Changelog
Sourced from expo-camera's changelog.
Commits
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 this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)