Skip to content

[Backport release-23.11] skarnet.org November 2023 release (2)#271301

Merged
5 commits merged intorelease-23.11from
backport-268744-to-release-23.11
Dec 1, 2023
Merged

[Backport release-23.11] skarnet.org November 2023 release (2)#271301
5 commits merged intorelease-23.11from
backport-268744-to-release-23.11

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions github-actions bot commented Nov 30, 2023

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

  • 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.

@alyssais @github-actions
skalibs: 2.14.0.0 -> 2.14.0.1
bf58bd2 
(cherry picked from commit fe3ac5f)
@alyssais @github-actions
s6: 2.12.0.0 -> 2.12.0.2
fcda1d9 
(cherry picked from commit ea737ef)
@alyssais @github-actions
s6-dns: 2.3.6.0 -> 2.3.7.0
dd5557f 
(cherry picked from commit 50c2a7a)
@alyssais @github-actions
s6-networking: 2.6.0.0 -> 2.7.0.0
48e0339 
(cherry picked from commit 9dcf049)
@alyssais @github-actions
tipidee: 0.0.1.0 -> 0.0.2.0
c9517c6 
(cherry picked from commit 9916e82)
@github-actions github-actions bot mentioned this pull request Nov 30, 2023
Merged
13 tasks
ghost
ghost approved these changes Nov 30, 2023
View reviewed changes
Copy link
Copy Markdown

@ghost ghost left a comment •
edited by ghost
Loading

Choose a reason for hiding this comment

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

I'm inclined to consider the s6-networking changes non-breaking for release purposes, since it sounds like the circumstances in which they are breaking are very minor.

Me too. @figsoda @RaitoBezarius please consider merging this backport; it won't break anything and if it does you can blame me.

Edit: minor note: I don't use tipidee so actually I can't vouch for that. But it's such pre-alpha software that I can't imagine anybody is using it in a serious way. If you're super-paranoid maybe drop c9517c6 from this PR but I don't think that's really necessary.

@delroth delroth added the 12.approvals: 1 This PR was reviewed and approved by one person. label Nov 30, 2023
@RaitoBezarius
Copy link
Copy Markdown
Member

RaitoBezarius commented Dec 1, 2023

Please feel free to proceed as you see fit :) ; LGTM.

@delroth delroth added 12.approvals: 2 This PR was reviewed and approved by two persons. and removed 12.approvals: 1 This PR was reviewed and approved by one person. labels Dec 1, 2023
@ofborg ofborg bot added 10.rebuild-darwin: 11-100 This PR causes between 11 and 100 packages to rebuild on Darwin. 10.rebuild-linux: 11-100 This PR causes between 11 and 100 packages to rebuild on Linux. labels Dec 1, 2023
@ghost ghost merged commit 62c9696 into release-23.11 Dec 1, 2023
@ghost
Copy link
Copy Markdown

ghost commented Dec 1, 2023

Thanks. I am extra-careful with the release branches; I don't generally merge things to them unless I get an explicit ok from the release maintainers.

@ghost ghost deleted the backport-268744-to-release-23.11 branch December 1, 2023 21:51
@RaitoBezarius
Copy link
Copy Markdown
Member

RaitoBezarius commented Dec 1, 2023

And thank you for being excellent on that!

This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@RaitoBezarius RaitoBezarius RaitoBezarius approved these changes

+1 more reviewer
Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

10.rebuild-darwin: 11-100 This PR causes between 11 and 100 packages to rebuild on Darwin. 10.rebuild-linux: 11-100 This PR causes between 11 and 100 packages to rebuild on Linux. 12.approvals: 2 This PR was reviewed and approved by two persons.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@RaitoBezarius @delroth @alyssais