Sourced from swoosh's\nreleases.
\n\n\nv1.16.10 🚀
\n🐛 Bug Fixes
\n\n
\n- mua: no mx when relay
\n@ruslandoga
(#934)📝 Documentation
\n\n
\n- mua: update docs
\n@ruslandoga
(#935)⛓️ Dependency
\n\n
\n- Bump req from 0.5.2 to 0.5.4
\n@dependabot
(#937)- Bump req from 0.5.1 to 0.5.2
\n@dependabot
(#932)- Bump ex_doc from 0.34.1 to 0.34.2
\n@dependabot
(#933)- Bump mime from 2.0.5 to 2.0.6
\n@dependabot
(#930)- Bump jason from 1.4.1 to 1.4.3
\n@dependabot
(#929)- Bump req from 0.5.0 to 0.5.1
\n@dependabot
(#928)- Bump ex_doc from 0.34.0 to 0.34.1
\n@dependabot
(#926)- Bump plug from 1.16.0 to 1.16.1
\n@dependabot
(#927)- Bump bandit from 1.5.4 to 1.5.5
\n@dependabot
(#925)- Bump bandit from 1.5.2 to 1.5.4
\n@dependabot
(#921)- Bump mua from 0.2.1 to 0.2.2
\n@dependabot
(#920)- Bump ex_aws from 2.5.3 to 2.5.4
\n@dependabot
(#917)- Bump ex_doc from 0.33.0 to 0.34.0
\n@dependabot
(#915)- Bump mua from 0.2.0 to 0.2.1
\n@dependabot
(#916)Full Changelog: https://github.com/swoosh/swoosh/compare/v1.16.9...v1.16.10
\n
Sourced from swoosh's\nchangelog.
\n\n\n1.16.10
\n🐛 Bug Fixes
\n\n
\n- mua: no mx when relay
\n@ruslandoga
(#934)📝 Documentation
\n\n
\n- mua: update docs
\n@ruslandoga
(#935)
92cbe3e
\nv1.16.10ef22805
\nmua: update docs (#935)98450a8
\nBump req from 0.5.2 to 0.5.4 (#937)cb3bea1
\nmua: skip mx lookup when relay is used (#934)b1c2ce3
\nBump req from 0.5.1 to 0.5.2 (#932)8a75efe
\nBump ex_doc from 0.34.1 to 0.34.2 (#933)7bda2b8
\nBump mime from 2.0.5 to 2.0.6 (#930)7039ade
\nBump jason from 1.4.1 to 1.4.3 (#929)2b00243
\nBump req from 0.5.0 to 0.5.1 (#928)dbb96a2
\nBump ex_doc from 0.34.0 to 0.34.1 (#926)Sourced from req's\nchangelog.
\n\n\nv0.5.4 (2024-07-18)
\n\n
\n- [
\nrun_finch
], [Req.parse_message/2
]:\nGracefully handle process messages not meant\nfor the asynchronous response. In that case,\nReq.parse_message/2
returns:unknown
.v0.5.3 (2024-07-18)
\n\n
\n- \n
\n[
\nReq.Test
]: Fix using shared mode- \n
\n[
\nencode_body
]: Add:form_multipart
\noption- \n
\n[
\nput_aws_sigv4
]: Try detecting the service- \n
\n[
\nrun_finch
]: Fix setting:finch
option
8733431
\nRelease v0.5.49928489
\nReq.parse_message/2
, run_finch
: Handle\nunrelated messages4b43e6d
\nUpdate Req.parse_message/2 signatured0366ef
\nUpdate docs0b7c23a
\nShow example if into: File.stream (#392)8431d07
\nRelease v0.5.39bb1470
\nput_aws_sigv4
: Try detecting the servicef6fb034
\nRemove unused code60253db
\nencode_body
: Add :form_multipart
71bb9ae
\nUse :finch
value to override finch instance (#391)Sourced from earmark's\nchangelog.
\n\n\nEarmark 1.4.47\n2024-07-12
\nFirst a small explanation
\nThis has been backported from RobertDober/earmark_parser#156.
\nIt seems however important to clarify some things concerning the\nsplit between
\nEarmark
and\nEarmarkParser
which\nwere confusing.They are only historically related and there is no\nformal dependency anymore. As I am still happy to help out with Earmark\nbut also\nvery relieved not to be obliged I might as well continue to do backports\nbugfixes (but probably not new features). However\nall decision about what will happen with
\nEarmark
and how\nthe internal parser evolves will not be taken by me.This release is done beacause our new maintainer asked me to\nmake it so (couldn't resist this one)\nand because he accepted the PR for the backport.
\nUnfortunately the naming of the projects and the internal module\n
\nEarmark.Parser
have made people unconfortable with bug\nreports.Please note two things here.
\nFirstly, and most importantly, nowbody will be harsh or impolite of\nyou file an issue in the wrong project, we'll figure it\nout.
\nSecondly I have opened an Issue\nabout better documenting this in both projects.\nAll comments and ideas on this topic are very much welcome.
\nHopefully this will become much clearer soon.
\nAnd now for something completely different
\n\n
\n- \n
\n[Fix for #501](pragdave/earmark#501)
\n- \n
\n[Fix for #495](pragdave/earmark#498)
\n- \n
\n[Fix for #361](pragdave/earmark#486)\nKudos to bradhanks
\nMuch work was put into
\nEarmark
by Brad in the last\nmonths working on getting rid of warnings, typespecs\nandmix format
compliance, the details of which are not\nreally interesting in RNs, but shall be duely appreciated.\n
\n- Fixing\nbroken link in doc\nKudos to Rodolfo\nCarvalho
\n
Sourced from mneme's\nreleases.
\n\n\nMneme v0.8.2 is now available.
\n\n
\n- Changelog\n
\n- Docs
\nThis release includes a couple of bug fixes and one small CLI\nfeature.
\n\n
\n- \n
\nThere were some regressions in the last few releases relating to map\npatterns that could cause many duplicate patterns to be suggested and,\nin some cases, incorrect patterns that wouldn't match your actual value.\nI believe these are now fixed, but please let me know if you run into\nany weird suggestions!
\n- \n
\nTwo new key bindings have been added to the CLI:
\nJ
and\nK
to jump to the first or last pattern. This can be helpful\nespecially when you have a large, nested data structure, as these can\ncause Mneme to generate quite a few patterns at various levels of\ncomplexity.
Sourced from mneme's\nchangelog.
\n\n\nv0.8.2 (2024-07-11)
\nAdded
\n\n
\n- Added
\nJ
andK
to jump to the first and\nlast pattern when multiple patterns are offered in a prompt.\n(J
andK
were previously equivalent to\nj
andk
, respectively.)Fixed
\n\n
\n- Don't suggest duplicate patterns when updating lists (or other\ncontainers of) maps.
\n- Don't generate incorrect map patterns when updating an existing\npattern that is a partial match of a new value. For instance, when\nupdating the pattern
\n%{x: 1, y: 2, z: 3}
for the new value\n%{x: 1, y: 2}
, the incorrect pattern%{x: 1, y: 2, z:\nnil}
would be suggested.
dd9cbd4
\nrelease: v0.8.2414cd8e
\nfix: correct spec for Assertion.select/2
81ffa01
\ndocs: update demo.tapea0a918b
\nfeat(cli): add J/K for first/last when multiple patterns are\npresent70f8f16
\nrefactor: replace Assertion.[prev,next]/1
with\nAssertion.select/2
065234e
\ndocs: update changelog4b5d4e8
\nfix: don't add nils to map patterns when partial patterns already\nexisted24e41b8
\nfix: don't generate duplicate map keysetsa5ba09b
\ndocs: update readme0234263
\ndocs: update readmeSourced from absinthe's\nchangelog.
\n\n\n1.7.7
\n\n
\n- POTENTIALLY BREAKING Bug Fix: Validate\nvariable usage in nested input arguments.This could break incoming\ndocuments previously considered valid. Skip the\nAbsinthe.Phase.Document.Arguments.VariableTypesMatch phase to avoid this\ncheck. See Absinthe.Pipeline on adjusting the document pipeline.
\n- #1321\nresolves telemetry issues
\n- Various minor dependency versioning tweaks
\n- Handle Elixir 1.17 warnings
\n
Sourced from oban's\nchangelog.
\n\n\nv2.17.12 — 2024-06-28
\nBug Fixes
\n\n
\n- \n
\n[Basic] Return
\n{:ok, job}
tuple on unique advisory lock\nconflict.The advisory lock clause only returned the job, not a success\ntuple.
\n
bd2892d
\nRelease v2.17.121996be9
\nReturn {:ok, job} tuple on adlock conflictSourced from jason's\nchangelog.
\n\n\nChangelog
\n1.5.0-alpha.2 (07.07.2023)
\n\n
\n- Add limit to decoded integer sizes of 1024 digits. This can be\nchanged\nwith the
\ndecoding_integer_digit_limit
app env config.
5c309b1
\nRequire stream_data only from Elixir 1.12e9702d4
\nBump 1.4.263d82ec
\nFix deprecation warnings in tests0d8a04f
\nUpdate dependencies5f7201b
\nFormat charlists28ff2c2
\nFix codegen to expand ranges44fc70a
\nFix non-deterministic test on OTP27 (#187)9c3bc4b
\nRemoves unused Dialyzer ignored warnings (#182)88a0bb8
\nRemove uneeded backtick (#173)Sourced from phoenix_ecto's\nchangelog.
\n\n\nv4.6.2
\n\n
\n- Bug fix\n
\n\n
\n- Attach directories to Pending Migrations exception
\n