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

google-chrome: 134.0.6998.88 -> 134.0.6998.165 #392809

Merged
merged 1 commit into from
Mar 24, 2025

Conversation

s0me1newithhand7s
Copy link
Contributor

trivial update

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.

Add a 👍 reaction to pull requests you find important.

@JohnRTitor JohnRTitor merged commit c63de0f into NixOS:master Mar 24, 2025
20 of 24 checks passed
@s0me1newithhand7s s0me1newithhand7s deleted the google-chrome-update branch March 24, 2025 18:26
@nix-owners nix-owners bot requested review from JohnRTitor and jnsgruk March 24, 2025 18:32
@JohnRTitor JohnRTitor added 1.severity: security Issues which raise a security issue, or PRs that fix one backport release-24.11 Backport PR automatically labels Mar 24, 2025
@nixpkgs-ci
Copy link
Contributor

nixpkgs-ci bot commented Mar 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-392809-to-release-24.11 origin/release-24.11
cd .worktree/backport-392809-to-release-24.11
git switch --create backport-392809-to-release-24.11
git cherry-pick -x c63de0f864537437b9ae7b03188a98dc8f682cd7

1 similar comment
@nixpkgs-ci
Copy link
Contributor

nixpkgs-ci bot commented Mar 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-392809-to-release-24.11 origin/release-24.11
cd .worktree/backport-392809-to-release-24.11
git switch --create backport-392809-to-release-24.11
git cherry-pick -x c63de0f864537437b9ae7b03188a98dc8f682cd7

@s0me1newithhand7s s0me1newithhand7s added backport release-24.11 Backport PR automatically and removed backport release-24.11 Backport PR automatically labels Mar 24, 2025
@nixpkgs-ci
Copy link
Contributor

nixpkgs-ci bot commented Mar 24, 2025

Successfully created backport PR for release-24.11:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1.severity: security Issues which raise a security issue, or PRs that fix one 10.rebuild-darwin: 1-10 10.rebuild-linux: 1-10 backport release-24.11 Backport PR automatically
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants