Skip to content

Update nixpkgs #1065

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Update nixpkgs #1065

wants to merge 2 commits into from

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Oct 16, 2024 •
edited
Loading

Automated changes by the update-flake-lock GitHub Action.

Flake lock file updates:

• Updated input 'nixpkgs':
    'github:NixOS/nixpkgs/b69de56fac8c2b6f8fd27f2eca01dcda8e0a4221?narHash=sha256-f0SBJz1eZ2yOuKUr5CA9BHULGXVSn6miBuUWdTyhUhU%3D' (2024-10-10)
  → 'github:NixOS/nixpkgs/ed30f8aba41605e3ab46421e3dcb4510ec560ff8?narHash=sha256-5oLdRa3vWSRbuqPIFFmQBGGUqaYZBxX%2BGGtN9f/n4lU%3D' (2025-05-04)

Running GitHub Actions on this PR

GitHub Actions will not run workflows on pull requests which are opened by a GitHub Action.

To run GitHub Actions workflows on this PR, run:

git branch -D update_flake_lock_action
git fetch origin
git checkout update_flake_lock_action
git commit --amend --no-edit
git push origin update_flake_lock_action --force

@github-actions github-actions bot added the dependencies Pull requests that update a dependency file label Oct 16, 2024
@github-actions github-actions bot force-pushed the update_flake_lock_action branch 4 times, most recently from 69d619e to 30982a0 Compare October 23, 2024 18:35
@github-actions github-actions bot force-pushed the update_flake_lock_action branch 6 times, most recently from d9fd85d to 15e3b35 Compare October 30, 2024 18:36
@github-actions github-actions bot force-pushed the update_flake_lock_action branch 5 times, most recently from 2844b1b to 83ce992 Compare November 7, 2024 18:34
@github-actions github-actions bot force-pushed the update_flake_lock_action branch 3 times, most recently from 85d4ca1 to 66bcfff Compare November 14, 2024 18:36
@github-actions github-actions bot force-pushed the update_flake_lock_action branch 5 times, most recently from 4eb58fc to 12443c6 Compare November 22, 2024 18:36
@github-actions github-actions bot force-pushed the update_flake_lock_action branch 3 times, most recently from 5794817 to 9f0da3f Compare November 30, 2024 18:35
@github-actions github-actions bot force-pushed the update_flake_lock_action branch 3 times, most recently from 407d067 to 21537fe Compare December 3, 2024 18:36
@github-actions github-actions bot force-pushed the update_flake_lock_action branch from c56bf0c to a1177ea Compare April 9, 2025 18:40
@mergify Mergify
Copy link
Contributor

mergify bot commented Apr 9, 2025

This pull request has been removed from the queue for the following reason: checks failed.

The merge conditions cannot be satisfied due to failing checks:

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

@github-actions github-actions bot force-pushed the update_flake_lock_action branch from a1177ea to 4d05c13 Compare April 10, 2025 18:36
@mergify Mergify
Copy link
Contributor

mergify bot commented Apr 10, 2025

This pull request has been removed from the queue for the following reason: checks failed.

The merge conditions cannot be satisfied due to failing checks:

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

@github-actions github-actions bot force-pushed the update_flake_lock_action branch from 4d05c13 to b8bb949 Compare April 11, 2025 18:38
@mergify Mergify
Copy link
Contributor

mergify bot commented Apr 11, 2025

This pull request has been removed from the queue for the following reason: checks failed.

The merge conditions cannot be satisfied due to failing checks:

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

@github-actions github-actions bot force-pushed the update_flake_lock_action branch from b8bb949 to dc545b2 Compare April 12, 2025 18:35
@mergify Mergify
Copy link
Contributor

mergify bot commented Apr 12, 2025

This pull request has been removed from the queue for the following reason: checks failed.

The merge conditions cannot be satisfied due to failing checks:

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

@github-actions github-actions bot force-pushed the update_flake_lock_action branch from dc545b2 to 0c6d121 Compare April 13, 2025 18:35
@mergify Mergify
Copy link
Contributor

mergify bot commented Apr 13, 2025

This pull request has been removed from the queue for the following reason: checks failed.

The merge conditions cannot be satisfied due to failing checks:

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

@github-actions github-actions bot force-pushed the update_flake_lock_action branch from 0c6d121 to 27c5bb8 Compare April 20, 2025 18:35
@mergify Mergify
Copy link
Contributor

mergify bot commented Apr 20, 2025

This pull request has been removed from the queue for the following reason: checks failed.

The merge conditions cannot be satisfied due to failing checks:

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

@github-actions github-actions bot force-pushed the update_flake_lock_action branch from 27c5bb8 to 6004420 Compare April 24, 2025 18:39
@mergify Mergify
Copy link
Contributor

mergify bot commented Apr 24, 2025

This pull request has been removed from the queue for the following reason: checks failed.

The merge conditions cannot be satisfied due to failing checks:

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

@github-actions github-actions bot force-pushed the update_flake_lock_action branch from 6004420 to b70cf41 Compare April 29, 2025 18:38
@mergify Mergify
Copy link
Contributor

mergify bot commented Apr 29, 2025

This pull request has been removed from the queue for the following reason: checks failed.

The merge conditions cannot be satisfied due to failing checks:

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

@github-actions github-actions bot force-pushed the update_flake_lock_action branch from b70cf41 to 59e590d Compare April 30, 2025 18:40
@mergify Mergify
Copy link
Contributor

mergify bot commented Apr 30, 2025

This pull request has been removed from the queue for the following reason: checks failed.

The merge conditions cannot be satisfied due to failing checks:

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

@github-actions github-actions bot force-pushed the update_flake_lock_action branch from 59e590d to b5c0a53 Compare May 1, 2025 18:40
@mergify Mergify
Copy link
Contributor

mergify bot commented May 1, 2025

This pull request has been removed from the queue for the following reason: checks failed.

The merge conditions cannot be satisfied due to failing checks:

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

@github-actions github-actions bot force-pushed the update_flake_lock_action branch from b5c0a53 to 4fc54d7 Compare May 2, 2025 18:39
@mergify Mergify
Copy link
Contributor

mergify bot commented May 2, 2025

This pull request has been removed from the queue for the following reason: checks failed.

The merge conditions cannot be satisfied due to failing checks:

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

@github-actions github-actions bot force-pushed the update_flake_lock_action branch from 4fc54d7 to e984aca Compare May 3, 2025 18:36
@mergify Mergify
Copy link
Contributor

mergify bot commented May 3, 2025

This pull request has been removed from the queue for the following reason: checks failed.

The merge conditions cannot be satisfied due to failing checks:

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

@github-actions github-actions bot force-pushed the update_flake_lock_action branch from e984aca to fc5c03e Compare May 4, 2025 18:36
@mergify Mergify
Copy link
Contributor

mergify bot commented May 4, 2025

This pull request has been removed from the queue for the following reason: checks failed.

The merge conditions cannot be satisfied due to failing checks:

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

github-actions bot added 2 commits May 5, 2025 18:37
@github-actions
flake.lock: Update
89034d2 
Flake lock file updates:

• Updated input 'nixpkgs':
    'github:NixOS/nixpkgs/41dea55321e5a999b17033296ac05fe8a8b5a257?narHash=sha256-WvLXzNNnnw%2BqpFOmgaM3JUlNEH%2BT4s22b5i2oyyCpXE%3D' (2024-10-25)
  → 'github:NixOS/nixpkgs/ed30f8aba41605e3ab46421e3dcb4510ec560ff8?narHash=sha256-5oLdRa3vWSRbuqPIFFmQBGGUqaYZBxX%2BGGtN9f/n4lU%3D' (2025-05-04)
@github-actions
flake.lock: Update
add914e 
Flake lock file updates:

• Updated input 'nixpkgs':
    'github:NixOS/nixpkgs/b69de56fac8c2b6f8fd27f2eca01dcda8e0a4221?narHash=sha256-f0SBJz1eZ2yOuKUr5CA9BHULGXVSn6miBuUWdTyhUhU%3D' (2024-10-10)
  → 'github:NixOS/nixpkgs/ed30f8aba41605e3ab46421e3dcb4510ec560ff8?narHash=sha256-5oLdRa3vWSRbuqPIFFmQBGGUqaYZBxX%2BGGtN9f/n4lU%3D' (2025-05-04)
@github-actions github-actions bot force-pushed the update_flake_lock_action branch from fc5c03e to add914e Compare May 5, 2025 18:37
@mergify Mergify
Copy link
Contributor

mergify bot commented May 5, 2025

This pull request has been removed from the queue for the following reason: checks failed.

The merge conditions cannot be satisfied due to failing checks:

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants