# Julia 1.7.3 testing period

**URL:** <https://discourse.julialang.org/t/julia-1-7-3-testing-period/79811>\
**Category:** Announcements\
**Created:** [April 22, 2022, 7:40am UTC](https://discourse.julialang.org/t/julia-1-7-3-testing-period/79811 "2022-04-22T07:40:07Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![kristoffer.carlsson](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/kristoffer.carlsson/32/22_2.png) [@kristoffer.carlsson](https://discourse.julialang.org/u/kristoffer.carlsson)\
**Post date:** [April 22, 2022, 7:40am UTC](https://discourse.julialang.org/t/julia-1-7-3-testing-period/79811/1 "2022-04-22T07:40:07Z")

</div>

The `release-1.7` branch on the Julia repository now contains the set of commits we’re planning to tag as v1.7.3, the third patch release in the 1.7 series. The list of commits included since v1.7.2 is available [here](https://github.com/JuliaLang/julia/compare/v1.7.2...release-1.7). As a patch release, it should be strictly non-breaking for existing code and should introduce no new features at all, just bug fixes and performance enhancements.

We encourage users, especially package authors, to test their code using a source build of the `release-1.7` branch to ensure there are no changes in behavior. (Binaries are not available for prereleases of patch versions at this time.) A package evaluation run showed no regressions from v1.7.2, so we should be good, but extra testing and assurance are always worthwhile. If you run into any issues, please report them on Julia’s [GitHub issue tracker](https://github.com/JuliaLang/julia/issues). We ask that you post them there rather than in this thread for visibility to the developers.

Assuming all is well, we’ll move forward with releasing v1.7.3 in a week or so.

---

<div class="post-metadata">

**Author:** ![nsslh](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/nsslh/32/27447_2.png) [@nsslh](https://discourse.julialang.org/u/nsslh)\
**Post date:** [May 5, 2022, 12:26pm UTC](https://discourse.julialang.org/t/julia-1-7-3-testing-period/79811/2 "2022-05-05T12:26:23Z")

</div>

No security issues addressed in this release, as far as I can tell. Are you able to confirm?

---

<div class="post-metadata">

**Author:** ![kristoffer.carlsson](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/kristoffer.carlsson/32/22_2.png) [@kristoffer.carlsson](https://discourse.julialang.org/u/kristoffer.carlsson)\
**Post date:** [May 5, 2022, 1:10pm UTC](https://discourse.julialang.org/t/julia-1-7-3-testing-period/79811/3 "2022-05-05T13:10:46Z")

</div>

[https://github.com/JuliaLang/julia/pull/44810](https://github.com/JuliaLang/julia/pull/44810) could be considered a security issue but I cannot do an exact characterization of every change. You can see the changes here [https://github.com/JuliaLang/julia/compare/v1.7.2...release-1.7](https://github.com/JuliaLang/julia/compare/v1.7.2...release-1.7).

---

<div class="post-metadata">

**Author:** ![kristoffer.carlsson](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/kristoffer.carlsson/32/22_2.png) [@kristoffer.carlsson](https://discourse.julialang.org/u/kristoffer.carlsson)\
**Post date:** [May 9, 2022, 11:31am UTC](https://discourse.julialang.org/t/julia-1-7-3-testing-period/79811/4 "2022-05-09T11:31:07Z")

</div>

This release got a bit delayed due to some CI problems and one of the people that usually creates binaries is on vacation. But it is being worked on.