Skip to content

Conversation

@depfu
Copy link
Contributor

@depfu depfu bot commented Dec 9, 2025

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ phoenix_live_reload (1.3.3 → 1.6.2) · Repo · Changelog

Release Notes

1.6.2 (from changelog)

  • Bug fixes
    • Properly deal with Unicode when forwarding logs

1.6.1 (from changelog)

  • Enhancements
    • Set :phoenix_live_reload private field to downstream instrumentation
    • Add @import directive support to CSS reload strategy

1.6.0 (from changelog)

  • Enhancements

    • Add support for __RELATIVEFILE__ when invoking editors
    • Change the default target window to :parent to not reload the whole page if a Phoenix app is shown inside an iframe. You can get the old behavior back by setting the :target_window option to :top:
      config :phoenix_live_reload, MyAppWeb.Endpoint,
        target_window: :top,
        ...
  • Bug fixes

    • Inject iframe if web console logger is enabled but there are no patterns
    • Allow web console to shutdown cleanly

1.4.1 (from changelog)

  • Improvements
    • Support new :notify configuration for third-party integration to file change events

1.4.0 (from changelog)

  • Improvements
    • Allow reload events to be debounced instead of triggered immediately
    • Add option to trigger full page reloads on css changes
  • Bug fixes
    • Handle false positives on </body> tags

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 72 commits:

↗️ file_system (indirect, 0.2.10 → 1.1.1) · Repo

Commits

See the full diff on Github. The new version differs by 30 commits:


👉 No CI detected

You don't seem to have any Continuous Integration service set up!

Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.

This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:

* [Circle CI](https://circleci.com), [Semaphore ](https://semaphoreci.com) and [Github Actions](https://docs.github.com/actions) are all excellent options. * If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github. * If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with `depfu/`.

Depfu Status

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands
@​depfu rebase
Rebases against your default branch and redoes this update
@​depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@​depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@​depfu cancel merge
Cancels automatic merging of this PR
@​depfu close
Closes this PR and deletes the branch
@​depfu reopen
Restores the branch and reopens this PR (if it's closed)
@​depfu pause
Ignores all future updates for this dependency and closes this PR
@​depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@​depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant