Update phoenix_live_reload 1.3.3 → 1.5.3 (minor) #41
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.
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.5.3) · Repo · Changelog
Release Notes
1.4.1 (from changelog)
1.4.0 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 51 commits:
Release v1.5.3
Make debug level messages readable in light mode (#156)
Remove undefined warning on earlier Elixir versions
Release 1.5.2
Prevent dup level
Bump changelog
Merge pull request #150 from joshamb/main
Merge pull request #153 from walkr/patch-1
Do not send the whole metadata across processes
Update phoenix_live_reload.js
load dependencies in application start callback (#151)
Handle more log types (ie notice)
Release v1.5.1
Fix regression on Elixir v1.14 and earlier
Fix typo (#148)
Release 1.5.0
Merge pull request #147 from phoenixframework/cm-web-logger
s/connected/attached
Remove unused join key
Guard Mix.Project at runtime
Support umbrellas and deps
openEditorAtCaller and openEditorAtDef
PLUG_EDITOR
better error
Only support ELIXIR_EDITOR_URL export and warn if missing on openEditor
Fix docs
Refactor based on feedback
Docs
Docs
Docs
Use endpoint based config rather than global
Add web console logger and open file from client support
Update mix.exs
Add missing licence file
Bump minor version
Fix compilation warnings on newest Elixir (#138)
Fix typo, mesage -> message (#136)
Release 1.4.1
Merge pull request #131 from phoenixframework/bms_liveview_reload
add liveviews reload test
accepts multiple topics-patterns
send updates when liveview files are updated
Release v1.4.0
Update CHANGELOG
Make it clear it's only possible to watch dirs inside the project root (#128)
Document :dirs option (#126)
feat: Add option to trigger full page reloads on css changes (#123)
Handle multiple body tags, closes #119
Fix unexpected quirks mode notification in Chrome (#118)
Specify default
Add basic debouncing
Commits
See the full diff on Github. The new version differs by 14 commits:
bump v1.0.0
use apache license (#92)
update ci badge in readme (#91)
fix ci (#90)
fix ci
Don't cd into tmp dir (#79)
Add CI, remove warnings on Elixir v1.17-dev (#89)
fix: apply `CFLAGS` and `LDFLAGS` during build step (#87)
Update readme (#86)
Better character handling (#85)
Fix test failure (#83)
Test for unsupported :recursive value (#82)
Fix typos (#81)
Misc doc changes (#73)
👉 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 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