-
Notifications
You must be signed in to change notification settings - Fork 12
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
[24.11] update nixpkgs 2024 12 10 #1196
Merged
osnyx
merged 8 commits into
fc-24.11-dev
from
PL-os-2411update-20241210-update-nixpkgs-2024-12-10
Dec 11, 2024
Merged
[24.11] update nixpkgs 2024 12 10 #1196
osnyx
merged 8 commits into
fc-24.11-dev
from
PL-os-2411update-20241210-update-nixpkgs-2024-12-10
Dec 11, 2024
Conversation
This file contains 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
The default monitoring check relied on varnish to run on a specific address. Since this address can be changed, the Sensu check needs to be adjusted to correctly infer the host and port that varnish is running on The listen address can only be reliably queried at runtime (without reimplementing Varnishd's command line parsing logic in nix) hence why multiple checks - one per address - are not possible.
…nitoring Fix varnish monitoring 2.0
This action is part of the update-nixpkgs workflow in fc-nixos-release-tools. It requires access to this repository's events, so it needs to be located here. PL-133100
Add update-nixpkgs cleanup action
This is to support the update-nixpkgs workflow without a devenv shell.
…-flake move package-, version update scripts to flake apps
Pull upstream NixOS changes, security fixes and package updates: - cacert: 3.104 -> 3.107 - cacert: 3.104 -> 3.107, (#358220) - chromium: remove ofborg maintainer ping workaround, use CODEOWNERS - chromium: resolve ref to rev for blink version string - curl: backport netrc regression fix - curl: backport netrc regression fix (#356660) - curl: backport other netrc regression fix - github-runner: fix test execution on build - gitlab-runner: Try fixing #356717 - gitlab: 17.3.7 -> 17.5.2 - keycloak: 26.0.5 -> 26.0.6 - mastodon: 4.3.1 -> 4.3.2 - matrix-synapse: 1.119.0 -> 1.120.2 - nginx: fix compatibility with zlib-ng - nodejs_20: 20.18.0 -> 20.18.1 - nss_latest: 3.106 -> 3.107 - openssh: add initrd-network-ssh nixos test to passthru.tests - percona-server: 8.4.0-1 -> 8.4.2-2 - php81: 8.1.30 -> 8.1.31 - php82: 8.2.25 -> 8.2.26 - php83: 8.3.13 -> 8.3.14 - postgresql: drop build-time dependency on GHC - postgresql_16: 16.4 -> 16.5 - ruby_3_2: 3.2.5 -> 3.2.6 - sudo: 1.9.16 -> 1.9.16p2 - systemd: 256.7 -> 256.8 - systemd: revert boot-breaking systemd-boot change - xorg.libX11: Fix spurious Xerror when running synchronized - xorg.libX11: Fix spurious Xerror when running synchronized (#356033) PL-os-2411update-20241210
Da ist das gitlab-assets mit nem OOM ausgestiegen?
|
osnyx
deleted the
PL-os-2411update-20241210-update-nixpkgs-2024-12-10
branch
December 11, 2024 09:31
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.
@flyingcircusio/release-managers
Release process