Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

openscad-unstable: 2024-01-22 -> 2024-02-18 #289650

Merged
merged 1 commit into from
Feb 18, 2024

Conversation

pca006132
Copy link
Contributor

Description of changes

update openscad-unstable.

Things done

  • Built on platform(s)
    • x86_64-linux
    • aarch64-linux
    • x86_64-darwin
    • aarch64-darwin
  • For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
    • sandbox = relaxed
    • sandbox = true
  • Tested, as applicable:
  • Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
  • Tested basic functionality of all binary files (usually in ./result/bin/)
  • 24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)
    • (Package updates) Added a release notes entry if the change is major or breaking
    • (Module updates) Added a release notes entry if the change is significant
    • (Module addition) Added a release notes entry if adding a new NixOS module
  • Fits CONTRIBUTING.md.

Add a 👍 reaction to pull requests you find important.

@pca006132
Copy link
Contributor Author

it seems that the CI failure is not caused by the commit.

@7c6f434c
Copy link
Member

Apparently the check is fixed by #289655 and I am asking in #289649 about some details of the incident.

@7c6f434c 7c6f434c merged commit 045b51a into NixOS:master Feb 18, 2024
27 of 28 checks passed
@pca006132 pca006132 deleted the bump-openscad-unstable branch February 18, 2024 12:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants