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

This repository currently has no open or pending branches.

Detected dependencies

github-actions

.github/workflows/code-style.yaml

• actions/checkout v3
• actions/setup-node v3
• actions/cache v3
• peter-evans/create-pull-request v5

.github/workflows/combine-prs.yaml

• github/combine-prs v3.1.1

.github/workflows/publish-ghpages.yaml

• actions/checkout v3
• actions/setup-node v3
• actions/cache v3

.github/workflows/sync-issue-labels.yaml

• actions/checkout v3

.github/workflows/test-and-release.yaml

• actions/checkout v3
• actions/setup-node v3
• actions/cache v3

.github/workflows/update-repo-info.yaml

• actions/checkout v3

npm

package.json

• @turf/distance 6.5.0
• @nordicsemiconductor/asset-tracker-cloud-code-style 12.0.60
• @prefresh/snowpack 3.2.0
• @snowpack/plugin-babel 2.1.7
• @snowpack/plugin-react-refresh 2.5.0
• @snowpack/plugin-sass 1.4.0
• @snowpack/plugin-typescript 1.2.1
• @swc/jest *
• @types/jest 29.5.3
• @types/leaflet 1.9.3
• @types/node 18.16.19
• @types/react 18.2.15
• @types/react-dom 18.2.7
• @types/snowpack-env 2.3.4
• @types/styled-components 5.1.26
• jest 29.6.1
• leaflet 1.9.4
• nmea-simple 3.3.0
• normalize.css 8.0.1
• react 18.2.0
• react-dom 18.2.0
• snowpack 3.8.8
• source-map-loader 4.0.1
• styled-components 6.0.4
• node >=18
• npm >=9

---

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

🚨 The automated release from the saga 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 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 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.

---

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two Factor Authentication for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization and writes" level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀