Introduce MutatingScope::getCallableParameterType #19090
VincentLangletAnnotations
343 errors and 95 warnings
|
Analyse (2)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (4)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (4)
A task was canceled.
|
|
Analyse (1)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (1)
A task was canceled.
|
|
Analyse (14)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (40)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (32)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (5)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (35)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (5)
The operation was canceled.
|
|
Analyse (61)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (63)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (88)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (7)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (7)
A task was canceled.
|
|
Analyse (9)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (9)
The operation was canceled.
|
|
Analyse (6)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (6)
A task was canceled.
|
|
Analyse (24)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (24)
The operation was canceled.
|
|
Analyse (16)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (16)
A task was canceled.
|
|
Analyse (83)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (13)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (13)
A task was canceled.
|
|
Analyse (39)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (39)
The operation was canceled.
|
|
Analyse (28)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (22)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (28)
The operation was canceled.
|
|
Analyse (22)
The operation was canceled.
|
|
Analyse (17)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (17)
A task was canceled.
|
|
Analyse (12)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (12)
A task was canceled.
|
|
Analyse (8)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (109)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (8)
The operation was canceled.
|
|
Analyse (23)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (23)
A task was canceled.
|
|
Analyse (94)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (10)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (10)
The operation was canceled.
|
|
Analyse (11)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (11)
A task was canceled.
|
|
Analyse (36)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (36)
A task was canceled.
|
|
Analyse (34)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (19)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (100)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (34)
A task was canceled.
|
|
Analyse (19)
A task was canceled.
|
|
Analyse (102)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (46)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (46)
A task was canceled.
|
|
Analyse (54)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (45)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (54)
A task was canceled.
|
|
Analyse (45)
The operation was canceled.
|
|
Analyse (31)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (31)
A task was canceled.
|
|
Analyse (25)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (49)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (25)
A task was canceled.
|
|
Analyse (49)
A task was canceled.
|
|
Analyse (48)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (30)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (48)
The operation was canceled.
|
|
Analyse (30)
The operation was canceled.
|
|
Analyse (47)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (47)
A task was canceled.
|
|
Analyse (64)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (82)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (64)
The operation was canceled.
|
|
Analyse (82)
The operation was canceled.
|
|
Analyse (50)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (131)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (50)
A task was canceled.
|
|
Analyse (74)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (52)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (74)
The operation was canceled.
|
|
Analyse (52)
The operation was canceled.
|
|
Analyse (43)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (43)
A task was canceled.
|
|
Analyse (56)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (56)
A task was canceled.
|
|
Analyse (51)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (51)
A task was canceled.
|
|
Analyse (75)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (75)
A task was canceled.
|
|
Analyse (59)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (59)
A task was canceled.
|
|
Analyse (20)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (20)
The operation was canceled.
|
|
Analyse (55)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (26)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (15)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (26)
The operation was canceled.
|
|
Analyse (15)
A task was canceled.
|
|
Analyse (55)
The operation was canceled.
|
|
Analyse (27)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (27)
A task was canceled.
|
|
Analyse (138)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (140)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (65)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (139)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (65)
The operation was canceled.
|
|
Analyse (44)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (67)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (44)
A task was canceled.
|
|
Analyse (67)
A task was canceled.
|
|
Analyse (145)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (157)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (70)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (70)
A task was canceled.
|
|
Analyse (42)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (42)
The operation was canceled.
|
|
Analyse (155)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (72)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (72)
The operation was canceled.
|
|
Analyse (57)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (53)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (57)
The operation was canceled.
|
|
Analyse (53)
The operation was canceled.
|
|
Analyse (62)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (62)
The operation was canceled.
|
|
Analyse (69)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (69)
The operation was canceled.
|
|
Analyse (152)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (153)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (86)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (86)
The operation was canceled.
|
|
Analyse (147)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (77)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (77)
The operation was canceled.
|
|
Analyse (91)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (91)
The operation was canceled.
|
|
Analyse (68)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (68)
The operation was canceled.
|
|
Analyse (89)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (89)
The operation was canceled.
|
|
Analyse (81)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (81)
The operation was canceled.
|
|
Analyse (105)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (105)
A task was canceled.
|
|
Analyse (186)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (87)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (87)
The operation was canceled.
|
|
Analyse (85)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (95)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (103)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (85)
A task was canceled.
|
|
Analyse (95)
The operation was canceled.
|
|
Analyse (107)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (103)
A task was canceled.
|
|
Analyse (107)
The operation was canceled.
|
|
Analyse (111)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (111)
The operation was canceled.
|
|
Analyse (76)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (76)
A task was canceled.
|
|
Analyse (124)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (124)
The operation was canceled.
|
|
Analyse (80)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (80)
A task was canceled.
|
|
Analyse (110)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (110)
A task was canceled.
|
|
Analyse (127)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (127)
The operation was canceled.
|
|
Analyse (120)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (120)
The operation was canceled.
|
|
Analyse (118)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (118)
A task was canceled.
|
|
Analyse (122)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (122)
The operation was canceled.
|
|
Analyse (136)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (134)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (136)
The operation was canceled.
|
|
Analyse (134)
The operation was canceled.
|
|
Analyse (165)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (165)
A task was canceled.
|
|
Analyse (220)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (121)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (121)
A task was canceled.
|
|
Analyse (123)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (146)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (123)
The operation was canceled.
|
|
Analyse (146)
A task was canceled.
|
|
Analyse (141)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (141)
The operation was canceled.
|
|
Analyse (158)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (158)
The operation was canceled.
|
|
Analyse (161)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (161)
A task was canceled.
|
|
Analyse (174)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (174)
The operation was canceled.
|
|
Analyse (176)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (176)
The operation was canceled.
|
|
Analyse (191)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (191)
The operation was canceled.
|
|
Analyse (169)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (169)
A task was canceled.
|
|
Analyse (209)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (209)
The operation was canceled.
|
|
Analyse (183)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (183)
The operation was canceled.
|
|
Analyse (182)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (182)
A task was canceled.
|
|
Analyse (193)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (193)
A task was canceled.
|
|
Analyse (177)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (177)
The operation was canceled.
|
|
Analyse (208)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (208)
The operation was canceled.
|
|
Analyse (207)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (207)
The operation was canceled.
|
|
Analyse (223)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (223)
A task was canceled.
|
|
Analyse (203)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (203)
The operation was canceled.
|
|
Analyse (205)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (205)
The operation was canceled.
|
|
Analyse (222)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (222)
A task was canceled.
|
|
Analyse (215)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (215)
The operation was canceled.
|
|
Analyse (218)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (167)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (218)
The operation was canceled.
|
|
Analyse (167)
A task was canceled.
|
|
Analyse (196)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (196)
The operation was canceled.
|
|
Analyse (60)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (58)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (163)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (96)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (187)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (79)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (185)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (99)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (84)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (41)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (179)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (217)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (212)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (221)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (112)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (213)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (199)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (108)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (73)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (106)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (178)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (125)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (116)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (38)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (115)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (130)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (137)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (151)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (117)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (114)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (148)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (188)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (210)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (29)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (78)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (150)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (133)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (211)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (104)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (171)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (113)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (162)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (101)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (144)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (192)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (219)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (184)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (92)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (194)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (190)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (119)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (143)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (197)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (180)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (126)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (168)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (173)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (206)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (135)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (200)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (204)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (189)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (149)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (170)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (214)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (164)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (132)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (90)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (159)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (181)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (201)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (216)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (175)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (154)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (224)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (129)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (195)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (142)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (128)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (172)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (202)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (18)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (18)
The operation was canceled.
|
|
Analyse (93)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (93)
The operation was canceled.
|
|
Analyse (97)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (97)
The operation was canceled.
|
|
Analyse (71)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (71)
The operation was canceled.
|
|
Analyse (156)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (156)
The operation was canceled.
|
|
Analyse (166)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (166)
The operation was canceled.
|
|
Analyse (98)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (98)
The operation was canceled.
|
|
Analyse (33)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (33)
The operation was canceled.
|
|
Analyse (66)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (66)
The operation was canceled.
|
|
Analyse (160)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (160)
The operation was canceled.
|
|
Analyse (21)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (21)
The operation was canceled.
|
|
Analyse (37)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (37)
The operation was canceled.
|
|
Analyse (198)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (198)
The operation was canceled.
|
|
Analyse (0)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Analyse (3)
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Issue bot
Canceling since a higher priority waiting request for run-issue-bot-refactor/mutatingScope exists
|
|
Download data
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/cache@v4, actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (60)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (58)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (163)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (96)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (187)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (185)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (79)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (99)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (84)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (41)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (179)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (217)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (212)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (221)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (112)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (213)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (199)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (108)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (73)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (106)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (178)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (125)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (116)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (38)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (115)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (130)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (137)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (151)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (117)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (114)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (148)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (188)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (210)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (29)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (78)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (150)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (133)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (211)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (104)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (113)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (171)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (162)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (101)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (144)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (192)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (219)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (184)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (92)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (194)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (190)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (119)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (143)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (197)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (180)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (126)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (168)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (173)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (206)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (135)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (200)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (204)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (189)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (149)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (170)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (214)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (164)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (132)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (90)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (159)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (181)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (201)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (216)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (175)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (154)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (224)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (129)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (195)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (142)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (128)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (172)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (202)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (18)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (93)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (97)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (71)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (156)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (166)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (98)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (33)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (66)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (160)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (21)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (37)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Analyse (198)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, Wandalen/wretry.action@v3.8.0_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
issue-cache
|
486 KB |
sha256:595839db0760e226ceb971738d8df96ecc241ccf6a98dfbf13ca617b396f8572
|
|
|
matrix
|
270 KB |
sha256:a85ef510f80d491c3c30c6b1d7eafa56b5ebafc27513cd1445ad40706e741ca8
|
|
|
playground-cache
|
462 KB |
sha256:702a638b6571a991d55ca997d2e382f1052301d58594ac1b5382c994ee3f509b
|
|