chore(deps): update mix dependencies #702
No reviewers
Labels
No labels
bug
duplicate
enhancement
help wanted
high priority
invalid
L
low priority
M
medium priority
needs refinement
optional
question
S
security
technical improvement
UX Improvement
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
local-it/mitgliederverwaltung!702
Loading…
Reference in a new issue
No description provided.
Delete branch "renovate/mix-dependencies"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
1.4.0→1.5.07.5.1→7.6.01.8.16→1.8.17Release Notes
ash-project/ash_admin (ash_admin)
v1.5.0Compare Source
Features:
show what a create or update action returns besides the record by Fredrik Teschke
choose the fields shown for each relationship on the show page by Etienne Lacoursiere
hide the table search with the filters by Etienne Lacoursiere
searchable table columns via table_searchable_columns by Etienne Lacoursiere
add host_app_path option to link back to the host app by Etienne Lacoursiere
Bug Fixes:
only let the actor plug grant tenant controls by Paul Schoenfelder
only let the actor plug grant actor and authorization controls by Paul Schoenfelder
send no metadata message when an action returns none by Fredrik Teschke
register Cinder's colocated hooks in the admin bundle by azmaveth
spark formatter entry and Tailwind scan of the theme by Etienne Lacoursiere
give phx-change forms an id by Fredrik Teschke
ExHammer/hammer (hammer)
v7.6.0Compare Source
LeakyBucket(ETS and Atomic backends) andTokenBucket(Atomic backend) returning a flat{:deny, 1000}; they now return the real time in milliseconds until the hit would be allowed, as the ETSTokenBuckethas since 7.5.0. The leaky buckets count in whole seconds, so their value runs to the second boundary at which the bucket has leaked enough. Behaviour change: the value is no longer always 1000. It can be much larger (e.g. up to 144000 for a bucket 144 over capacity atleak_rate: 1) or smaller (down to 1 when the next second is about to start). Code that converts it to aretry-afterheader should round up and floor at 1 second. A rate of 0 still answers{:deny, 1000}. (#221)LeakyBucket(ETS and Atomic backends) allowing a hit whenever the level was below capacity, whatever its cost, so a bucket could be filled tocapacity - 1 + cost. A hit is now allowed only if the level after it stays within capacity, as the moduledoc always said and as the Mnesia backend does. Behaviour change: hits withcost > 1that used to overfill the bucket are now denied; hits withcost: 1behave as before. Acostlarger thancapacityis never allowed. (#222)use Hammer, backend: :atomic, algorithm: :sliding_windownow raises anArgumentErrorsaying that sliding window is not available for the Atomic backend and pointing to the ETS backend. It already failed at compile time, but with an unhelpful "could not load module" error. The error for an unknown Atomic algorithm now says "algorithm" rather than "backend" and no longer lists:sliding_window. (#222)FixWindowPerKeyhanging on a key forever. Resetting an expired window took a lock in the key's atomic; a process killed while holding it (for example a request process shut down mid-call) left the lock behind, and every laterhitorincon that key spun on it without returning. An expired window is now replaced by a fresh atomic, so there is no lock. A lock left behind by 7.5.1 or earlier is treated as an expired window. (#222)TokenBucketETS backend letting far more thanrefill_ratethrough. The refill clock advanced by a whole number of milliseconds, rounded down, so part of each elapsed stretch was credited again on the next hit. Atrefill_rate: 600a caller hitting in a tight loop got about 1000 hits per second, and above 1000 tokens per second, where a token is worth less than a millisecond, the clock did not move at all and the limiter was effectively off (over a million hits in half a second atrefill_rate: 1500,capacity: 10). Present since 7.5.0. The clock now advances by the exact time credited. (#222)TokenBucketrefilling in whole seconds, which capped sustained throughput atcapacitytokens per second whenrefill_rate > capacityand delivered tokens in a lump at each second boundary. It now refills by the millisecond and keeps fractions of a token, so its{:deny, ms}value is exact to the millisecond (e.g. 19 atrefill_rate: 55). Buckets held in memory across a hot code upgrade start over full. (#222)LeakyBucket(ETS and Atomic backends) raising the level, andTokenBucketETS backend taking tokens away, when the stored clock was ahead of the caller's. That happens when a concurrent hit reads the time later or the wall clock steps back; the negative elapsed time was applied as a negative leak or refill. It now counts as no time elapsed, and aTokenBucket(both backends) that denies in that state includes the time until the stored clock is reached in its{:deny, ms}value, since nothing refills before then. (#222)phoenixframework/phoenix (phoenix)
v1.8.17Compare Source
Security fixes
Bug fixes
Enhancements
reconnectWhenHidden(#6883)Configuration
📅 Schedule: (UTC)
* * * * *)🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.