Repository navigation
fix: docs: 4.6.0 post states the dev-tooling targets that were not met - #637
Merged
Merged
Conversation
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.
Closes #636
Follow-up of #634, whose squash merged without the edit.
Change
The tests section of
site/src/content/changelog/4.6.0.mdxnow states plainly the three dev-tooling targets that were not met, with the measured numbers: shared-change land 255 s vs 120 s target; our tooling peaks at 8 cores vs the 4-core cap (not enforced yet, #632); warmbun run test11 to 13 s vs 10 s.Docs-only copy change (no behaviour to regression-test); the land gate runs the changelog route checks.
Checklist
bun run validatepasses (pre-push)