- Bugfix - Feature - Code style update (formatting, renaming) - Refactoring (no functional changes, no api changes) - Build related changes - Documentation content changes by ashcoft · Pull Request #168 · LibreCodeCoop/extract

ashcoft · 2026-10-31T04:57:34Z

Pull Request Description

Related Issue

Issue Number:

Pull Request Type

Pull request checklist

Did you explain or provide a way of how can we test your code ?
If your pull request is related to frontend modifications provide a print of before and after screen
Did you provide a general summary of your changes ?
Try to limit your pull request to one type, submit multiple pull requests if needed

- Updated appinfo/info.xml with Nextcloud 33 support (min-version 30). - Replaced internal OC\Files\Filesystem::isFileBlacklisted with OCP\Files\IFilenameValidator. - Fixed vite.config.js to correctly target src/main.ts. - Updated @nextcloud npm dependencies to latest compatible versions. - Verified frontend build and PHP linting. Co-authored-by: ashcoft <1115854+ashcoft@users.noreply.github.com>

…861883122648452809 Nextcloud 33 Compatibility Update for Extract App

- Update max-version to 34 in info.xml - Bump version to 3.1.0 - Update CHANGELOG.md Co-authored-by: openhands <openhands@all-hands.dev>

feat: Add NC33+ support

Update translations from Transifex

…dates Bumps the npm_and_yarn group with 6 updates in the / directory: | Package | From | To | | --- | --- | --- | | [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) | `7.1.5` | `7.3.5` | | [dompurify](https://github.com/cure53/DOMPurify) | `3.4.5` | `3.4.12` | | [form-data](https://github.com/form-data/form-data) | `4.0.5` | `4.0.6` | | [js-yaml](https://github.com/nodeca/js-yaml) | `4.1.1` | `4.3.0` | | [qs](https://github.com/ljharb/qs) | `6.14.0` | `6.15.3` | | [rollup](https://github.com/rollup/rollup) | `4.50.0` | `4.62.2` | Updates `vite` from 7.1.5 to 7.3.5 - [Release notes](https://github.com/vitejs/vite/releases) - [Changelog](https://github.com/vitejs/vite/blob/v7.3.5/packages/vite/CHANGELOG.md) - [Commits](https://github.com/vitejs/vite/commits/v7.3.5/packages/vite) Updates `dompurify` from 3.4.5 to 3.4.12 - [Release notes](https://github.com/cure53/DOMPurify/releases) - [Commits](cure53/DOMPurify@3.4.5...3.4.12) Updates `form-data` from 4.0.5 to 4.0.6 - [Changelog](https://github.com/form-data/form-data/blob/master/CHANGELOG.md) - [Commits](form-data/form-data@v4.0.5...v4.0.6) Updates `js-yaml` from 4.1.1 to 4.3.0 - [Changelog](https://github.com/nodeca/js-yaml/blob/master/CHANGELOG.md) - [Commits](nodeca/js-yaml@4.1.1...4.3.0) Updates `qs` from 6.14.0 to 6.15.3 - [Changelog](https://github.com/ljharb/qs/blob/main/CHANGELOG.md) - [Commits](ljharb/qs@v6.14.0...v6.15.3) Updates `rollup` from 4.50.0 to 4.62.2 - [Release notes](https://github.com/rollup/rollup/releases) - [Changelog](https://github.com/rollup/rollup/blob/master/CHANGELOG.md) - [Commits](rollup/rollup@v4.50.0...v4.62.2) --- updated-dependencies: - dependency-name: vite dependency-version: 7.3.5 dependency-type: direct:development dependency-group: npm_and_yarn - dependency-name: dompurify dependency-version: 3.4.12 dependency-type: indirect dependency-group: npm_and_yarn - dependency-name: form-data dependency-version: 4.0.6 dependency-type: indirect dependency-group: npm_and_yarn - dependency-name: js-yaml dependency-version: 4.3.0 dependency-type: indirect dependency-group: npm_and_yarn - dependency-name: qs dependency-version: 6.15.3 dependency-type: indirect dependency-group: npm_and_yarn - dependency-name: rollup dependency-version: 4.62.2 dependency-type: indirect dependency-group: npm_and_yarn ... Signed-off-by: dependabot[bot] <support@github.com>

…sues Vite 7.3.5 with esbuild 0.27 cannot transform destructuring patterns for older browser targets (Chrome 109, Edge 109, iOS 11). This commit excludes these older browsers from the browserslist to fix the build failure in CI. Co-authored-by: openhands <openhands@all-hands.dev>

…rn-6ef150ff13 chore(deps): Bump the npm_and_yarn group across 1 directory with 6 updates

Bumps the npm_and_yarn group with 1 update in the / directory: [fast-uri](https://github.com/fastify/fast-uri). Updates `fast-uri` from 3.1.0 to 3.1.3 - [Release notes](https://github.com/fastify/fast-uri/releases) - [Commits](fastify/fast-uri@v3.1.0...v3.1.3) --- updated-dependencies: - dependency-name: fast-uri dependency-version: 3.1.3 dependency-type: indirect dependency-group: npm_and_yarn ... Signed-off-by: dependabot[bot] <support@github.com>

…rn-85f100c75a chore(deps-dev): Bump fast-uri from 3.1.0 to 3.1.3 in the npm_and_yarn group across 1 directory

The @nextcloud/vite-config v2 requires vite ^7.1.4, but the merged PR updated vite to ^8.1.4 causing a peer dependency conflict. Updated @nextcloud/vite-config to ^3.0.0-beta.0 which supports vite v8. Co-authored-by: openhands <openhands@all-hands.dev>

fix: update @nextcloud/vite-config to v3 beta to support vite v8

- Update @nextcloud/eslint-config from 9.0.0-rc.5 to 9.0.1 (stable) - Update @nextcloud/stylelint-config from 3.1.0 to 3.2.2 - Update @nextcloud/browserslist-config from 3.0.1 to 3.1.2 - Update openapi-typescript from 7.9.1 to 7.13.0 - Update Node.js requirement to support ^20 || ^22 || ^24 - Update info.xml max-version to 35 for Nextcloud 35 support Co-authored-by: openhands <openhands@all-hands.dev>

- Change Nextcloud support from 30-35 to 33-34 - Change Node.js requirement to ^24 only - Update npm requirement to support npm 10 or 11 Co-authored-by: openhands <openhands@all-hands.dev>

- Update @nextcloud/eslint-config to 9.0.1 - Update @nextcloud/stylelint-config to 3.2.2 - Update @nextcloud/browserslist-config to 3.1.2 - Update openapi-typescript to 7.13.0 - Change Node.js requirement to ^24 - Change Nextcloud support to 33-34 - Update phpVersion in psalm.xml to 8.4 - Fix CI workflow to allow phpVersion >= minimum Co-authored-by: openhands <openhands@all-hands.dev>

chore: NC 33-34 and Node 24+ support

- Add .releaserc configuration for semantic versioning - Add GitHub Actions workflow to trigger releases on main branch - Workflow builds the Nextcloud app and attaches to GitHub release Co-authored-by: openhands <openhands@all-hands.dev>

Co-authored-by: openhands <openhands@all-hands.dev>

feat: add semantic-release workflow for auto releases

fix(l10n): Update translations from Transifex

The 4 upstream commits (npm-audit-fix and sync-workflow-templates changes) were already applied to main by content in #39, but they were applied as new commits rather than by merging upstream's history. GitHub's compare view therefore still reported main as "behind by 4", because it measures commit ancestry, not content. This merges upstream/main into main. The merge introduces no file changes: the tree is byte-identical before and after, which is why git resolved it without conflicts. It exists purely so upstream/main becomes an ancestor of main and the compare reads as up to date. No content from this repository is altered. In particular the action-version pins that Dependabot raised here (for example create-github-app-token v3.3.0 over upstream's v3.2.0) are preserved, since the merge takes no content from either side. Co-authored-by: openhands <openhands@all-hands.dev>

chore(sync): merge upstream LibreCodeCoop/main to close the ancestry gap

## [3.1.2](v3.1.1...v3.1.2) (2026-10-29) ### Bug Fixes * **ci:** adopt secured LibreCode npm audit workflow ([2c9e0ea](2c9e0ea)) * **ci:** exclude EOL Nextcloud branches from npm audit ([62cd386](62cd386))

The v3.1.2 release failed, so the tag exists but the release has no archives: @semantic-release/github -> Failed step "success" RequestError [HttpError]: Not Found GET https://api.github.com/repos/ashcoft/extract/pulls/165/commits The success step resolves each released commit to a pull request and fails the whole release with a 404 when a number cannot be resolved. Merging LibreCodeCoop/extract's history brought in commits whose messages reference pull requests that exist only upstream, for example: Merge pull request LibreCodeCoop#165 from LibreCodeCoop/fix/manage-npm-audit-through-librcode-catalog PR LibreCodeCoop#165 does not exist in this repository, so the lookup 404s. That commit is now permanently part of main, so every future release would fail the same way. Disable the comment and label side of the success step: - `successCommentCondition: false` skips the block that performs the PR lookup. The condition form is used rather than `successComment: false`, which the plugin logs as deprecated. - `releasedLabels: false` stops the step trying to label those same PRs. Nothing is lost here: the app is not published to npm and no issue or PR subscribers depend on release comments. Co-authored-by: openhands <openhands@all-hands.dev>

"Encryption is not supported yet" was shown for every user as soon as any encryption module was enabled on the instance, even for archives that were not encrypted. The check consulted the server-wide flag: if ($this->encryptionManager->isEnabled()) { ...refuse... } That flag only reports whether an encryption module is *available*, not whether the file being extracted is encrypted, so it blocked a valid use case. Extraction works with server-side encryption. The archive is read through Storage::getLocalFile(), and the encryption storage wrapper serves that from a decrypted temporary file: getLocalFile() calls getCachedFile(), which calls toTmpFile(), which copies through fopen(). fopen() goes through the wrapper's decryption path, so the bytes handed to 7za or ZipArchive are already plaintext. Nothing in the extraction path needs to change. Remove the refusal, the now-unused OCP\Encryption\IManager constructor dependency and its import, and add a test asserting the refusal cannot return. Update the README and appinfo/info.xml, which both advertised the old limitation. Password-protected archives remain unsupported; that is a separate limitation and is still documented. Co-authored-by: openhands <openhands@all-hands.dev>

fix(release): stop the release failing on upstream pull request numbers

## [3.1.3](v3.1.2...v3.1.3) (2026-10-30) ### Bug Fixes * **release:** stop the release failing on upstream pull request numbers ([3876977](3876977)), closes [LibreCodeCoop#165](https://github.com/ashcoft/extract/issues/165) [LibreCodeCoop/fix/manage-npm-audit-throu#librcode-catalog](https://github.com/LibreCodeCoop/fix/manage-npm-audit-throu/issues/librcode-catalog) [LibreCodeCoop#165](https://github.com/ashcoft/extract/issues/165)

Follow-up to the previous commit, which removed the encryption refusal. Two review findings, both confirmed. cubic P1: removing the refusal made a broken path reachable. The destination is derived from the archive's local path: $dir = dirname($file); $extractTo = $dir . '/' . $fileName; and postExtract() then expects Nextcloud to see the result there. That holds for plain local storage, where getLocalFile() returns the file inside the data directory. It does not hold with server-side encryption enabled or on object storage: Encryption::getLocalFile() falls through to LocalTempFileTrait::getCachedFile(), so the path is a TempManager file, $dir becomes /tmp, and nothing is published. The user would get a success and no folder. Guard on Storage::isLocal() instead. That is the actual precondition: false both when encryption is enabled (Wrapper\Encryption::isLocal() returns false) and for object storage (Common::isLocal() documents "the common implementation returns a temporary file by default"). The old encryption check missed object storage entirely. sourcery and cubic: the PHP rar path ignored $entry->extract() and returned success, so a password-protected or damaged entry produced a partial result reported as complete. It now fails the extraction and logs the entry. Replace the source-text regression test with behavioural tests that drive execute(): one asserts a non-local storage is refused before the service is reached, the other that local storage passes the guard and reaches extraction. tests/stubs/oc_hooks_emitter.php declared Emitter as a class, but the real type is an interface, so the OCP interfaces could not be loaded outside a full Nextcloud checkout. Corrected to an interface and loaded from the bootstrap. Co-authored-by: openhands <openhands@all-hands.dev>

Codacy's comparison-operator check flags the bare boolean in the new storage ternary. Compare explicitly, matching the style used elsewhere in this file. Co-authored-by: openhands <openhands@all-hands.dev>

fix(extraction): allow extraction when server-side encryption is enabled

## [3.1.4](v3.1.3...v3.1.4) (2026-10-30) ### Bug Fixes * **extraction:** allow extraction when server-side encryption is enabled ([6924cc0](6924cc0)) * **extraction:** guard on local storage, and propagate rar failures ([df4d49b](df4d49b))

…orage "Extraction is only supported on local storage" was shown for every archive on object storage (S3, Swift, ...) and whenever server-side encryption was enabled. The guard added in df4d49b was correct about the symptom but refused the request instead of fixing it. The cause is that the extraction unpacks the archive next to the original file and then relies on Nextcloud seeing the result in the data directory. That only holds on real local storage, because getLocalFile() then returns a path inside the data directory. On object storage, or with the encryption storage wrapper, getLocalFile() returns a temporary copy instead (Encryption::getLocalFile() falls through to LocalTempFileTrait::getCachedFile(), and Common::isLocal() documents that "the common implementation returns a temporary file by default"). The destination then resolves to something like /tmp and nothing is published. Keep the local fast path, and add the import step the old code only documented: when the destination storage is not local, unpack into a request-owned temporary directory (ITempManager) and recreate the tree through the Nextcloud files API. Creating each folder and writing each file with Folder::newFile() produces the files-cache entries and write hooks as part of the copy, so the result is published without a storage scan. The temporary directory is removed after the request, and a failure while publishing is reported as a normal extraction failure instead of a success the user cannot see. While extracting the forbidden-name cleanup into its own method, fix the walk that visited `.` and `..`: the filename validator rejects those, so unlink() was called on a directory for every folder in the archive. Co-authored-by: openhands <openhands@all-hands.dev>

## [3.1.5](v3.1.4...v3.1.5) (2026-10-30) ### Bug Fixes * **extraction:** import the result on object storage and encrypted storage ([4048efb](4048efb))

fix(l10n): Update translations from Transifex

## [3.1.6](v3.1.5...v3.1.6) (2026-10-31) ### Bug Fixes * **l10n:** Update translations from Transifex ([f92d702](f92d702))

Add repository instructions that every change goes through a pull request and that nothing may be pushed directly to main. A direct push to main triggers the automated Release workflow, which publishes a release with no review step. Co-authored-by: openhands <openhands@all-hands.dev>

The reuse-compliance-check job failed because AGENTS.md carried no copyright or licence information. Add the standard SPDX comment block used by the other Markdown files. Also act on the review feedback: - Qualify the release warning. release.config.cjs marks maintenance commits (chore, docs, ci, refactor, style, test, build, revert) as no-release and the workflow is skipped when the head commit contains `skip release`, so not every direct push publishes a release. The rule stands because such a push still lands on main without review. - Document the `zlib` requirement: WrappedTarballExtractionTest builds its gzip fixtures with Phar::GZ, which needs zlib. - Say "PHP 8.1 through 8.x" to match the `^8.1` constraint in composer.json. - Note the REUSE requirement so a new file is not left without headers again. Co-authored-by: openhands <openhands@all-hands.dev>

docs: record the pull-request-only workflow in AGENTS.md

chatgpt-codex-connector · 2026-10-31T04:57:48Z

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	⚠️ Failed 2026-10-31T04:58:51.021910Z We couldn’t complete this review. Comment `@codex review` to try again.	`0a7eb3c`	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

Bumps [follow-redirects](https://github.com/follow-redirects/follow-redirects) from 1.16.1 to 1.16.2. - [Release notes](https://github.com/follow-redirects/follow-redirects/releases) - [Commits](follow-redirects/follow-redirects@v1.16.1...v1.16.2) --- updated-dependencies: - dependency-name: follow-redirects dependency-version: 1.16.2 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>

…directs-1.16.2 chore(deps): Bump follow-redirects from 1.16.1 to 1.16.2

Bumps [fsfe/reuse-action](https://github.com/fsfe/reuse-action) from 5.0.0 to 6.0.0. - [Release notes](https://github.com/fsfe/reuse-action/releases) - [Commits](fsfe/reuse-action@bb774aa...676e2d5) --- updated-dependencies: - dependency-name: fsfe/reuse-action dependency-version: 6.0.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>

Bumps [skjnldsv/read-package-engines-version-actions](https://github.com/skjnldsv/read-package-engines-version-actions) from 3 to 4. - [Release notes](https://github.com/skjnldsv/read-package-engines-version-actions/releases) - [Commits](skjnldsv/read-package-engines-version-actions@v3...06d6db4) --- updated-dependencies: - dependency-name: skjnldsv/read-package-engines-version-actions dependency-version: '4' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>

Bumps [fsfe/reuse-action](https://github.com/fsfe/reuse-action) from 5.0.0 to 6.0.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/fsfe/reuse-action/releases">fsfe/reuse-action's releases</a>.</em></p> <blockquote> <h2>v6.0.0</h2> <ul> <li>Bump to v6 #(43)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/fsfe/reuse-action/commit/676e2d560c9a403aa252096d99fcab3e1132b0f5"><code>676e2d5</code></a> Bump to reuse v6</li> <li>See full diff in <a href="https://github.com/fsfe/reuse-action/compare/bb774aa972c2a89ff34781233d275075cbddf542...676e2d560c9a403aa252096d99fcab3e1132b0f5">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=fsfe/reuse-action&package-manager=github_actions&previous-version=5.0.0&new-version=6.0.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details>  --- ## Summary by cubic Updates the `fsfe/reuse-action` GitHub Action from v5.0.0 to v6.0.0 in the REUSE compliance check workflow. - This is a major version bump, so the REUSE compliance check may behave differently. <sup>Written for commit e76321c. Summary will update on new commits.</sup> <a href="https://cubic.dev/pr/ashcoft/extract/pull/64?utm_source=github" target="_blank" rel="noopener noreferrer" data-no-image-dialog="true"><picture><source media="(prefers-color-scheme: dark)" srcset="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"><source media="(prefers-color-scheme: light)" srcset="https://www.cubic.dev/buttons/review-in-cubic-light.svg"><img alt="View guided diff" src="https://www.cubic.dev/buttons/review-in-cubic-light.svg"></picture></a>

@V3

google-labs-jules Bot and others added 30 commits May 19, 2026 01:44

Merge pull request #1 from ashcoft/jules-nc33-compatibility-update-15…

e0776ef

…861883122648452809 Nextcloud 33 Compatibility Update for Extract App

Merge branch 'LibreCodeCoop:main' into main

f3591e2

feat: add NC33+ support

40a2a4e

- Update max-version to 34 in info.xml - Bump version to 3.1.0 - Update CHANGELOG.md Co-authored-by: openhands <openhands@all-hands.dev>

Merge pull request #2 from ashcoft/feature/nc33-plus-support

fe347d6

feat: Add NC33+ support

Merge pull request #3 from LibreCodeCoop/main

e554518

Update translations from Transifex

Merge pull request #8 from ashcoft/dependabot/npm_and_yarn/npm_and_ya…

6302d4c

…rn-6ef150ff13 chore(deps): Bump the npm_and_yarn group across 1 directory with 6 updates

Merge pull request #9 from ashcoft/dependabot/npm_and_yarn/npm_and_ya…

83d62e5

…rn-85f100c75a chore(deps-dev): Bump fast-uri from 3.1.0 to 3.1.3 in the npm_and_yarn group across 1 directory

Merge pull request #10 from ashcoft/fix/vite-config-v3

6e8ae06

fix: update @nextcloud/vite-config to v3 beta to support vite v8

chore: target NC 33-34 and Node 24+ only

9366b4e

- Change Nextcloud support from 30-35 to 33-34 - Change Node.js requirement to ^24 only - Update npm requirement to support npm 10 or 11 Co-authored-by: openhands <openhands@all-hands.dev>

Merge pull request #12 from ashcoft/feature/nc34-plus-support

5003879

chore: NC 33-34 and Node 24+ support

Merge branch 'feature/nc34-plus-support'

f4becb2

fix: simplify releaserc config

79d7626

Co-authored-by: openhands <openhands@all-hands.dev>

fix: build app before semantic-release in workflow

d143d37

Co-authored-by: openhands <openhands@all-hands.dev>

Merge branch 'feature/nc34-plus-support'

8c4a0d2

chore: remove release workflow temporarily

1d6c870

feat: add semantic-release workflow for auto releases

76778ae

fix: add REUSE annotations for new files

187a89d

Co-authored-by: openhands <openhands@all-hands.dev>

Merge pull request #14 from ashcoft/feature/add-release-workflow

0570379

feat: add semantic-release workflow for auto releases

Merge pull request #16 from LibreCodeCoop/main

e6888e2

fix(l10n): Update translations from Transifex

aviator-app Bot and others added 23 commits October 28, 2026 13:58

Merge pull request #56 from ashcoft/sync/upstream-main-ancestry

71dd146

chore(sync): merge upstream LibreCodeCoop/main to close the ancestry gap

chore(release): 3.1.2 [skip ci]

b0be329

## [3.1.2](v3.1.1...v3.1.2) (2026-10-29) ### Bug Fixes * **ci:** adopt secured LibreCode npm audit workflow ([2c9e0ea](2c9e0ea)) * **ci:** exclude EOL Nextcloud branches from npm audit ([62cd386](62cd386))

Merge pull request #57 from ashcoft/fix/release-upstream-pr-reference

fb8dc90

fix(release): stop the release failing on upstream pull request numbers

style: compare the external flag explicitly for Codacy

b4b0d60

Codacy's comparison-operator check flags the bare boolean in the new storage ternary. Compare explicitly, matching the style used elsewhere in this file. Co-authored-by: openhands <openhands@all-hands.dev>

Merge pull request #58 from ashcoft/fix/allow-extraction-with-encryption

589cb0f

fix(extraction): allow extraction when server-side encryption is enabled

chore(release): 3.1.4 [skip ci]

e6cb340

## [3.1.4](v3.1.3...v3.1.4) (2026-10-30) ### Bug Fixes * **extraction:** allow extraction when server-side encryption is enabled ([6924cc0](6924cc0)) * **extraction:** guard on local storage, and propagate rar failures ([df4d49b](df4d49b))

chore(release): 3.1.5 [skip ci]

4a996c4

## [3.1.5](v3.1.4...v3.1.5) (2026-10-30) ### Bug Fixes * **extraction:** import the result on object storage and encrypted storage ([4048efb](4048efb))

Merge pull request #60 from LibreCodeCoop/main

d81a03d

fix(l10n): Update translations from Transifex

chore(release): 3.1.6 [skip ci]

511e44f

## [3.1.6](v3.1.5...v3.1.6) (2026-10-31) ### Bug Fixes * **l10n:** Update translations from Transifex ([f92d702](f92d702))

Merge pull request #62 from ashcoft/chore/agents-md

0a7eb3c

docs: record the pull-request-only workflow in AGENTS.md

dependabot Bot and others added 6 commits October 31, 2026 14:25

Merge pull request #63 from ashcoft/dependabot/npm_and_yarn/follow-re…

2e609f6

…directs-1.16.2 chore(deps): Bump follow-redirects from 1.16.1 to 1.16.2

Navigation Menu

Repository navigation

- Bugfix - Feature - Code style update (formatting, renaming) - Refactoring (no functional changes, no api changes) - Build related changes - Documentation content changes - #168

- Bugfix - Feature - Code style update (formatting, renaming) - Refactoring (no functional changes, no api changes) - Build related changes - Documentation content changes#168
ashcoft wants to merge 130 commits into
LibreCodeCoop:mainfrom
ashcoft:main

ashcoft commented Oct 31, 2026

Uh oh!

chatgpt-codex-connector Bot commented Oct 31, 2026 •

edited

Loading

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

ashcoft commented Oct 31, 2026

Pull Request Description

Related Issue

Pull Request Type

Pull request checklist

Uh oh!

chatgpt-codex-connector Bot commented Oct 31, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codex Review Summary

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

chatgpt-codex-connector Bot commented Oct 31, 2026 •

edited

Loading