Repository navigation
Lock file maintenance - #25
Merged
Merged
Conversation
renovate
Bot
force-pushed
the
renovate/lock-file-maintenance
branch
from
November 2, 2026 03:36
22d53d1 to
21540db
Compare
renovate
Bot
force-pushed
the
renovate/lock-file-maintenance
branch
from
November 2, 2026 03:58
21540db to
a8d91d8
Compare
tyrsson
added a commit
that referenced
this pull request
Nov 2, 2026
…#27) Renovate PR #25 moves the php-db/phpdb dev dependency from source reference ed4a407c2f51b951e0261da0bf93baacb23d2e98 to 1570a6122cde75699394a6a38cf17335c3b1d622 on the 0.6.x branch. At 1570a612, Sql::buildSqlString() and Sql::prepareStatementForSqlObject() declare PhpDb\Sql\Exception\RuntimeException, so mago analyze reports unhandled-thrown-type at every call site in this package that was not declaring it, and possible-method-access-on-null where the code reads the magic `where` property of Select and Delete. Declare the exception with @throws where propagation is intended: InitDbCommand::executeDdl and execute; DbSessionHandler::destroy, gc, read, write, updateTimestamp and validateId; PhpDbSessionPersistence::initializeSessionFromRequest, persistSession and the private destroy. No exception is caught, no control flow is changed and runtime behaviour is identical; only docblocks and imports change. The three possible-method-access-on-null findings are recorded in analysis-baseline.toml rather than fixed in source. Select::__get() and Delete::__get() both return getWhere(), which is `return $this->where ??= new Where();`, so the null branch is unreachable at runtime; the nullable type comes only from the `@property ?Where $where` annotation on the vendor classes, which is expected to be corrected upstream. The baseline entries are the two issue blocks mago itself generates for those findings. composer.lock is untouched; the dependency change belongs to #25.
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
renovate
Bot
force-pushed
the
renovate/lock-file-maintenance
branch
from
November 2, 2026 04:10
3dac68b to
9a2a7d3
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.
This PR contains the following updates:
🔧 This Pull Request updates lock files to use the latest dependency versions.
Configuration
📅 Schedule: (in timezone UTC)
* 0-3 * * 1)🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
Read more information about the use of Renovate Bot.