Use @actions/core.exportVariable instead of set-env (#19)

* fix: use @actions/core.exportVariable instead of set-env

`set-env` is now deprecated. `@actions/core` exposes `exportVariable`
to be used instead.

https://github.com/actions/toolkit/tree/main/packages/core#exporting-variables

* chore: bump @actions/core to v1.2.6
This commit is contained in:
Stig Otnes Kolstad
2020-10-20 08:51:52 +02:00
committed by GitHub
parent 3aa19be838
commit 2f6bfda1e2
19 changed files with 445 additions and 226 deletions
+5 -5
View File
@@ -1,16 +1,16 @@
interface CommandProperties {
[key: string]: string;
[key: string]: any;
}
/**
* Commands
*
* Command Format:
* ##[name key=value;key=value]message
* ::name key=value,key=value::message
*
* Examples:
* ##[warning]This is the user warning message
* ##[set-secret name=mypassword]definitelyNotAPassword!
* ::warning::This is the message
* ::set-env name=MY_VAR::some value
*/
export declare function issueCommand(command: string, properties: CommandProperties, message: string): void;
export declare function issueCommand(command: string, properties: CommandProperties, message: any): void;
export declare function issue(name: string, message?: string): void;
export {};