Repository navigation
chore(deps): bump phoenix from 1.8.14 to 1.8.15 - #207
Merged
Merged
Conversation
dependabot
Bot
added
dependencies
Contributor
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Bumps [phoenix](https://github.com/phoenixframework/phoenix) from 1.8.14 to 1.8.15. - [Release notes](https://github.com/phoenixframework/phoenix/releases) - [Changelog](https://github.com/phoenixframework/phoenix/blob/v1.8.15/CHANGELOG.md) - [Commits](phoenixframework/phoenix@v1.8.14...v1.8.15) --- updated-dependencies: - dependency-name: phoenix dependency-version: 1.8.15 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/hex/phoenix-1.8.15
branch
from
October 7, 2026 07:15
828fbc6 to
d12a9f4
Compare
hyperpolymath
approved these changes
Oct 7, 2026
5 of 13 tasks
hyperpolymath
added a commit
that referenced
this pull request
Oct 7, 2026
## Summary bofig#211 pinned `elixir-ci-reusable.yml` to `1c62ff84`, the **pre-squash branch head** of standards#1190. That PR's body flagged the pin as provisional. When the branch was deleted after the squash merge, the SHA stopped resolving. Every `elixir-ci` run since then has failed at startup with **0 jobs**: | Time (UTC) | Event | Head | Conclusion | |---|---|---|---| | 07:13:27 | push | `f5e414f5` (#211 merge) | **success** | | 07:15:54 | pull_request | `d12a9f4e` | failure | | 09:59:28 | pull_request | `7c2b4129` | failure | | 10:02:03 | push | `e59b3f6d` (#207) | failure | | 10:02:07 | pull_request | `1e016a4c` | failure | | 10:03:48 | push | `cc41782a` (#208) | failure (run 37604869992) | This PR re-pins to `d7b85cac`, the squash merge on standards `main`. `git diff 1c62ff84 d7b85cac -- .github/workflows/elixir-ci-reusable.yml` is empty, so the called workflow is byte-identical. The pin is the only change, one line. ## Type of change - [x] 🐛 Bug fix (non-breaking change that fixes an issue): `elixir-ci` cannot start on `main`. - [ ] ✨ New feature: no. - [ ] 💥 Breaking change: no. - [ ] 🕳️ Soundness fix: no. The workflow is unchanged; only the ref changes. - [ ] 📖 Documentation: no. - [ ] 🧹 Refactor / tech debt: no. - [ ] ⚡ Performance: no. - [x] 🔧 Build / CI / tooling ## 📌 New pins - **Head SHA: `e9476eb`** (see the commit list for the full SHA) - **`hyperpolymath/standards/.github/workflows/elixir-ci-reusable.yml@d7b85cac57eb16edf51508d6f30806e86d63c9d3`** (standards#1190 squash merge, an ancestor of standards `main`). Was `@1c62ff84348892e4ee23ccf58576f8d1c728ddbe`, the deleted branch head. - The container digests are unchanged. `actions.lock` is unchanged: it records no reusable-workflow refs, and it held no `elixir-ci.yml` key at `f5e414f5` either, where the run was green. ## How has this been verified? - `git merge-base --is-ancestor d7b85cac origin/main` in the standards clone: true. - `git ls-remote origin ci/elixir-reusable-db-services`: empty, so the old pin's branch is gone. - `git diff 1c62ff84 d7b85cac -- .github/workflows/elixir-ci-reusable.yml`: empty. - `actionlint .github/workflows/elixir-ci.yml`: rc=0, no output. - The run on this PR is the end-to-end test. It should reproduce #211's result: 344 tests, 0 failures, 21 excluded. ## Checklist - [x] My commits are **signed** (`git commit -S`); `%G?` = `G`. - [ ] I ran the project's own checks/tests locally and they pass: no. This machine has no BEAM toolchain; CI is the test. - [ ] New files carry the correct `SPDX-License-Identifier`: n/a, no new files. - [x] Docs are updated, and no public claim now overstates what the code does: no docs are affected. - [x] I have not introduced a soundness hole. ## Notes for reviewers Lesson for the estate, recorded in dev-notes: never merge a caller pinned to a reusable's PR-branch head. Re-pin to the squash SHA **before** the callee's branch is deleted, or the caller breaks silently with a 0-job startup failure that check-run listings do not show. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01Vwyfa8Eq6GYCqYnwo4fqGb Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
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 phoenix from 1.8.14 to 1.8.15.
Release notes
Sourced from phoenix's releases.
Changelog
Sourced from phoenix's changelog.
Commits
bd18018fix version in package.json762d1a1Release v1.8.15f735b51Update assets405f892Fix async close leaking to replaced transport (#6854)968a940Restore NULL parameters on phx.gen.cert's public key algorithm (#6848)1d09594Remove stale test in Socket.TransportTest (#6849)04e14f1Bump Tailwind CLI in phx.new templates to 4.3.3 (#6845)d676d61Clarify potential resource exhaustion with long pollingd344b10docs: remove outdated problem statement from routing guide (#6841)