What happened?

Since the update to v2.1.0, this action has not been working for me.
It was working before the change.

I haven't changed my workflow at all.
Here is the code:

uses: actions/[email protected]
        with:
          script: |
            const { Octokit } = require("@octokit/action");
            const octokit = new Octokit
            ({
              auth: '${{ env.GITHUB_TOKEN }}'
            })
            await octokit.rest.repos.createDispatchEvent
            ({
              owner: '${{ github.repository_owner }}',
              repo: '${{ env.GITHUB_ACTIONS_REPO_NAME }}',
              event_type: '${{ env.GITHUB_ACTIONS_EVENT_TYPE_ADD_PARENT_MODULE }}',
              client_payload: {
                 submodule_name: '${{ github.event.repository.name }}'
               }
            });

Is there something I need to change to get this working again?

Versions

v2.1.0

Relevant log output

Unhandled error: Error: [@octokit/auth-action] The token variable is specified more than once. Use either `with.token`, `with.GITHUB-TOKEN`, `with.GITHUB_TOKEN`, or `env.GITHUB_TOKEN`. See https://github.com/octokit/auth-action.js#createactionauth

Code of Conduct

• I agree to follow this project's Code of Conduct

Getting this error since 2020.08.03 10:00 PM GMT+2.

Error: [@octokit/auth-action] `GITHUB_ACTION` environment variable is not set. @octokit/auth-action is meant to be used in GitHub Actions only.

I take it something changed at GitHub's side? Is this something to be addressed by you, GH, or the users?

Description

Node v10 has been deprecated so there is no need to keep giving support to it in our CI.

Context

You can find more details here

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Location: package.json
Error type: The renovate configuration file contains some invalid settings
Message: Configuration option 'packageRules[0].npm' should be a json object, Invalid configuration option: @pika/pack, Invalid configuration option: author, Invalid configuration option: jest, Invalid configuration option: keywords, Invalid configuration option: license, Invalid configuration option: name, Invalid configuration option: packageRules[0].@octokit/auth-token, Invalid configuration option: packageRules[0].@octokit/types, Invalid configuration option: packageRules[0].i, Invalid configuration option: packageRules[1].@octokit/request, Invalid configuration option: packageRules[1].@pika/pack, Invalid configuration option: packageRules[1].@pika/plugin-build-node, Invalid configuration option: packageRules[1].@pika/plugin-ts-standard-pkg, Invalid configuration option: packageRules[1].@types/fetch-mock, Invalid configuration option: packageRules[1].@types/jest, Invalid configuration option: packageRules[1].fetch-mock, Invalid configuration option: packageRules[1].jest, Invalid configuration option: packageRules[1].prettier, Invalid configuration option: packageRules[1].semantic-release, Invalid configuration option: packageRules[1].ts-jest, Invalid configuration option: packageRules[1].typescript, Invalid configuration option: publishConfig, Invalid configuration option: release, Invalid configuration option: renovate, Invalid configuration option: scripts, Invalid configuration option: version, The "npm" object can only be configured at the top level of a config but was found inside "packageRules[0]"

The most used first-party actions/checkout action uses the cleaner token input instead of the 60s-like GITHUB_TOKEN

https://github.com/actions/checkout#usage

Can this also automatically support with.token instead of just GITHUB_TOKEN?

steps:
  - name: My action
    with:
      token: ${{ secrets.GITHUB_TOKEN }}

Describe the need

Following up #104

A few first-party actions like:

• https://github.com/actions/add-to-project/blob/main/src/add-to-project.ts#L38
• https://github.com/actions/github-script/blob/main/src/main.ts#L27

uses kebab-case style for github token, on the community side much more ;)

Nice to have with.github-token support instead of only with.token or with.github_token, like:

steps:
  - name: My action
    with:
      github-token: ${{ github.token }}

SDK Version

No response

API Version

No response

Relevant log output

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

Follow up to #221

Ideally we would do a test_matrix step and then a test step that depends on test_matrix, so that for branch protections we can require test independent of the Node versions we are using.

See this for reference: https://github.com/octokit/core.js/blob/393caf31b2e802ea9be59aa84f90d64f98953fdb/.github/workflows/test.yml#L32

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Cannot push to the Git repository.

semantic-release cannot push the version tag to the branch master on the remote Git repository with URL https://x-access-token:[secure]@github.com/octokit/auth-action.js.

This can be caused by:

• a misconfiguration of the repositoryUrl option
• the repository being unavailable
• or missing push permission for the user configured via the Git credentials on your CI environment

Good luck with your project ✨

Your semantic-release bot 📦🚀

This issue contains a list of Renovate updates and their statuses.

Awaiting Schedule

These updates are awaiting their schedule. Click on a checkbox to ignore the schedule.

• fix(deps): lock file maintenance

• Check this box to trigger a request for Renovate to run again on this repository