WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
Skip to content
Comments for ensuring backward compatibility

Edit session operation #71

Sign in to view logs

Edit session operation

Edit session operation #71

Triggered via pull request October 18, 2024 14:03
@marinsokol5marinsokol5
synchronize #5657
Status Success
Total duration 17s
Artifacts –
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

backwards-compatibility-commenter.yml

on: pull_request_target
comment
7s
comment
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
comment
The following actions uses node12 which is deprecated and will be forced to run on node16: peter-evans/create-or-update-comment@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
comment
The following actions use a deprecated Node.js version and will be forced to run on node20: peter-evans/create-or-update-comment@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
comment
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/