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

k3s_1_29: 1.29.12+k3s1 -> 1.29.13+k3s1 #379386

Merged
merged 1 commit into from
Feb 22, 2025
Merged

Conversation

rorosen
Copy link
Contributor

@rorosen rorosen commented Feb 4, 2025

https://github.com/k3s-io/k3s/releases/tag/v1.29.13%2Bk3s1

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/)
  • 25.05 Release Notes (or backporting 24.11 and 25.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.

@NixOS/k3s


Add a 👍 reaction to pull requests you find important.

@github-actions github-actions bot added 6.topic: k3s Kubernates distribution (https://k3s.io/) 10.rebuild-darwin: 0 This PR does not cause any packages to rebuild on Darwin 10.rebuild-linux: 1 10.rebuild-linux: 1-10 labels Feb 4, 2025
@rorosen rorosen changed the title k3s: 1.29.12+k3s1 -> 1.29.13+k3s1 k3s_1_29: 1.29.12+k3s1 -> 1.29.13+k3s1 Feb 5, 2025
@rorosen
Copy link
Contributor Author

rorosen commented Feb 21, 2025

Kindly asking for merge, the rcs for the next release are already available.

Copy link
Member

@wrmilling wrmilling left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM (though I don't have merge rights)

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review pr 379386


x86_64-linux

✅ 1 package built:
  • k3s_1_29

@wrmilling wrmilling added 12.approvals: 1 This PR was reviewed and approved by one reputable person 12.approved-by: package-maintainer This PR was reviewed and approved by a maintainer listed in the package labels Feb 22, 2025
@marcusramberg marcusramberg merged commit 3dff67e into NixOS:master Feb 22, 2025
37 checks passed
@wrmilling wrmilling added backport release-24.11 Backport PR automatically and removed backport release-24.11 Backport PR automatically labels Feb 22, 2025
@rorosen rorosen added the backport release-24.11 Backport PR automatically label Feb 24, 2025
@nixpkgs-ci
Copy link
Contributor

nixpkgs-ci bot commented Feb 24, 2025

Backport failed for release-24.11, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin release-24.11
git worktree add -d .worktree/backport-379386-to-release-24.11 origin/release-24.11
cd .worktree/backport-379386-to-release-24.11
git switch --create backport-379386-to-release-24.11
git cherry-pick -x 36b022d07d45092b812413e6fe284d6fef7057aa

@rorosen rorosen deleted the k3s_1_29 branch February 24, 2025 19:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
6.topic: k3s Kubernates distribution (https://k3s.io/) 10.rebuild-darwin: 0 This PR does not cause any packages to rebuild on Darwin 10.rebuild-linux: 1-10 10.rebuild-linux: 1 12.approvals: 1 This PR was reviewed and approved by one reputable person 12.approved-by: package-maintainer This PR was reviewed and approved by a maintainer listed in the package backport release-24.11 Backport PR automatically
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants