chore: merge dev into main - #98
Merged
Merged
Conversation
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
marked this pull request as ready for review
September 15, 2026 15:33
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automated rollup PR for changes accumulated on
dev. Mark ready when you want it to land — and use a merge commit, not squash, so individualfeat:/fix:commits stay visible to release-please.