-
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
Pull in changes from 24.05 (to enable globbing) #1156
Conversation
Using `hard` mode causes existing mounts to persist infinitely, avoiding clients getting stuck with a broken mount that doesn't recover automatically. Using the `automount` unit causes clients to be more persistent when mounts fail (during boot) and causes applications to not accidentally access the mount directory without the mount. Unify the used host names on clients and servers and make sure they match what our /etc/hosts file says so that missing DNS during boot or bootstrap doesn't become a problem. Automatically reboot when the `mnt-nfs-shared.mount` unit changes as it is not reliable that NFS-related changes can be applied online. Remove our separate reload unit that didn't work properly in too many cases. Fixes PL-133062
…nt-v2 nfs: hard mount and fixed remount (v2)
Activate fail2ban sshd ddos jail for non production machines
…-metadata doc: Improve documentation for devhost with channel metadata file
…rvice-reload-breakage [FC-41403] fail during unit reload with syntax errors in the varnish config
Pull upstream NixOS changes, security fixes and package updates: - chromium: 129.0.6668.100 -> 130.0.6723.69 (CVE-2024-10229, CVE-2024-10230, CVE-2024-10231) - discourse: 3.2.5 -> 3.3.2 - docker: 27.3.0 -> 27.3.1 - element-web: 1.11.81 -> 1.11.82 - firefox: 131.0.3 -> 132.0 - github-runner: 2.319.1 -> 2.320.0 - gitlab: 17.2.8 -> 17.3.6 - grafana: 10.4.10 -> 10.4.11 - linux: 5.15.164 -> 5.15.169 - nss_latest: 3.105 -> 3.106 - unifi8: 8.4.62 -> 8.5.6
PL-133119
…-2405-update-nixpkgs-2024-11-04 Update nixpkgs (2024-11-04)
…obbing-2405 [24.05][PL-133119] release: use globs for constituents
This reverts commit 0f1f870. Let's first sync the new release logic before trying a smaller channel again.
Several changes in 24.11 made the diff too complicated to adopt that largescale revamp of release logic. Just follow what 24.05 does for now and redo changes if necessary.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's two things we now need to figure out about how we merge 24.05 into 24.11 (and this is similar to how we merge 24.01 into the hardware branch)
- What should happen with the changelogs? (I think we should just remove them.)
- The version updates need to be ignored.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The changelogs should be deleted, I think.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just manually and then as an extra commit?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
don't care.
Apparently the version.nix didn't actually change in this PR, but I can't see where it was reverted ... ?!? |
That package is not yet available in the nixpkgs pinned right now. Revert this after upgrading the nixpkgs revision.
version is missing here as well
I did a |
Those were all solved in the discussions above. |
@flyingcircusio/release-managers
Release process
./changelog.sh
PR release workflow (internal)
Design notes
on
oroff
. Example: rate limiting.Security implications