Skip to content

chore: merge dev into main - #98

Merged
TitusKirch merged 3 commits into
mainfrom
dev
Sep 15, 2026
Merged

TitusKirch merged 3 commits into
mainfrom
dev

Conversation

@github-actions

Copy link
Copy Markdown

Automated rollup PR for changes accumulated on dev. Mark ready when you want it to land — and use a merge commit, not squash, so individual feat:/fix: commits stay visible to release-please.

0.6.0 is the first release tagged with its component, so release-please
compared it against duxt@v0.5.0, a tag that never existed: 0.5.0 was cut as
v0.5.0. Later releases compare two component tags and are unaffected.
Run 34791359819 retained concurrency 8 while 4 and 12 were each about 25%
faster, for two reasons that were not about concurrency. Every candidate was
refused for fewer OG images than the best build, but the shortfall sat in
repetition 1 at every setting, the baseline included; completeness is now
judged against the fullest build of the same repetition. And each setting ran
on its own matrix leg, so a slower machine read as a slower setting; every
setting is now built on one runner, interleaved, with the order rotating.
@TitusKirch
TitusKirch marked this pull request as ready for review September 15, 2026 15:33
@TitusKirch
TitusKirch merged commit f622ddc into main Sep 15, 2026
16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant