`set-output` command is deprecated and will be disabled soon

[shenxianpeng]

[cpp-linter (11)](https://github.com/cpp-linter/test-cpp-linter-action/actions/runs/3247052956/jobs/5326536419#step:11:145)
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/

[cpp-linter (9)](https://github.com/cpp-linter/test-cpp-linter-action/actions/runs/3247052956/jobs/5326536298)
Node.js 12 actions are deprecated. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/. Please update the following actions to use Node.js 16: actions/checkout, actions/checkout

see https://github.com/cpp-linter/test-cpp-linter-action/actions/runs/3247052956

[2bndy5]

Using an env var seems easy to migrate to, but both v1 and v2 have to be adjusted... Unless you want v1 to become [more] broken.

[2bndy5]

The second warning isn't a problem with the cpp-linter-action. It just means that we have to update the version of actions/checkout used in the workflow file. I recently had to solve this with another repo.

[shenxianpeng]

I opened a PR for v2 cpp-linter/cpp-linter#13, I think we should also migrate to v1

[2bndy5]

looks like v1 is already set to use the latest cpp-linter release:

cpp-linter-action/setup.py

Line 13 in 17526ee

install_requires=["cpp-linter"],

I'm ok with that, but feel free to pin it to a specific version if you want.

[shenxianpeng]

OK, I will open another PR to pin it to v1.4.9