mob-sakai / unity.package-manager.metadata

Contains metadata used by the com.unity.package-manager package to fulfill client requests
MIT License
24 stars 1 forks source link

The automated release is failing 🚨 #2

Closed mob-sakai closed 4 years ago

mob-sakai commented 4 years ago

:rotating_light: The automated release from the master branch failed. :rotating_light:

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:

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.


The analyzeCommits plugin returned an invalid value. It must return a valid semver release type.

The analyzeCommits plugin must return a valid semver release type. The valid values are: patch, minor, major.

The analyzeCommits function of the @semantic-release/exec returned `diff --git a/package.json b/package.json index 9f5c04c..16dbfd3 100644 --- a/package.json +++ b/package.json @@ -15,5 +15,219 @@ "update": "semantic-release", "update:local": "semantic-release --no-ci", "update:debug": "semantic-release --no-ci --dry-run --debug"

We recommend to report the issue to the @semantic-release/exec authors, providing the following informations:


Good luck with your project ✨

Your semantic-release bot :package::rocket:

mob-sakai commented 4 years ago

:rotating_light: The automated release from the master branch failed. :rotating_light:

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:

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.


The analyzeCommits plugin returned an invalid value. It must return a valid semver release type.

The analyzeCommits plugin must return a valid semver release type. The valid values are: patch, minor, major.

The analyzeCommits function of the @semantic-release/exec returned `diff --git a/package.json b/package.json index 9f5c04c..16dbfd3 100644 --- a/package.json +++ b/package.json @@ -15,5 +15,219 @@ "update": "semantic-release", "update:local": "semantic-release --no-ci", "update:debug": "semantic-release --no-ci --dry-run --debug"

We recommend to report the issue to the @semantic-release/exec authors, providing the following informations:


Good luck with your project ✨

Your semantic-release bot :package::rocket:

mob-sakai commented 4 years ago

:rotating_light: The automated release from the master branch failed. :rotating_light:

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:

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.


The analyzeCommits plugin returned an invalid value. It must return a valid semver release type.

The analyzeCommits plugin must return a valid semver release type. The valid values are: patch, minor, major.

The analyzeCommits function of the @semantic-release/exec returned `diff --git a/package.json b/package.json index 9f5c04c..16dbfd3 100644 --- a/package.json +++ b/package.json @@ -15,5 +15,219 @@ "update": "semantic-release", "update:local": "semantic-release --no-ci", "update:debug": "semantic-release --no-ci --dry-run --debug"

We recommend to report the issue to the @semantic-release/exec authors, providing the following informations:


Good luck with your project ✨

Your semantic-release bot :package::rocket:

mob-sakai commented 4 years ago

:rotating_light: The automated release from the master branch failed. :rotating_light:

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:

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.


The analyzeCommits plugin returned an invalid value. It must return a valid semver release type.

The analyzeCommits plugin must return a valid semver release type. The valid values are: patch, minor, major.

The analyzeCommits function of the @semantic-release/exec returned `diff --git a/package.json b/package.json index 9f5c04c..16dbfd3 100644 --- a/package.json +++ b/package.json @@ -15,5 +15,219 @@ "update": "semantic-release", "update:local": "semantic-release --no-ci", "update:debug": "semantic-release --no-ci --dry-run --debug"

We recommend to report the issue to the @semantic-release/exec authors, providing the following informations:


Good luck with your project ✨

Your semantic-release bot :package::rocket:

mob-sakai commented 4 years ago

:rotating_light: The automated release from the master branch failed. :rotating_light:

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:

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.


The analyzeCommits plugin returned an invalid value. It must return a valid semver release type.

The analyzeCommits plugin must return a valid semver release type. The valid values are: patch, minor, major.

The analyzeCommits function of the @semantic-release/exec returned `diff --git a/package.json b/package.json index 9f5c04c..16dbfd3 100644 --- a/package.json +++ b/package.json @@ -15,5 +15,219 @@ "update": "semantic-release", "update:local": "semantic-release --no-ci", "update:debug": "semantic-release --no-ci --dry-run --debug"

We recommend to report the issue to the @semantic-release/exec authors, providing the following informations:


Good luck with your project ✨

Your semantic-release bot :package::rocket:

mob-sakai commented 4 years ago

:rotating_light: The automated release from the master branch failed. :rotating_light:

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:

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.


The analyzeCommits plugin returned an invalid value. It must return a valid semver release type.

The analyzeCommits plugin must return a valid semver release type. The valid values are: patch, minor, major.

The analyzeCommits function of the @semantic-release/exec returned `diff --git a/package.json b/package.json index 9f5c04c..16dbfd3 100644 --- a/package.json +++ b/package.json @@ -15,5 +15,219 @@ "update": "semantic-release", "update:local": "semantic-release --no-ci", "update:debug": "semantic-release --no-ci --dry-run --debug"

We recommend to report the issue to the @semantic-release/exec authors, providing the following informations:


Good luck with your project ✨

Your semantic-release bot :package::rocket:

mob-sakai commented 4 years ago

:rotating_light: The automated release from the master branch failed. :rotating_light:

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:

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.


The analyzeCommits plugin returned an invalid value. It must return a valid semver release type.

The analyzeCommits plugin must return a valid semver release type. The valid values are: patch, minor, major.

The analyzeCommits function of the @semantic-release/exec returned `diff --git a/package.json b/package.json index 27b8847..bd43660 100644 --- a/package.json +++ b/package.json @@ -17,8 +17,84 @@ "update:debug": "semantic-release --no-ci --dry-run --debug" }, "searchablePackages": [

We recommend to report the issue to the @semantic-release/exec authors, providing the following informations:


Good luck with your project ✨

Your semantic-release bot :package::rocket:

mob-sakai commented 4 years ago

:rotating_light: The automated release from the master branch failed. :rotating_light:

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:

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.


The analyzeCommits plugin returned an invalid value. It must return a valid semver release type.

The analyzeCommits plugin must return a valid semver release type. The valid values are: patch, minor, major.

The analyzeCommits function of the @semantic-release/exec returned `diff --git a/package.json b/package.json index 27b8847..bd43660 100644 --- a/package.json +++ b/package.json @@ -17,8 +17,84 @@ "update:debug": "semantic-release --no-ci --dry-run --debug" }, "searchablePackages": [

We recommend to report the issue to the @semantic-release/exec authors, providing the following informations:


Good luck with your project ✨

Your semantic-release bot :package::rocket: