All workflows publish.yml

Actor

All actors alan

Status

All status Success Failure Waiting Running

Mostly just commented out a lot of the extra debugging log noise

#24 -Commit 159599c777 pushed by alan

main

2025-06-24 22:04:26 +00:00

40s

Added more debugging

#23 -Commit 344a417c31 pushed by alan

main

2025-06-24 20:09:18 +00:00

44s

Trying explicitly throwing error to trigger catch clause

#22 -Commit 21469c647a pushed by alan

main

2025-06-24 19:47:16 +00:00

37s

Trying explicitly throwing error to trigger catch clause

#21 -Commit b71329a1be pushed by alan

main

2025-06-24 19:34:13 +00:00

53s

Trying explicitly throwing error to trigger catch clause

#20 -Commit b5f7c028e2 pushed by alan

main

2025-06-24 18:59:52 +00:00

31s

Publish to Private NPM Registry

#19 -Commit 3a9bb1ad05 pushed by alan

main

2025-06-24 18:42:28 +00:00

26s

Added more stuff for debugging to figure out what is happening

#18 -Commit b357cf3f8f pushed by alan

main

2025-06-24 18:38:18 +00:00

30s

A workaround (maybe) for a really annoying issue with error handling and how parameters get passed to what

#17 -Commit 9a073f6dca pushed by alan

main

2025-06-24 17:20:49 +00:00

33s

Forgot to change code in second spot (this is why DRY principal exists etc...)

#16 -Commit 711007a67a pushed by alan

main

2025-06-24 17:00:07 +00:00

44s

Because for async contexts the

#15 -Commit 203d0488e6 pushed by alan

main

2025-06-24 16:43:04 +00:00

42s

Attempting to handle async properly under this new wrapping strategy in the hope that makes both async and normal functions act consistently

#14 -Commit 0305f5eaeb pushed by alan

main

2025-06-24 16:15:57 +00:00

43s

Reverting back from pp.use to pp.get but adding some debugging to see if I can find a path forward

#13 -Commit 33511adf1c pushed by alan

main

2025-06-24 14:16:08 +00:00

40s

Added return to see if that stops timed out error

#12 -Commit 73c2c404cf pushed by alan

main

2025-06-24 13:54:10 +00:00

32s

Seeing if by using pp.use instead of pp.get I get the next function as expected that would allow for proper error handling withn the decorators

#11 -Commit 338e67e4d2 pushed by alan

main

2025-06-24 13:28:17 +00:00

44s

Seemingly accidentally ended up with an infinite loop.Hopefullly this fixes it

#10 -Commit ecb9a27d8d pushed by alan

main

2025-06-24 12:42:30 +00:00

43s

Attempting change to Controller's setup to see if it fixes error handling problem

#9 -Commit 868a8aaadb pushed by alan

main

2025-06-24 12:23:40 +00:00

43s

Even More Debugging

#8 -Commit e3ba1639c4 pushed by alan

main

2025-06-24 11:48:11 +00:00

47s

More Debugging

#7 -Commit eb7dcaf556 pushed by alan

main

2025-06-24 01:25:03 +00:00

33s

Debugging

#6 -Commit d8e8c3bbcd pushed by alan

main

2025-06-24 00:43:57 +00:00

50s

Attempted to add proper error handling within the Page decorator such that errors are handled consistently both with and without the Page decorator

#5 -Commit a308d69766 pushed by alan

main

2025-06-23 21:48:04 +00:00

55s

Small change to the global template values middleware that should fix issue with downstream web app

#4 -Commit e7b291c78d pushed by alan

main

2025-06-18 10:20:13 +00:00

45s

Small changes mostly intended to re-trigger automation

#3 -Commit 8b12c0cc6c pushed by alan

main

2025-06-18 10:15:48 +00:00

1m2s

Slight mismatch with version numbers meant automation didn't work

#2 -Commit 527372c344 pushed by alan

main

2025-06-18 10:08:42 +00:00

39s

Changed automation from GitHub to Forgejo + some small improvements

#1 -Commit 56be45cc94 pushed by alan

main

2025-06-18 10:05:01 +00:00

1m24s