Skip to content

Don't mark subpackage releases as latest when the root is a package - #613

Open
maleadt wants to merge 1 commit into
JuliaRegistries:masterfrom
maleadt:tb/subdir-latest
Open

maleadt wants to merge 1 commit into
JuliaRegistries:masterfrom
maleadt:tb/subdir-latest

Conversation

@maleadt

@maleadt maleadt commented Nov 17, 2026

Copy link
Copy Markdown

GitHub marks the most recently published release as the repository's latest. A subpackage's TagBot step usually runs right after the top-level package's, so its release takes over the "Latest" badge. For example, KernelAbstractions.jl's KernelInterface-v0.4.6 was published 4 seconds after v0.10.6.

With this change, subpackage releases are not marked latest when the repository root holds a package at the release commit, meaning a JuliaProject.toml or Project.toml with a name and UUID. A root project without those is an environment, not a package. Repositories whose packages all live in subdirectories behave as before.

GitHub marks the most recently published release as the repository's
latest. A subpackage's TagBot step usually runs right after the
top-level package's, so the subpackage release took over the "Latest"
badge.

When the repository root holds a package (a project file with a name and
UUID) at the release commit, leave subpackage releases unmarked.
Repositories whose only packages live in subdirectories are unaffected.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant