Release failure: invalid header field value for "Authorization" during publish step #293

batyrmuhadov commented 2025年12月21日 00:18:42 +01:00

The build step completes successfully; however, the release step is failing

Error Log

ERR execution failed error="Get \"https://codeberg.org/api/v1/version\": net/http: invalid header field value for \"Authorization\""

Workflow file

publish:image:woodpeckerci/plugin-releasesettings:files:- 'ocean-*.tar.xz'api_key:from_secret:codeberg_tokenwhen:branch:masterevent:tag

**The build step completes successfully; however, the release step is failing** ### **Error Log** `ERR execution failed error="Get \"https://codeberg.org/api/v1/version\": net/http: invalid header field value for \"Authorization\""` ### **Workflow file** ```yaml publish: image: woodpeckerci/plugin-release settings: files: - 'ocean-*.tar.xz' api_key: from_secret: codeberg_token when: branch: master event: tag

Gusted commented 2025年12月21日 01:39:52 +01:00

In which CI pipeline are you seeing this problem?

In which CI pipeline are you seeing this problem?

batyrmuhadov commented 2025年12月21日 15:16:57 +01:00

.woodpecker.yaml

steps:build:image:rust:1.82-bullseyeenvironment:RUST_BACKTRACE:"1"commands:- apt-get update -y && apt-get install -y xz-utils pkg-config libssl-dev- cargo run --package=helix-loader --bin=hx-loader -- fetch- cargo run --package=helix-loader --bin=hx-loader -- build- cargo build --profile opt --locked- mkdir -p dist && cp target/opt/hx dist/ && cp -r runtime dist/- rm -rf dist/runtime/grammars/sources- tar cJf helix-$(date -u +%Y-%m-%d)-x86_64-linux.tar.xz -C dist . - ls -lh helix-*.tar.xzwhen:event:- push- tagpublish:image:woodpeckerci/plugin-releasesettings:files:- 'helix-*.tar.xz'api_key:from_secret:woodpecker_tokendepends_on:- buildwhen:event:tag

### .woodpecker.yaml ```yaml steps: build: image: rust:1.82-bullseye environment: RUST_BACKTRACE: "1" commands: - apt-get update -y && apt-get install -y xz-utils pkg-config libssl-dev - cargo run --package=helix-loader --bin=hx-loader -- fetch - cargo run --package=helix-loader --bin=hx-loader -- build - cargo build --profile opt --locked - mkdir -p dist && cp target/opt/hx dist/ && cp -r runtime dist/ - rm -rf dist/runtime/grammars/sources - tar cJf helix-$(date -u +%Y-%m-%d)-x86_64-linux.tar.xz -C dist . - ls -lh helix-*.tar.xz when: event: - push - tag publish: image: woodpeckerci/plugin-release settings: files: - 'helix-*.tar.xz' api_key: from_secret: woodpecker_token depends_on: - build when: event: tag ```

Gusted commented 2025年12月22日 02:34:17 +01:00

https://ci.codeberg.org/repos/15710/pipeline/52/3 to me it looks like the pipeline was successful? Was the error you saw from locally running this workflow?

https://ci.codeberg.org/repos/15710/pipeline/52/3 to me it looks like the pipeline was successful? Was the error you saw from locally running this workflow?

batyrmuhadov commented 2025年12月22日 09:07:41 +01:00

Yes, as I said build completes, but release fails. https://ci.codeberg.org/repos/15710/pipeline/54/4 And no I don't run it locally.

Yes, as I said build completes, but release fails. https://ci.codeberg.org/repos/15710/pipeline/54/4 And no I don't run it locally.

mahlzahn commented 2025年12月22日 10:33:59 +01:00

Are you sure about your token? Maybe it needs to be token 5273afe22...?

Are you sure about your token? Maybe it needs to be `token 5273afe22...`?

batyrmuhadov commented 2025年12月22日 15:55:49 +01:00

@mahlzahn wrote in #293 (comment):

Are you sure about your token? Maybe it needs to be token 5273afe22...?

I am not sure that's the issue. I initially suspected the token as well and tried updating it, but the problem persists. Or am I doing something wrong?

@mahlzahn wrote in https://codeberg.org/Codeberg-CI/feedback/issues/293#issuecomment-9136866: > Are you sure about your token? Maybe it needs to be `token 5273afe22...`? I am not sure that's the issue. I initially suspected the token as well and tried updating it, but the problem persists. Or am I doing something wrong?

6543 commented 2026年01月11日 00:00:32 +01:00

this code reads the token:

that is used the forgejo client to do stuff:

that is directly passed through to the forgejo sdk

so the plugin itselfe does not conversion/handeling of the token

so i suspect an forgejo sdk bug or forgejo bug

this code reads the token: https://codeberg.org/woodpecker-plugins/release/src/commit/0295fa984c8fe7a1b907b173237bc65a086b95d4/flags.go#L24-L25 that is used the forgejo client to do stuff: https://codeberg.org/woodpecker-plugins/release/src/commit/0295fa984c8fe7a1b907b173237bc65a086b95d4/impl.go#L104 that is directly passed through to the forgejo sdk https://codeberg.org/woodpecker-plugins/release/src/commit/0295fa984c8fe7a1b907b173237bc65a086b95d4/forge/forgejo.go#L29 so the plugin itselfe does not conversion/handeling of the token so i suspect an forgejo sdk bug or forgejo bug

6543 commented 2026年01月11日 00:19:09 +01:00

as per forgejo swagger
image

that's correct so the problem must be the token itselve

https://codeberg.org/mvdkleijn/forgejo-sdk/src/commit/5f3afea2faac9b9b33bc78eebc7a6d1778f6bed2/forgejo/client.go#L113-L120 https://codeberg.org/mvdkleijn/forgejo-sdk/src/commit/5f3afea2faac9b9b33bc78eebc7a6d1778f6bed2/forgejo/client.go#L350-L352 as per forgejo swagger  that's correct so the problem must be the token itselve