chore(deps): bump better-auth from 1.4.7 to 1.4.9 in /apps/server#55
Open
dependabot[bot] wants to merge 1 commit intomainfrom
Open
chore(deps): bump better-auth from 1.4.7 to 1.4.9 in /apps/server#55dependabot[bot] wants to merge 1 commit intomainfrom
dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
Bumps [better-auth](https://github.com/better-auth/better-auth/tree/HEAD/packages/better-auth) from 1.4.7 to 1.4.9. - [Release notes](https://github.com/better-auth/better-auth/releases) - [Commits](https://github.com/better-auth/better-auth/commits/v1.4.9/packages/better-auth) --- updated-dependencies: - dependency-name: better-auth dependency-version: 1.4.9 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
dependencies
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| "@sinclair/typebox": "^0.34.15", | ||
| "better-auth": "1.4.7", | ||
| "better-auth": "1.4.9", | ||
| "drizzle-orm": "^0.44.7", |
Contributor
There was a problem hiding this comment.
The root bun.lock file was not updated as part of this PR and still references better-auth at 1.4.7. Because Bun resolves installed packages from the lockfile rather than package.json directly, any environment that runs bun install using the existing lockfile will continue to install 1.4.7 rather than the intended 1.4.9.
To fix, run bun install locally after merging (or as part of this PR) to regenerate bun.lock with the updated better-auth version, and commit the updated lockfile.
Prompt To Fix With AI
This is a comment left during a code review.
Path: apps/server/package.json
Line: 22
Comment:
**Lockfile not updated alongside package.json**
The root `bun.lock` file was not updated as part of this PR and still references `better-auth` at `1.4.7`. Because Bun resolves installed packages from the lockfile rather than `package.json` directly, any environment that runs `bun install` using the existing lockfile will continue to install `1.4.7` rather than the intended `1.4.9`.
To fix, run `bun install` locally after merging (or as part of this PR) to regenerate `bun.lock` with the updated `better-auth` version, and commit the updated lockfile.
How can I resolve this? If you propose a fix, please make it concise.
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 better-auth from 1.4.7 to 1.4.9.
Release notes
Sourced from better-auth's releases.
... (truncated)
Commits
35fcd1achore: release v1.4.9b96c38bMerge branch 'canary'148b32echore: release v1.4.85c2180efix: correct wildcard pattern matching fortrustedOrigins(#6904)ae90b48fix: correct wildcard pattern matching fortrustedOrigins(#6904)70d49e7fix: don't set state query param if state is not provided (#6822)cd77223fix: don't set state query param if state is not provided (#6822)60c77fafix: use operator in list members where clause (#6850)da82085fix: use operator in list members where clause (#6850)d808c31fix(client): set session data on refreshManager (#6932)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)You can disable automated security fix PRs for this repo from the Security Alerts page.
Greptile Summary
This PR bumps
better-authfrom1.4.7to1.4.9inapps/server, picking up several bug fixes (wildcardtrustedOriginsmatching, 2FA token cleanup, session cookie handling) and new features (OAuth 2.1 provider plugin, Patreon social provider, SAML security improvements). The change itself is straightforward, but thebun.locklockfile was not regenerated as part of this PR.apps/server/package.json;bun.lockwas not included in the diff and still recordsbetter-auth@1.4.7, meaningbun installon any CI or developer machine will continue to resolve the old version until the lockfile is regenerated and committed.Important Files Changed
Prompt To Fix All With AI
Reviews (1): Last reviewed commit: "chore(deps): bump better-auth from 1.4.7..." | Re-trigger Greptile