Skip to content

actions - add actual full version to log ? #286

Open
@MSP-Greg

Description

@MSP-Greg

Recently had a issue with checking out a ref (tag) on a repo installed/cloned via this action. Something recently broke what previously worked. Not quite sure as to the cause, but I wondered one thing.

Most people pin actions to the major version in workflows. Could actions start logging the full version in the log? It would help when things are acting 'odd'.

I've got a public custom action, with a dist folder, and I just added the following line in js code:

const version = JSON.parse(fs.readFileSync(`${__dirname}\\package.json`, 'utf8')).version

And then logged it.

Building it copied package.json it to the dist folder, but it's a small, and that way the version isn't duplicated...

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions