Curtis Vogt

Single nightly failure is: ``` [3956] signal (11.1): Segmentation fault: 11 in expression starting at /Users/runner/work/TimeZones.jl/TimeZones.jl/test/thread-safety.jl:1 ``` Time to remove these tests

@NHDaly let me know if you have any feedback

> @nickrobinson251 told me that we can also construct new timezones if the user constructs a custom timezone or something? is that something we need to consider? It is possible...

I've self-reviewed this code again and it seems like a better path forward for handling thread safety. I'm re-running the tests again here to verify things are working with the...

In PR https://github.com/JuliaTime/TimeZones.jl/pull/441 the `deps/build.jl` was removed so this is no longer an issue. Included in TimeZones release 1.12

In PR https://github.com/JuliaTime/TimeZones.jl/pull/441 all of the lazy tzdata artifacts were removed in favor of using precompiled time zones provided by [TZJData.jl](https://github.com/JuliaTime/TZJData.jl) non-lazy artifacts. The end result is that when using...

In PR https://github.com/JuliaTime/TimeZones.jl/pull/441 all of the lazy tzdata artifacts were removed in favor of using precompiled time zones provided by [TZJData.jl](https://github.com/JuliaTime/TZJData.jl) non-lazy artifacts. The end result is that when using...

In PR https://github.com/JuliaTime/TimeZones.jl/pull/441 the `deps/build.jl` was removed so this is no longer an issue. Included in TimeZones release 1.12

In PR https://github.com/JuliaTime/TimeZones.jl/pull/441 the `deps/build.jl` was removed so this is no longer an issue. Included in TimeZones release 1.12

In PR https://github.com/JuliaTime/TimeZones.jl/pull/441 the `deps/build.jl` was removed so this is no longer an issue. Included in TimeZones release 1.12