Issue 190: Use GITHUB_OUTPUT environment file to set output.

This follows the guidelines described in
https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
This commit is contained in:
Josu Vergara Lecue 2022-10-26 21:17:29 +02:00
parent 8502f4970e
commit e02ebb3d92
No known key found for this signature in database
GPG Key ID: BA675D52ED953D82
1 changed files with 3 additions and 2 deletions

View File

@ -202,7 +202,8 @@ const pkg = getPackageJson();
console.log('newVersion 2:', newVersion);
newVersion = `${tagPrefix}${newVersion}`;
console.log(`newVersion after merging tagPrefix+newVersion: ${newVersion}`);
console.log(`::set-output name=newTag::${newVersion}`);
// Using sh as command instead of directly echo to be able to use file redirection
await runInWorkspace('sh', ['-c', `echo "newTag=${newVersion}" >> $GITHUB_OUTPUT`]);
try {
// to support "actions/checkout@v1"
if (process.env['INPUT_SKIP-COMMIT'] !== 'true') {
@ -210,7 +211,7 @@ const pkg = getPackageJson();
}
} catch (e) {
console.warn(
'git commit failed because you are using "actions/checkout@v2"; ' +
'git commit failed because you are using "actions/checkout@v2" or later; ' +
'but that doesnt matter because you dont need that git commit, thats only for "actions/checkout@v1"',
);
}