# Exclude parsing of \`public\` statements in Julia v1.10 CI

**URL:** <https://discourse.julialang.org/t/exclude-parsing-of-public-statements-in-julia-v1-10-ci/126998>\
**Category:** Tooling\
**Tags:** codecov, ci\
**Created:** [March 15, 2025, 11:59pm UTC](https://discourse.julialang.org/t/exclude-parsing-of-public-statements-in-julia-v1-10-ci/126998 "2025-03-15T23:59:16Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![gdalle](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/gdalle/32/27854_2.png) [@gdalle](https://discourse.julialang.org/u/gdalle)\
**Post date:** [March 16, 2025, 7:19am UTC](https://discourse.julialang.org/t/exclude-parsing-of-public-statements-in-julia-v1-10-ci/126998/5 "2025-03-16T07:19:15Z")

</div>

See also

> [@Is Compat.jl worth it for the \`public\` keyword?](https://discourse.julialang.org/t/is-compat-jl-worth-it-for-the-public-keyword/119041):
>
> With the introduction of public by @Lilith, many packages will want to mark their unexported public symbols that way. Since public is only available in Julia 1.11, the current recommended way to do this in 1.10 is with the Compat.jl package. Before we add it everywhere, I’m wondering if there are any negative side effects to it? @stevengj seems to think it’s fine but I’d love to get other opinions. In particular, it depends on 4 stdlibs: Dates, LinearAlgebra, TOML and UUIDs.

---

_[View the full topic](https://discourse.julialang.org/t/exclude-parsing-of-public-statements-in-julia-v1-10-ci/126998)._