nordicsemiconductor / asset-tracker-cloud-memfault-aws-js Goto Github PK

🚨 The automated release from the saga branch failed. 🚨

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

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 fix 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 saga branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are 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 saga on the remote Git repository with URL https://x-access-token:[secure]@github.com/NordicSemiconductor/asset-tracker-cloud-memfault-aws-js.git.

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 📦🚀

If the device reports an unknown hardware version, it will fail. Therefore, on failure, see if the hardware version needs to be created.

{
    "hardware_version": "thingy91_nrf9160-v2",
    "deviceId": "352656106654760"
}

{
    "status": 404,
    "headers": {
        "date": "Tue, 15 Mar 2022 13:17:08 GMT",
        "content-type": "application/json",
        "content-length": "133",
        "connection": "close",
        "server": "nginx",
        "x-frame-options": "SAMEORIGIN",
        "x-xss-protection": "1; mode=block",
        "x-content-type-options": "nosniff",
        "strict-transport-security": "max-age=60; includeSubDomains",
        "referrer-policy": "strict-origin-when-cross-origin",
        "set-cookie": [
            "csrf_token=a1626df8fc13b8788424553cb4d5a8f4b235096606f84394a5f6660452da5dea; Expires=Sun, 20 Mar 2022 13:17:08 GMT; Max-Age=432000; Secure; Path=/; SameSite=Lax",
            "session=eyJjc3JmX3Rva2VuIjoiYTE2MjZkZjhmYzEzYjg3ODg0MjQ1NTNjYjRkNWE4ZjRiMjM1MDk2NjA2Zjg0Mzk0YTVmNjY2MDQ1MmRhNWRlYSJ9.YjCR1A.fFYZYKP6FECOADVnndG8kswqXHU; Secure; HttpOnly; Path=/"
        ],
        "vary": "Cookie",
        "cache-control": "no-cache, no-store"
    },
    "body": "{\"error\":{\"code\":1003,\"http_code\":404,\"message\":\"HardwareVersion with name `thingy91_nrf9160-v2` not found\",\"type\":\"NotFoundError\"}}\n"
}

The testthingpolicycleanuppolicyCleanUp200989B6 does not work.

CloudFormation did not receive a response from your Custom Resource. Please check your logs for requestId [3e5577d5-c670-4e0a-9003-2f0773e2fddb]. If you are using the Python cfn-response module, you may need to update your Lambda function code so that CloudFormation can attach the updated version.

Replace jest with the Node.js test runner (and tsmatchers for assertions if needed).

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Repository problems

These problems occurred while renovating this repository. View logs.

• WARN: Fallback to renovate.json file as a preset is deprecated, please use a default.json file instead.

This repository currently has no open or pending branches.

Detected dependencies

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

I couldn't find the code where you are loading the variables in the environment, is it automatically done by AWS cli ?