Bump delight-im/auth from 8.3.0 to 9.0.0#17
Conversation
Bumps [delight-im/auth](https://github.com/delight-im/PHP-Auth) from 8.3.0 to 9.0.0. - [Commits](delight-im/PHP-Auth@v8.3.0...v9.0.0) --- updated-dependencies: - dependency-name: delight-im/auth dependency-version: 9.0.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
dependencies
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: a4ed873e1a
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| "type": "project", | ||
| "require": { | ||
| "delight-im/auth": "^8.3", | ||
| "delight-im/auth": "^9.0", |
There was a problem hiding this comment.
Bumping delight-im/auth in composer.json without updating the committed src/vendor tree means the deployed image still runs v8.3.0, because the Docker build path only copies /src and does not run composer install (see Dockerfile build steps and .github/workflows/docker-image.yml). In this commit, src/vendor/composer/installed.json still records delight-im/auth as v8.3.0, so the intended upgrade to 9.0.0 is not actually shipped.
Useful? React with 👍 / 👎.
|
Looks like delight-im/auth is no longer updatable, so this is no longer needed. |
Bumps delight-im/auth from 8.3.0 to 9.0.0.
Commits
ef996fdUpdate dependencies245e10bExplain commercial support in README288bc1dSave all relevant user actions on 'Auth' interface to audit loged7fb0bImplement method 'Auth#logForAudit' for saving records to audit log68beb69Track which mechanism was used when successfully providing OTP for 2FA10cf5a3Capture 2FA configuration in variable before returning itcdcc820Determine if configuration had actually been active when disabling 2FA2d2ff46Improve code style1fc2a87Add database structure for audit log for SQLitef451437Add database structure for audit log for PostgreSQLDependabot 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)