Skip to content

[Backport release-23.11] cargo-llvm-lines: 0.4.36 -> 0.4.37#302282

Closed
github-actions[bot] wants to merge 1 commit intorelease-23.11from
backport-302226-to-release-23.11
Closed

[Backport release-23.11] cargo-llvm-lines: 0.4.36 -> 0.4.37#302282
github-actions[bot] wants to merge 1 commit intorelease-23.11from
backport-302226-to-release-23.11

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Apr 7, 2024

Bot-based backport to release-23.11, triggered by a label in #302226.

  • Before merging, ensure that this backport is acceptable for the release.
    • Even as a non-commiter, if you find that it is not acceptable, leave a comment.

(cherry picked from commit 5c9dfe4)
@matthiasbeyer
Copy link
Contributor

Result of nixpkgs-review pr 302282 run on x86_64-linux 1

1 package failed to build:
  • cargo-llvm-lines

@matthiasbeyer
Copy link
Contributor

Picked to #298312

@ofborg ofborg bot requested review from figsoda and matthiasbeyer April 7, 2024 07:56
@ofborg ofborg bot added 10.rebuild-darwin: 1-10 This PR causes between 1 and 10 packages to rebuild on Darwin. 10.rebuild-darwin: 1 This PR causes 1 package to rebuild on Darwin. 10.rebuild-linux: 1-10 This PR causes between 1 and 10 packages to rebuild on Linux. 10.rebuild-linux: 1 This PR causes 1 package to rebuild on Linux. labels Apr 7, 2024
@NickCao NickCao marked this pull request as draft April 7, 2024 14:51
@NickCao NickCao closed this Apr 7, 2024
@matthiasbeyer matthiasbeyer deleted the backport-302226-to-release-23.11 branch April 7, 2024 15:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

10.rebuild-darwin: 1-10 This PR causes between 1 and 10 packages to rebuild on Darwin. 10.rebuild-darwin: 1 This PR causes 1 package to rebuild on Darwin. 10.rebuild-linux: 1-10 This PR causes between 1 and 10 packages to rebuild on Linux. 10.rebuild-linux: 1 This PR causes 1 package to rebuild on Linux.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants