Update phoenix: 1.6.11 → 1.6.16 (patch)

[depfu]

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 (1.6.11 → 1.6.16) · Repo · Changelog

Commits

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

• Release 1.6.16
• Fix race condition in channels during leave on dup topic on longpoll (#5281)
• Add embed_templates to formatter locals
• Release 1.6.15
• Release 1.6.15
• Fix reconnecting websockets on heartbeat timeout (#4921)
• Bump phoenix_view
• Release 1.6.14
• Fix wildcard check_origin vulnerability.
• Release 1.6.13
• Fetch docker release image from API
• Bump package lock
• Release v1.6.12
• Update Dockerfile template (#4937)

✳️ jason (1.3.0 → 1.4.0) · Repo · Changelog

Release Notes

1.4.0

Enhancements

• Use the :erlang.float_to_binary(_, [:short]) function, instead of io_lib_format.fwrite_g/1
  where available (OTP 24.1+). This provides equivalent output with much less memory used
  and significantly improved performance.

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

Commits

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

• Release 1.4.0
• Bump bench deps
• Bump CI versions
• Bump deps
• Use float_to_binary [:short] if available
• Bump OTP version in GitHub Actions (#153)
• Update README.md (#152)
• fix release year (#146)

✳️ phoenix_html (3.2.0 → 3.3.0) · Repo · Changelog

Release Notes

3.3.0 (from changelog)

• Enhancements

  • Support deeply nested class lists
  • Implement Phoenix.HTML.Safe for URI
  • Implement Phoenix.HTML.FormData for Map

• Bug fix

  • Generate unique IDs for checkboxes based on the value
  • Use artificial button click instead of form.submit in JavaScript to trigger all relevant events
  • Fix a bug where false/true attributes in aria/data/phx would emit literal "true" and "false" values

• Deprecations

  • Phoenix.HTML.Tag.attributes_escape/1 is deprecated in favor of Phoenix.HTML.attributes_escape/1

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

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

✳️ phoenix_pubsub (2.0.0 → 2.1.1) · Repo · Changelog

Release Notes

2.1.1 (from changelog)

Enhancements

• Support compatibility with 2.0 nodes when pool_size is 1

2.1.0 (from changelog)

Enhancements

• Support handle_info callback on Phoenix.Tracker

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

Commits

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

• Release 2.1.1
• Rename first adapter in the pool for backwards compatability (#169)
• Release 2.1.0
• Fix return
• Add optional handle_info callback to tracker
• Add brackets (#166)
• Fix typos (#163)
• More docs
• Add a pool size to PG2 adapter
• Fix error in tracker
• Clean up tracker docs
• Fix missing update for subscribe method description (#146)
• docs(Adapter): include variable names in callbacks (#139)
• Fix docs on Phoenix.PubSub module (#140)
• Fixes a typo in the README (#142)

✳️ plug_cowboy (2.5.2 → 2.6.0) · Repo · Changelog

Release Notes

2.6.0 (from changelog)

Enhancements

• Support websocket upgrades
• Require Plug v1.14+ and Elixir v1.10+

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

Commits

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

• Release v2.6.0
• More fixes
• Prepare for 2.6.0
• Implement WebSocket support based on Plug.Conn.Adapter.upgrade/3 (#88)
• Use erlef/setup-beam for GH action (#82)
• Add 1.13 to CI matrix (#81)
• Update ci.yml

↗️ phoenix_view (indirect, 1.0.0 → 2.0.2) · Repo · Changelog

Release Notes

2.0.2 (from changelog)

• Fix regression where directories were not being tracked for new files

2.0.0 (from changelog)

• Extract Phoenix.Template to a separete dependency: phoenix_template
• Document replacing Phoenix.View with Phoenix.Component
• Deprecate Phoenix.View.render_layout/4 in favor of Phoenix.Component with slots instead

1.1.1 (from changelog)

• Add compile-time dependencies to template engines

1.1.0 (from changelog)

• Do not add compile time dependencies on arguments given to Phoenix.View and Phoenix.Template
• Deprecate render_existing/3 in favor of function_exported?/3 checks

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

Commits

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

• Release v2.0.2
• Fix regression where directories were not being tracked for new files
• Release v2.0.1
• Fix interchanged nouns in docs (#17)
• Update docs
• Update CHANGELOG with version 2.0.0 (#14)
• Bump Elixir to 1.14 and Erlang/OTP to 25 in CI (#15)
• Changes in migration section of docs (#13)
• Release 2.0.0
• Bump phoenix_template
• Update docs to refer to Web module (#12)
• Formatting
• Merge pull request #11 from phoenixframework/cm-formats
• Support changed format_encoder interface
• Update ci.yml
• Update deprecations
• Fix CI
• Use Phoenix template git dep
• Tidy up templates
• Migrate template logic to Phoenix.View
• Move logic from Phoenix.Template to Phoenix.View
• Deprecate render_layout
• Fix syntax error in documentation (#10)
• Fix minor documentation typo (#9)
• Default to Jason
• Release v1.1.2
• Specific to no_return
• Another attempt to tackle no_return
• Add spec to raising function
• Release v1.1.1
• Add compile-time dependencies to template engines
• Update ex_doc
• Clarify render_one/render_many docs
• Removes spec for overridable function (#7)
• Release v1.1.0
• Do not add compile time deps on use options
• Run formatter
• Update ExDoc
• Deprecate render_existing
• Update CI config (#4)
• Minor updates (#3)

↗️ plug (indirect, 1.13.6 → 1.14.0) · Repo · Changelog

Release Notes

1.14.0 (from changelog)

Require Elixir v1.10+.

Enhancements

• Add Plug.Conn.prepend_req_headers/2 and Plug.Conn.merge_req_headers/2
• Support adapter upgrades with Plug.Conn.upgrade_adapter/3
• Add "Copy to Markdown" button in exception page
• Support exclusive use of tlsv1.3

Bug fixes

• Make sure last parameter works within maps

Deprecations

• Deprecate server pushes as they are no longer supported by browsers

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

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ plug_crypto (indirect, 1.2.2 → 1.2.3) · Repo · Changelog

Release Notes

1.2.3 (from changelog)

• Remove warnings on Elixir v1.14

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

Commits

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

• Release v1.2.3
• Fix Elixir 1.14 warnings (#30)
• Update ci.yml
• Use `import Bitwise` instead of `use Bitwise` (#29)
• Update plug link (#26)
• Update crypto.ex
• Rename arg for clarity in Plug.Crypto.encrypt/4 (#25)
• Run formatter

↗️ telemetry (indirect, 1.1.0 → 1.2.1) · Repo · Changelog

Release Notes

1.2.1 (from changelog)

Fixed

• Fixed a local handler warning log when using telemetry_test. (#124)

1.2.0 (from changelog)

Added

• Added telemetry_test module for testing telemetry events. (#118)

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

Commits

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

• Release 1.2.1 (#125)
• replace local function capture in telemetry_test (#124)
• Fix docs generation (#123)
• Release 1.2.0 (#121)
• Fix example in docs (#122)
• Add telemetry_test (#118)
• Update versions on CI (#120)
• Update documentation on telemetry:span/3 (#117)
• Point to new repo (#116)
• Update documentation on telemetry:span/3 (#113)
• Post 1.1.0 updates (#108)

🆕 castore (added, 1.0.0)

🆕 phoenix_template (added, 1.0.1)

---

👉 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, Semaphore and Travis-CI 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

@​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 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)