Skip to content

chore: release 0.7.2 - #407

Open
oc-tmueller wants to merge 1 commit into
masterfrom
release/v0.7.2
Open

chore: release 0.7.2#407
oc-tmueller wants to merge 1 commit into
masterfrom
release/v0.7.2

Conversation

@oc-tmueller

Copy link
Copy Markdown

Repackaging release, part of the remediation for owncloud/core#41824.

Why

The notifications asset published for the previous version was uploaded from the build working tree rather than from build/artifacts/appstore/notifications.tar.gz. It therefore shipped .git/, .github/, tests/, vendor-bin/ and build/artifacts/ as part of the signed app.

Because those files are covered by appinfo/signature.json, an administrator cannot delete them without breaking occ integrity:check-app — so the only fix is a new release built by CI.

What this does

Bumps appinfo/info.xml to 0.7.2 and adds the changelog entry. No functional change.

Tagging v0.7.2 lets .github/workflows/release.yml publish the packaged artifact. That workflow now also asserts the tarball is free of development files (owncloud/reusable-workflows#97), so this class of problem cannot recur silently.

Merging

The release.yml workflow asserts the tag matches appinfo/info.xml, so merge this before pushing v0.7.2.

Once published, the new tag gets repinned in the ownCloud 11.0.1 bundle specs.

🤖 Generated with Claude Code

Repackaging release. The notifications asset published for the previous version
was uploaded from the build working tree rather than from
build/artifacts/appstore/notifications.tar.gz, so it shipped .git/, .github/,
tests/, vendor-bin/ and build/artifacts/ as part of the signed app.

Tagging v0.7.2 lets the automated release workflow publish the packaged
artifact, which now also asserts that the tarball carries no development
files. No functional change.

Refs: owncloud/core#41824

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@oc-tmueller
oc-tmueller requested a review from a team as a code owner September 9, 2026 13:03
@CLAassistant

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants