v1.10.1

ProgressMeter v1.10.1

Diff since v1.10.0

• the force keyword in next! and update! can force the updating of the progressbar
• the safe_lock keyword controls the lock for thread-safety

Merged pull requests:

• Bump julia-actions/setup-julia from 1 to 2 (#308) (@dependabot[bot])
• fix breaking setproperty! introduced in #304 (#309) (@MarcMush)
• Bump julia-actions/cache from 1 to 2 (#314) (@dependabot[bot])
• Allow forcing the progress bar update (#315) (@alyst)
• lock by default - add safe_lock option for control (#322) (@lmiq)
• ProgressMeter 1.10.1 (#324) (@MarcMush)

Closed issues:

• asyncmap (#96)
• Broken for threads (#143)
• Performance test fails in 1.7 (#219)
• It shows repeated output in VScode (#231)
• is_threading is racy (#232)
• Mangled test output on julia 1.11 (#303)
• A code in README.md doesn't work (#310)
• Some tests did not pass (#313)
• InexactError check_top_bit (#316)
• Julia 1.11: BoundsError: attempt to access MemoryRef{Int64} at index [1] (#317)