Bump @actions/core from 1.0.0 to 1.2.6

[dependabot]

Bumps @actions/core from 1.0.0 to 1.2.6.

Changelog

Sourced from @actions/core's changelog.

1.2.6

• Update exportVariable and addPath to use environment files

1.2.5

• Correctly bundle License File with package

1.2.4

• Be more lenient in accepting non-string command inputs
• Add Echo commands

1.2.3

• IsDebug logging

1.2.2

• Fix escaping for runner commands

1.2.1

• Remove trailing comma from commands
• Add "types" to package.json

1.2.0

• saveState and getState functions for wrapper tasks (on finally entry points that run post job)

1.1.3

• setSecret added to register a secret with the runner to be masked from the logs
• exportSecret which was not implemented and never worked was removed after clarification from product.

1.1.1

• Add support for action input variables with multiple spaces #127
• Switched ## commands to :: commands (should have no noticeable impact) [#110)(https://github-redirect.dependabot.com/Update to use :: instead of ## actions/toolkit#110)

1.1.0

• Added helpers for group and endgroup #98

Commits

• See full diff in compare view

Maintainer changes

This version was pushed to npm by thboop, a new releaser for @actions/core since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

[kdorosh]

@rsora also note that to fix this, we will need to run npm install and commit the new node modules. This is what we had to do to get the errors to go away on our fork. Happy to help with this

[rsora]

@kdorosh Could you check that the current master is ok and contains the correct runtime dependencies?
Thanks! 🙇

[kdorosh]

sure, #17