-
Notifications
You must be signed in to change notification settings - Fork 256
An error occurred in the workflow #1074
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@michaelbennn, that error is trying to let you know that there is an error in your configuration specifically in the remote configuration section. Can you fill out the bug template with your configuration at least? The boilerplate is supposed to help me determine the issue and provide a solution. The specific error is detecting that you have configured a HTTP URL of some kind and have not set the |
Also don't point at the master branch, always point at a specific tag when defining an action. If I introduced breaking changes or even just had master branch in a broken state, you would have a broken pipeline. |
This issue has not received a response in 14 days. If no response is received in 7 days, it will be closed. We look forward to hearing from you. |
This issue was closed because no response was received. |
… insecure URL error Due to the previous default token loading, PSR configuration load would initate the default RemoteConfig. During validation of the remote config, the HVCS object was initialized and upon initialization the URL is evaluated for insecure protocol causing errors when the URL was pulled from the env. This change removes the need for initialization which means the URL validation will not occur pre-maturely Resolves: python-semantic-release#1169, python-semantic-release#1074
… insecure URL error (#1173) Due to the previous default token loading, PSR configuration load would initate the default RemoteConfig. During validation of the remote config, the HVCS object was initialized and upon initialization the URL is evaluated for insecure protocol causing errors when the URL was pulled from the env. This change removes the need for initialization which means the URL validation will not occur pre-maturely Resolves: #1169, #1074
🎉 This issue has been resolved in Version 9.18.1 🎉You can find more information about this release on the GitHub Releases page. |
Bug Report
Description
I am going to use python-semantic-release to perform CICD operations in gitea action, but it reports an error and it keeps this error
this is workflow.

Expected behavior
Actual behavior
Environment
pip freeze
git log --oneline --decorate --graph --all -n 50
Configuration
Semantic Release Configuration
Build System Configuration
GitHub Actions Job Definition
Execution Log
semantic-release -vv command
Additional context
The text was updated successfully, but these errors were encountered: