Skip to content

fix: nightly release signature validation#6726

Merged
vitormattos merged 2 commits intomainfrom
fix/nightly-release-signature-validation
Feb 5, 2026
Merged

fix: nightly release signature validation#6726
vitormattos merged 2 commits intomainfrom
fix/nightly-release-signature-validation

Conversation

@vitormattos
Copy link
Member

No description provided.

The occ integrity:sign-app command needs write access to the appinfo
directory to create signature.json. This adds chmod -R a+w after copying
appinfo to ensure the directory is writable regardless of file ownership.

Signed-off-by: Vitor Mattos <1079143+vitormattos@users.noreply.github.com>
The 'Sign app' step was re-signing an already signed tarball created
by the Makefile. This caused signature validation failures on the
Nextcloud Appstore API because:

1. Makefile correctly signs at build/artifacts/sign/libresign
2. Duplicate step extracted, re-signed at wrong path, and recreated tarball
3. This corrupted the original valid signature
4. API rejected with 'invalid padding' or 'bad signature' errors

The Makefile already handles all signing correctly:
- Downloads certificate from GitHub
- Signs setup files with libresign:developer:sign-setup
- Signs app files with occ integrity:sign-app
- Creates properly signed tarball

Removing this redundant step fixes nightly releases not appearing
on apps.nextcloud.com.

Signed-off-by: Vitor Mattos <1079143+vitormattos@users.noreply.github.com>
@vitormattos vitormattos added this to the Next Major (34) milestone Feb 5, 2026
@vitormattos vitormattos self-assigned this Feb 5, 2026
@github-project-automation github-project-automation bot moved this to 0. Needs triage in Roadmap Feb 5, 2026
@vitormattos
Copy link
Member Author

/backport to stable33

@vitormattos
Copy link
Member Author

/backport to stable32

@vitormattos vitormattos merged commit bb7fb08 into main Feb 5, 2026
60 checks passed
@vitormattos vitormattos deleted the fix/nightly-release-signature-validation branch February 5, 2026 16:29
@github-project-automation github-project-automation bot moved this from 0. Needs triage to 4. to release in Roadmap Feb 5, 2026
@backportbot-libresign
Copy link

The backport to stable33 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable33
git pull origin stable33

# Create the new backport branch
git checkout -b backport/6726/stable33

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick 2aec68be dfcabe12

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/6726/stable33

Error: Failed to push branch backport/6726/stable33: fatal: could not read Username for 'https://github.com': No such device or address


Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

@vitormattos
Copy link
Member Author

/backport to stable33

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: 4. to release

Development

Successfully merging this pull request may close these issues.

1 participant