|
00:54
finanalyst left
10:07
finanalyst joined
10:23
finanalyst left
11:01
rakkable left
11:02
rakkable joined
11:23
[Tux] left
11:27
[Tux] joined
11:33
librasteve_ joined
|
|||
| librasteve_ | rakudoweekly.blog/2026/02/09/2026-...n-gymraeg/ | 12:15 | |
| lizmat | librasteve_++ | 12:26 | |
|
13:55
[Tux] left
14:02
[Tux] joined
19:16
notna joined
|
|||
| notna | Hi @all. | 19:18 | |
| How can one get the "latest" (Star) release information from `www.rakudo.org/star`? | |||
| tellable6 | 2024-05-05T19:45:24Z #raku-dev <ab5tract> notna: I’ve also struggled with the commit message moment after doing long discussions across tickets | ||
| notna | So, something similar to getting the latest source via `rakudo.org/latest/star/src`? | 19:19 | |
| lizmat | I'm not sure I understand the question | 19:23 | |
| notna | Well, as an example... run `curl rakudo.org/star/` and receive something like `2026.01`... | 19:28 | |
| ... or something like `curl api.rakudo.org/star/` and getting a (huge) (json or txt) output for ALL the Star releases with whatever infos per release, where only the `latest` has a `latest` tag... | 19:32 | ||
| lizmat | I don't think there is something like that.. perhaps create an issue in github.com/rakudo/rakudo.org ? | 19:33 | |
| notna | ok | 19:40 | |
| I will ask for something like what I do at github.com/rakudo/star/blob/525bb8...43-L30C131 there then | 19:42 | ||
| hope, that makes sense... | |||
| lizmat | yeah, it does :-) | 19:45 | |
| Geth | rakudo/main: eeb97aca99 | (Elizabeth Mattijsen)++ | src/core.c/Exception.rakumod Make error reporting more resilient wrt warnings To prevent: Unhandled exception: No exception handler located for warn Found while looking at a role composition issue. |
19:47 | |
|
20:50
notna left,
notna joined,
notna left
|
|||