7 Jul 2026
ugexe my guess is she copy pasted the text it shows when selecting squash and merge but then switched to regular merge and copied that text in. Alternatively github automatically populated that title/description when selecting squash first and then changing to merge 17:42
github.com/rakudo/rakudo/commit/58...952b635d0e 17:43
github.com/rakudo/rakudo/commit/d8...72d0cd3d28
(shown to show the default merge commit title/description, and the confusing one) 17:44
[Coke] (it is weird)++ 17:45
ugexe so my assumption is releasable is confused, i.e. it tries to match `Merge pull request ..`
finanalyst finanalyst joined 17:48
[Coke] I think it reports the same way, it's *me* that gets confused when it doesn't say merge, because then I can't tell by looking at releasable output that it's a merge. 17:56
... and if I click on the "merge" commit, github isn't showing it as a merge - in the other cases, it shows me "this merges PR#xxx" and I can click on the PR #, and see the commit IDs in the UI 17:57
... i never did start a point release for moarvm. 18:19
Will do that today
raku.land/cpan:JNTHN/JSON::Schema shows a copyright on alexander, but cpan author of JNTHN 19:11
... it also fails to install on a recent rakudo. :(
is github.com/croservices/json-schema/issues the correct REPO still? 19:12
lizmat yeah, looks like... 19:16
guess we could transfer it to ramu community modules 19:17
[Coke] github.com/croservices/json-schema/issues/9 19:19
do we "own" croservices now? or how does that work.
ugexe wow, a bot trying to get you to download a virus or whatever 19:23
lizmat looks like it installs if you install ECMA262Regex separately first 19:31
[Coke] that module is already installed 19:34
checking versions... 19:35
ugexe you think its specific to windows though? 19:36
[Coke] It could be, I don't know.
Looks like I have ECMA262 installed at the latest version (1.2) 19:37