Skip to content

revision 0.2.4 r1#31

Merged
emilypi merged 4 commits into
emilypi:masterfrom
andreasabel:revision-0.2.4-r1
Apr 18, 2026
Merged

revision 0.2.4 r1#31
emilypi merged 4 commits into
emilypi:masterfrom
andreasabel:revision-0.2.4-r1

Conversation

@andreasabel

@andreasabel andreasabel commented Apr 18, 2026

Copy link
Copy Markdown
Contributor
  • Bump upper dependency bound on base.

  • Add GHC version 9.14.1 to tested-with list.

  • Add GHC version 9.14 to CI build matrix.

  • v0.2.4 revision 1; bump tested-with minor versions

Extends:

This was referenced Apr 18, 2026
@andreasabel

Copy link
Copy Markdown
Contributor Author

Made a revision based on this PR:
2026-04-18T11:27:17Z AndreasAbel nonempty-vector-0.2.4-r1

@emilypi
emilypi merged commit c14b838 into emilypi:master Apr 18, 2026
@emilypi

emilypi commented Apr 18, 2026

Copy link
Copy Markdown
Owner

Thanks all

@emilypi

emilypi commented Apr 18, 2026

Copy link
Copy Markdown
Owner

Wait - i just realized you meant revision to hackage? Why not wait for a response?

@andreasabel

Copy link
Copy Markdown
Contributor Author

Because I had already gotten no response for > 100 days on #28.

@emilypi

emilypi commented Apr 19, 2026

Copy link
Copy Markdown
Owner

You didn't try and contact me by any other means. Sorry, but that's intolerable for me. You can be pushy and fork all you want but don't touch my hackage packages outside of the process that exists for a reason. Clearly I am still around touching packages from time to time. Sometimes I miss a message. You need to not wait only 16 hours after opening a PR to get my attention, or just try another means outside of github issues. There is a maintainer email that exists for this precise reason.

@andreasabel

Copy link
Copy Markdown
Contributor Author

I am sorry, I had to means of telling you would react this time after PR #29 had been open for over 3 months with 2 explicit pings over time.
There is nothing personal here. As a Hackage Trustee, I am concerned about Hackage working for the best of the community, and in this case, there was no reason for keeping the restriction of base any longer.

@andreasabel
andreasabel deleted the revision-0.2.4-r1 branch April 19, 2026 10:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants