Don't remember types after impure assignments #18579
clxmstaabAnnotations
324 errors and 224 warnings
|
Analyse (15)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (0)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (16)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (1)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (107)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (76)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (28)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (151)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (101)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (101)
The operation was canceled.
|
|
Analyse (86)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (105)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (121)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (121)
The operation was canceled.
|
|
Analyse (130)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (130)
The operation was canceled.
|
|
Analyse (83)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (194)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (118)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (134)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (134)
The operation was canceled.
|
|
Analyse (176)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (94)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (163)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (163)
The operation was canceled.
|
|
Analyse (78)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (53)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (6)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (164)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (19)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (138)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (138)
The operation was canceled.
|
|
Analyse (204)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (29)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (146)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (59)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (93)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (155)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (195)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (188)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (47)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (120)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (208)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (140)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (4)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (63)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (135)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (8)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (68)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (136)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (23)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (223)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (26)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (137)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (56)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (89)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (169)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (149)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (181)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (55)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (212)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (199)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (30)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (113)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (203)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (185)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (82)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (57)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (12)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (192)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (182)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (65)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (172)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (145)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (108)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (61)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (205)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (43)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (34)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (10)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (95)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (219)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (197)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (36)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (191)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (111)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (72)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (158)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (104)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (156)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (22)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (91)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (184)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (84)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (215)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (160)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (81)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (60)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (110)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (179)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (187)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (207)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (100)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (54)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (129)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (99)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (112)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (131)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (39)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (148)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (174)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (147)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (132)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (11)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (103)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (221)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (190)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (177)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (49)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (70)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (143)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (200)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (200)
The operation was canceled.
|
|
Analyse (202)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (119)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (193)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (193)
The operation was canceled.
|
|
Analyse (178)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (180)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (46)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (109)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (217)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (141)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (157)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (224)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (142)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (80)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (42)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (166)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (33)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (32)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (32)
A task was canceled.
|
|
Analyse (114)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (150)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (150)
The operation was canceled.
|
|
Analyse (153)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (45)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (77)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (77)
The operation was canceled.
|
|
Analyse (216)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (216)
The operation was canceled.
|
|
Analyse (74)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (74)
The operation was canceled.
|
|
Analyse (124)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (124)
The operation was canceled.
|
|
Analyse (48)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (48)
The operation was canceled.
|
|
Analyse (87)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (87)
The operation was canceled.
|
|
Analyse (123)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (123)
The operation was canceled.
|
|
Analyse (88)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (88)
The operation was canceled.
|
|
Analyse (92)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (92)
The operation was canceled.
|
|
Analyse (106)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (106)
The operation was canceled.
|
|
Analyse (20)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (20)
The operation was canceled.
|
|
Analyse (96)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (35)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (96)
The operation was canceled.
|
|
Analyse (35)
The operation was canceled.
|
|
Analyse (25)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (25)
The operation was canceled.
|
|
Analyse (67)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (67)
The operation was canceled.
|
|
Analyse (27)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (27)
The operation was canceled.
|
|
Analyse (117)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (13)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (44)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (117)
The operation was canceled.
|
|
Analyse (13)
The operation was canceled.
|
|
Analyse (44)
The operation was canceled.
|
|
Analyse (5)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (5)
The operation was canceled.
|
|
Analyse (173)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (173)
The operation was canceled.
|
|
Analyse (7)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (90)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (7)
The operation was canceled.
|
|
Analyse (90)
The operation was canceled.
|
|
Analyse (210)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (210)
The operation was canceled.
|
|
Analyse (69)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (186)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (186)
The operation was canceled.
|
|
Analyse (69)
The operation was canceled.
|
|
Analyse (154)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (154)
The operation was canceled.
|
|
Analyse (66)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (66)
The operation was canceled.
|
|
Analyse (17)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (17)
The operation was canceled.
|
|
Analyse (125)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (24)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (125)
The operation was canceled.
|
|
Analyse (24)
The operation was canceled.
|
|
Analyse (2)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (139)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (2)
The operation was canceled.
|
|
Analyse (139)
The operation was canceled.
|
|
Analyse (64)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (64)
The operation was canceled.
|
|
Analyse (51)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (51)
The operation was canceled.
|
|
Analyse (41)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (79)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (41)
The operation was canceled.
|
|
Analyse (79)
The operation was canceled.
|
|
Analyse (18)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (18)
The operation was canceled.
|
|
Analyse (115)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (115)
The operation was canceled.
|
|
Analyse (222)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (127)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (222)
The operation was canceled.
|
|
Analyse (127)
The operation was canceled.
|
|
Analyse (162)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (162)
The operation was canceled.
|
|
Analyse (168)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (168)
The operation was canceled.
|
|
Analyse (31)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (31)
The operation was canceled.
|
|
Analyse (75)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (75)
The operation was canceled.
|
|
Analyse (58)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (116)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (58)
The operation was canceled.
|
|
Analyse (116)
The operation was canceled.
|
|
Analyse (170)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (170)
The operation was canceled.
|
|
Analyse (37)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (37)
The operation was canceled.
|
|
Analyse (171)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (171)
The operation was canceled.
|
|
Analyse (201)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (201)
The operation was canceled.
|
|
Analyse (3)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (128)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (3)
The operation was canceled.
|
|
Analyse (128)
The operation was canceled.
|
|
Analyse (9)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (9)
The operation was canceled.
|
|
Analyse (102)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (102)
The operation was canceled.
|
|
Analyse (133)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (133)
The operation was canceled.
|
|
Analyse (50)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (50)
The operation was canceled.
|
|
Analyse (52)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (52)
The operation was canceled.
|
|
Analyse (71)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (71)
The operation was canceled.
|
|
Analyse (98)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (98)
The operation was canceled.
|
|
Analyse (38)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (196)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (38)
The operation was canceled.
|
|
Analyse (196)
The operation was canceled.
|
|
Analyse (198)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (21)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (198)
The operation was canceled.
|
|
Analyse (21)
The operation was canceled.
|
|
Analyse (218)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (40)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (218)
The operation was canceled.
|
|
Analyse (213)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (40)
The operation was canceled.
|
|
Analyse (73)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (213)
The operation was canceled.
|
|
Analyse (161)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (73)
The operation was canceled.
|
|
Analyse (161)
The operation was canceled.
|
|
Analyse (152)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (152)
The operation was canceled.
|
|
Analyse (167)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (167)
The operation was canceled.
|
|
Analyse (122)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (122)
The operation was canceled.
|
|
Analyse (62)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (62)
The operation was canceled.
|
|
Analyse (165)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (165)
The operation was canceled.
|
|
Analyse (206)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (206)
The operation was canceled.
|
|
Analyse (189)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (189)
The operation was canceled.
|
|
Analyse (14)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (14)
The operation was canceled.
|
|
Analyse (85)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (85)
The operation was canceled.
|
|
Analyse (97)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (209)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (97)
The operation was canceled.
|
|
Analyse (209)
The operation was canceled.
|
|
Analyse (220)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (220)
The operation was canceled.
|
|
Analyse (175)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (211)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (175)
The operation was canceled.
|
|
Analyse (211)
The operation was canceled.
|
|
Analyse (144)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (144)
The operation was canceled.
|
|
Analyse (159)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (159)
The operation was canceled.
|
|
Analyse (183)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (183)
The operation was canceled.
|
|
Analyse (126)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (126)
The operation was canceled.
|
|
Analyse (214)
Canceling since a higher priority waiting request for run-issue-bot-no-impre exists
|
|
Analyse (214)
The request was canceled due to the configured HttpClient.Timeout of 100 seconds elapsing.
|
|
Issue bot
Canceling since a higher priority waiting request for run-issue-bot-no-impre 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 (15)
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 (0)
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 (16)
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 (1)
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 (107)
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 (76)
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 (28)
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 (101)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, 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 (86)
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 (105)
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 (121)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, 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: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, 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 (83)
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 (118)
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 (134)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, 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 (176)
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 (94)
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: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, 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 (53)
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 (6)
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 (19)
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 (138)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, 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 (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 (146)
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 (59)
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 (93)
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 (155)
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 (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 (47)
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 (120)
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 (208)
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 (140)
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 (4)
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 (63)
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 (8)
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 (68)
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 (136)
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 (23)
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 (223)
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 (26)
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 (56)
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 (89)
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 (169)
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 (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 (55)
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 (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 (30)
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 (203)
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 (82)
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 (57)
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 (12)
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 (182)
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 (65)
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 (145)
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 (61)
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 (205)
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 (43)
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 (34)
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 (10)
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 (95)
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 (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 (36)
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 (191)
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 (111)
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 (72)
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 (158)
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 (156)
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 (22)
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 (91)
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 (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 (215)
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 (160)
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 (81)
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 (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 (110)
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 (207)
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 (100)
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 (54)
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 (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 (131)
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 (39)
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 (174)
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 (147)
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 (11)
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 (103)
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 (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 (177)
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 (49)
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 (70)
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 (200)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, 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 (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 (193)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, 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 (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 (46)
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 (109)
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 (141)
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 (157)
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 (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 (80)
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 (42)
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 (166)
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 (33)
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 (150)
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 (153)
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 (45)
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 (77)
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 (216)
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 (74)
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 (124)
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 (48)
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 (87)
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 (123)
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 (88)
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 (92)
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 (106)
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 (20)
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 (96)
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 (35)
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 (25)
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 (67)
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 (27)
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 (117)
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 (13)
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 (44)
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 (5)
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 (173)
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 (7)
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 (90)
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 (210)
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 (69)
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 (186)
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 (154)
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 (17)
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 (125)
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 (24)
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 (2)
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 (139)
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 (64)
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 (51)
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 (41)
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 (79)
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 (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 (115)
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 (222)
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 (127)
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 (162)
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 (168)
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 (31)
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 (75)
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 (58)
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 (116)
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 (170)
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 (171)
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 (201)
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 (3)
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 (128)
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 (9)
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 (102)
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 (133)
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 (50)
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 (52)
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 (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 (38)
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 (196)
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/
|
|
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 (218)
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 (40)
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 (213)
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 (73)
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 (161)
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 (152)
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 (167)
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 (122)
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 (62)
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 (165)
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 (206)
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 (189)
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 (14)
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 (85)
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 (209)
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 (220)
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 (175)
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 (211)
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 (144)
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 (159)
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 (183)
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 (126)
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
|
519 KB |
sha256:38abee5f5f9c58e55528fa0b034358afcbd6c50b44c5d123770ad6b55a2be33f
|
|
|
matrix
|
279 KB |
sha256:cb00843eb4131924a2390ae67fc462844071dd7ce4396713b22bf282f97aacf1
|
|
|
playground-cache
|
493 KB |
sha256:6d5aecb8fcb77b4c38ef9f0628bd1418fe15736c2e4841c29ce0e1b89e7358f7
|
|