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

certinfo-go: init at 0.1.36 #349962

Merged
merged 1 commit into from
Oct 23, 2024
Merged

Conversation

paepckehh
Copy link
Contributor

@paepckehh paepckehh commented Oct 20, 2024

Tool to analyze and troubleshoot certificates (x.509, ssh-certs, keys, ...)

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.11 Release Notes (or backporting 23.11 and 24.05 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.

Related to #81418

@paepckehh paepckehh force-pushed the certinfo-v0.1.36 branch 3 times, most recently from ac06e6e to c3e8914 Compare October 20, 2024 08:18
@paepckehh paepckehh changed the title certinfo: init at 0.1.36 certinfo-go: init at 0.1.36 Oct 20, 2024
@tomfitzhenry tomfitzhenry merged commit 017dcbc into NixOS:master Oct 23, 2024
38 checks passed
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.

4 participants