Repository navigation
update nullkomma and remove resolved workarounds - #63
Merged
Merged
Conversation
Co-authored-by: Copilot App <[email protected]>
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.
Update nullkomma from 0.1.536 to 0.1.552 (b6971c3), the latest released main revision at the start of this upgrade.
Remove the Linux Chromium font wrapper, the elf-specific startup setup hook, and the explicit allowOffNixpkgs opt-in. Upstream now provides each behavior through dataheld/nullkomma#260, dataheld/nullkomma#263 and dataheld/nullkomma#262. flake.nix shrinks from 94 to 69 lines; only flake.nix and flake.lock change. Applying the upstream upgrade workflow produced no additional tracked-file changes.
Closes #54.
Reviewed issues, PRs and discussion updated in both repositories during the preceding 12 hours. Keep #55 pending dataheld/nullkomma#258, and #52/#53 pending dataheld/nullkomma#264 (still open). Preserve the serial worker limit tracked by #56, browser preflight, timeouts, snapshots, check arguments and current CI/deployment gating. Neither #57 nor #62 is fixed by these upstream releases.
Validation:
Hosted CI and live deployment were not run. The signed commit uses [skip ci] to avoid duplicate expensive builds. The existing macOS sandbox browser exclusion remains; the installed suite was executed separately as the login user.