Skip to content

moonshine: 0.13.5 -> 0.15.0 - #546531

Merged
SuperSandro2000 merged 2 commits into
NixOS:masterfrom
ap-1:moonshine
Aug 14, 2026
Merged

moonshine: 0.13.5 -> 0.15.0#546531
SuperSandro2000 merged 2 commits into
NixOS:masterfrom
ap-1:moonshine

Conversation

@ap-1

@ap-1 ap-1 commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

changelog

  • It was flagged in a nixos/moonshine: init #544393 review that sleep inhibition via polkit was intended to be optional, but 0.14.1 adds it unconditionally and frames this as a bugfix. I'm choosing to match upstream here, since the rule won't do anything until a user is added to the moonshine group anyway.

Things done

@nixpkgs-ci
nixpkgs-ci Bot requested a review from neobrain July 28, 2026 03:05
@nixpkgs-ci nixpkgs-ci Bot added 8.has: package (update) This PR updates a package to a newer version 10.rebuild-linux: 1-10 This PR causes between 1 and 10 packages to rebuild on Linux. 10.rebuild-darwin: 0 This PR does not cause any packages to rebuild on Darwin. 10.rebuild-linux: 1 This PR causes 1 package to rebuild on Linux. labels Jul 28, 2026
@nixpkgs-review-gha

Copy link
Copy Markdown

nixpkgs-review result

Generated using nixpkgs-review-gha (def992f)

Command: nixpkgs-review pr 546531
Commit: 3eea1292093c0543379b0259324429668e2e9470 (subsequent changes)
Merge: 6f77e5e91b9f054a1db95293ff08aaaff5b6f4d2

Triggered by @coolcuber (35880825)
Logs: https://github.com/coolcuber/nixpkgs-review-gha/actions/runs/30365322722/attempts/1


x86_64-linux

✅ 1 package built:
  • moonshine

aarch64-linux

✅ 1 package built:
  • moonshine

aarch64-darwin

No rebuilds

@neobrain neobrain left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Thanks! Patch looks good and is working fine locally, but it's not a requirement to add yourself to the maintainer list. It would make more sense to add yourself after having done more substantial changes.

Also note there's a weekly auto-update on this package, which is generally a bit easier to review and merge than manual version bumps.

@ap-1

ap-1 commented Jul 28, 2026

Copy link
Copy Markdown
Contributor Author

Thanks! Patch looks good and is working fine locally, but it's not a requirement to add yourself to the maintainer list. It would make more sense to add yourself after having done more substantial changes.

Also note there's a weekly auto-update on this package, which is generally a bit easier to review and merge than manual version bumps.

Thanks for the review! On the maintainer entry, the weekly auto-update is actually the main reason I'd like to be listed. I add myself as a maintainer to packages I use so that I can personally see to getting the r-ryantm PRs merged sooner.

As far as I know there's no prerequisite of prior substantial changes for adopting a package in pkgs/by-name, but let me know if I've missed something. For context, I reviewed your original PR #544596 adding this package, so I'm not picking it up at random.

If there's nothing you'd like changed in the patch itself, could you dismiss the review so this can get merged?

@neobrain

Copy link
Copy Markdown
Contributor

Ah, I didn't notice the context of the original review.

My personal opinion is that maintainers should at minimum test package binaries before submitting updates, which hasn't happened here. Adding new maintainers just so PRs land a day earlier doesn't seem very effective (especially if it comes at the cost of not testing anything).

As you mention I don't think there are strictly documented requirements for becoming a maintainer, but since I'm not yet familiar with the soft conventions around nixpkgs maintainership I'll defer to my intuition there. My review doesn't block things though, so if other people are happy to add you to the list I don't mind.

@uku3lig

uku3lig commented Jul 29, 2026

Copy link
Copy Markdown
Member

0.14.1 was released earlier today, it's probably a good idea to update this PR

@ap-1 ap-1 changed the title moonshine: 0.13.5 -> 0.14.0 moonshine: 0.13.5 -> 0.14.1 Jul 29, 2026
@ap-1
ap-1 force-pushed the moonshine branch 3 times, most recently from b4cfc70 to 2287ce3 Compare July 29, 2026 17:11
@ap-1

ap-1 commented Jul 29, 2026

Copy link
Copy Markdown
Contributor Author

nixpkgs-review result

Generated using nixpkgs-review-gha (d38b08f)

Command: nixpkgs-review pr 546531
Commit: 2287ce37f54e5f707cf87cf3ae8310c075ef2161 (subsequent changes)
Merge: 1373ea79d72fcbc9df6769fc832e96d897c8a241

Logs: https://github.com/ap-1/nixpkgs-review-gha/actions/runs/30474225361/attempts/1


x86_64-linux

✅ 1 package built:
  • moonshine

aarch64-linux

✅ 1 package built:
  • moonshine

@ap-1

ap-1 commented Jul 29, 2026

Copy link
Copy Markdown
Contributor Author

Ah, I didn't notice the context of the original review.

My personal opinion is that maintainers should at minimum test package binaries before submitting updates, which hasn't happened here. Adding new maintainers just so PRs land a day earlier doesn't seem very effective (especially if it comes at the cost of not testing anything).

As you mention I don't think there are strictly documented requirements for becoming a maintainer, but since I'm not yet familiar with the soft conventions around nixpkgs maintainership I'll defer to my intuition there. My review doesn't block things though, so if other people are happy to add you to the list I don't mind.

I did build and run it locally when I opened the PR, but this time I tested game discovery and streaming as well. I avoid ticking the "Tested basic functionality" checkbox when it's unclear what the extent of "basic functionality" is.

maintainers/README.md encourages people who care about a package to assign themselves, no bar of prior work, and there's a documented process for dropping maintainers who go unresponsive. Being listed lets me use nixpkgs-merge-bot on the package, which is more the point than review latency.

Most of my commits on packages I maintain aren't just bumps anyway, and 0.14.1 isn't one either, see the PR body re: polkit. I'm happy to gate it if you'd rather.

If you don't have comments on the patch itself, could you dismiss the review? Requested changes tend to stop committers from picking a PR up even when the reviewer isn't the one merging.

Separately, at some point we should open an issue upstream about dropping their nix/package.nix. There's a fair amount of extraneous config in it that we already handle correctly here.

@repparw

repparw commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

we should open an issue upstream

probably invite the author/whoever maintains their flake/package to be a maintainer here

same for the moonshine module #544393

@ap-1 ap-1 changed the title moonshine: 0.13.5 -> 0.14.1 moonshine: 0.13.5 -> 0.14.5 Jul 31, 2026
@ap-1 ap-1 changed the title moonshine: 0.13.5 -> 0.14.5 moonshine: 0.13.5 -> 0.15.0 Aug 6, 2026
ap-1 added 2 commits August 6, 2026 02:40
Signed-off-by: Anish Pallati <i@anish.land>
Signed-off-by: Anish Pallati <i@anish.land>
@repparw

repparw commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review pr 546531
Commit: 586cd05a2446f03d85dc021474eaffb23a14e645


x86_64-linux

✅ 1 package built:
  • moonshine

@nixpkgs-ci nixpkgs-ci Bot added the 12.approvals: 1 This PR was reviewed and approved by one person. label Aug 7, 2026
@repparw

repparw commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

@neobrain humble bump

@SuperSandroBot

Copy link
Copy Markdown

nixpkgs-review result

Generated using nixpkgs-review-gha (0d7e614)

Command: nixpkgs-review pr 546531
Commit: 586cd05a2446f03d85dc021474eaffb23a14e645 (subsequent changes)
Merge: 7dcd35df250f0669e4811cbb78d7554212162da9

Logs: https://github.com/SuperSandro2000/nixpkgs-review-gha/actions/runs/31805708556/attempts/1


x86_64-linux

✅ 1 package built:
  • moonshine

aarch64-linux

✅ 1 package built:
  • moonshine

@nixpkgs-ci nixpkgs-ci Bot added 12.approvals: 2 This PR was reviewed and approved by two persons. 2.status: merge-bot eligible This PR can be merged by commenting "@NixOS/nixpkgs-merge-bot merge". and removed 12.approvals: 1 This PR was reviewed and approved by one person. labels Aug 14, 2026
@SuperSandro2000
SuperSandro2000 added this pull request to the merge queue Aug 14, 2026
Merged via the queue into NixOS:master with commit 9e8ae85 Aug 14, 2026
32 of 35 checks passed
@ap-1
ap-1 deleted the moonshine branch August 15, 2026 14:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

2.status: merge-bot eligible This PR can be merged by commenting "@NixOS/nixpkgs-merge-bot merge". 8.has: package (update) This PR updates a package to a newer version 10.rebuild-darwin: 0 This PR does not cause any packages 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. 12.approvals: 2 This PR was reviewed and approved by two persons.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants