marc/packwatch
Archived
1
0
Fork 0
Code Issues 5 Pull requests 10 Projects Releases 2 Packages Wiki Activity

The automated release is failing 🚨 #3

New issue
Closed
opened 2020-03-01 00:42:56 +00:00 by mcataford · 2 comments
mcataford commented 2020-03-01 00:42:56 +00:00 (Migrated from github.com)
Copy link

🚨 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:

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:%20433f9e03a41f98e051ed773dca2e4ffd27f425c5@github.com/mcataford/packwatch.git.

This can be caused by:

Good luck with your project ✨

Your semantic-release bot 📦🚀

## :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: - [Usage documentation](https://github.com/semantic-release/semantic-release/blob/caribou/docs/usage/README.md) - [Frequently Asked Questions](https://github.com/semantic-release/semantic-release/blob/caribou/docs/support/FAQ.md) - [Support channels](https://github.com/semantic-release/semantic-release#get-help) 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](https://github.com/semantic-release/semantic-release/issues/new)**. --- ### 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:%20433f9e03a41f98e051ed773dca2e4ffd27f425c5@github.com/mcataford/packwatch.git`. This can be caused by: - a misconfiguration of the [repositoryUrl](https://github.com/semantic-release/semantic-release/blob/master/docs/usage/configuration.md#repositoryurl) option - the repository being unavailable - or missing push permission for the user configured via the [Git credentials on your CI environment](https://github.com/semantic-release/semantic-release/blob/master/docs/usage/ci-configuration.md#authentication) --- Good luck with your project ✨ Your **[semantic-release](https://github.com/semantic-release/semantic-release)** bot :package::rocket: <!-- semantic-release:github -->
mcataford commented 2020-03-01 00:51:07 +00:00 (Migrated from github.com)
Copy link

🚨 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:

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://%20433f9e03a41f98e051ed773dca2e4ffd27f425c5@github.com/mcataford/packwatch.git.

This can be caused by:

Good luck with your project ✨

Your semantic-release bot 📦🚀

## :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: - [Usage documentation](https://github.com/semantic-release/semantic-release/blob/caribou/docs/usage/README.md) - [Frequently Asked Questions](https://github.com/semantic-release/semantic-release/blob/caribou/docs/support/FAQ.md) - [Support channels](https://github.com/semantic-release/semantic-release#get-help) 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](https://github.com/semantic-release/semantic-release/issues/new)**. --- ### 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://%20433f9e03a41f98e051ed773dca2e4ffd27f425c5@github.com/mcataford/packwatch.git`. This can be caused by: - a misconfiguration of the [repositoryUrl](https://github.com/semantic-release/semantic-release/blob/master/docs/usage/configuration.md#repositoryurl) option - the repository being unavailable - or missing push permission for the user configured via the [Git credentials on your CI environment](https://github.com/semantic-release/semantic-release/blob/master/docs/usage/ci-configuration.md#authentication) --- Good luck with your project ✨ Your **[semantic-release](https://github.com/semantic-release/semantic-release)** bot :package::rocket:
mcataford commented 2020-03-01 00:58:07 +00:00 (Migrated from github.com)
Copy link

🚨 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:

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:%20433f9e03a41f98e051ed773dca2e4ffd27f425c5@github.com/mcataford/packwatch.git.

This can be caused by:

Good luck with your project ✨

Your semantic-release bot 📦🚀

## :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: - [Usage documentation](https://github.com/semantic-release/semantic-release/blob/caribou/docs/usage/README.md) - [Frequently Asked Questions](https://github.com/semantic-release/semantic-release/blob/caribou/docs/support/FAQ.md) - [Support channels](https://github.com/semantic-release/semantic-release#get-help) 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](https://github.com/semantic-release/semantic-release/issues/new)**. --- ### 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:%20433f9e03a41f98e051ed773dca2e4ffd27f425c5@github.com/mcataford/packwatch.git`. This can be caused by: - a misconfiguration of the [repositoryUrl](https://github.com/semantic-release/semantic-release/blob/master/docs/usage/configuration.md#repositoryurl) option - the repository being unavailable - or missing push permission for the user configured via the [Git credentials on your CI environment](https://github.com/semantic-release/semantic-release/blob/master/docs/usage/ci-configuration.md#authentication) --- Good luck with your project ✨ Your **[semantic-release](https://github.com/semantic-release/semantic-release)** bot :package::rocket:
This repo is archived. You cannot comment on issues.
No Branch/Tag specified
Branches Tags
main
renovate/node-18.x-lockfile
renovate/node-20.x
renovate/node-18.x
renovate/rome-replacement
renovate/jest-monorepo
renovate/ts-jest-29.x-lockfile
renovate/actions-setup-node-4.x
renovate/actions-checkout-4.x
renovate/rome-12.x-lockfile
renovate/typescript-5.x
v2.0.0
v1.0.0
Labels
Clear labels   
bug

Something isn't working

  
dependencies

Pull requests that update a dependency file

  
documentation

Improvements or additions to documentation

  
duplicate

This issue or pull request already exists

  
enhancement

New feature or request

  
good first issue

Good for newcomers

  
help wanted

Extra attention is needed

  
Idea

   
invalid

This doesn't seem right

  
question

Further information is requested

  
released

   
security

Pull requests that address a security vulnerability

  
semantic-release

   
wontfix

This will not be worked on

No labels
bug
dependencies
documentation
duplicate
enhancement
good first issue
help wanted
Idea
invalid
question
released
security
semantic-release
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: marc/packwatch#3
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?