Skip to content

chore(deps): bump phoenix to 1.7.23#978

Open
MorganaFuture wants to merge 2 commits into
supabase:mainfrom
MorganaFuture:MorganaFuture/bump-phoenix-1.7.23
Open

chore(deps): bump phoenix to 1.7.23#978
MorganaFuture wants to merge 2 commits into
supabase:mainfrom
MorganaFuture:MorganaFuture/bump-phoenix-1.7.23

Conversation

@MorganaFuture
Copy link
Copy Markdown

What kind of change?

Security dependency bump.

Current behavior

Phoenix 1.7.20 is affected by GHSA-628h-q48j-jr6q (high):
long-poll NDJSON body splitting causes large memory allocation.
mix deps.audit fails CI.

New behavior

Bump Phoenix to 1.7.23 (first patched: 1.7.22). ~> 1.7.2 in
mix.exs already allows this — only mix.lock changes.

@MorganaFuture MorganaFuture requested a review from a team as a code owner May 12, 2026 09:52
Phoenix 1.7.20 is affected by a high-severity advisory: long-poll
NDJSON body splitting causes large memory allocation. Fixed in 1.7.22.
@MorganaFuture MorganaFuture force-pushed the MorganaFuture/bump-phoenix-1.7.23 branch from c62dd83 to 533672b Compare May 12, 2026 09:53
Switch the security workflow trigger from pull_request_target to
pull_request so that mix deps.audit and sobelow actually scan the
code being proposed. With pull_request_target, actions/checkout
defaults to the base branch (main), so PRs that fix or introduce
vulnerabilities are scanned against main and the result is the same
on every PR.

The dependency-submission step still requires write access (which
pull_request from forks cannot grant), so guard it with
`if: github.event_name != 'pull_request'`. The submission continues
to run on push to main and on the daily schedule.
@MorganaFuture
Copy link
Copy Markdown
Author

@v0idpwn Could you please take a look? Right now the pull_request_target trigger means this audit always scans main, not the PR diff. This pr should fix it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant