Repository navigation
Release: merge development into beta - #649
Open
github-actions[bot] wants to merge 47 commits into
Open
github-actions[bot] wants to merge 47 commits into
github-actions[bot] wants to merge 47 commits into
Conversation
) Bumps [jest-environment-jsdom](https://github.com/jestjs/jest/tree/HEAD/packages/jest-environment-jsdom) from 30.5.0 to 30.5.1. - [Release notes](https://github.com/jestjs/jest/releases) - [Changelog](https://github.com/jestjs/jest/blob/main/CHANGELOG.md) - [Commits](https://github.com/jestjs/jest/commits/v30.5.1/packages/jest-environment-jsdom) --- updated-dependencies: - dependency-name: jest-environment-jsdom dependency-version: 30.5.1 dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [webpack](https://github.com/webpack/webpack) from 5.110.1 to 5.110.3. - [Release notes](https://github.com/webpack/webpack/releases) - [Changelog](https://github.com/webpack/webpack/blob/main/CHANGELOG.md) - [Commits](webpack/webpack@v5.110.1...v5.110.3) --- updated-dependencies: - dependency-name: webpack dependency-version: 5.110.3 dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [sass](https://github.com/sass/dart-sass) from 1.103.1 to 1.104.0. - [Release notes](https://github.com/sass/dart-sass/releases) - [Changelog](https://github.com/sass/dart-sass/blob/main/CHANGELOG.md) - [Commits](sass/dart-sass@1.103.1...1.104.0) --- updated-dependencies: - dependency-name: sass dependency-version: 1.104.0 dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…#641) Bumps [@typescript-eslint/parser](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/parser) from 8.68.0 to 8.69.0. - [Release notes](https://github.com/typescript-eslint/typescript-eslint/releases) - [Changelog](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/parser/CHANGELOG.md) - [Commits](https://github.com/typescript-eslint/typescript-eslint/commits/v8.69.0/packages/parser) --- updated-dependencies: - dependency-name: "@typescript-eslint/parser" dependency-version: 8.69.0 dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
) Bumps [conduction/hydra-gates](https://github.com/ConductionNL/.github) from 1.10.0 to 1.16.0. - [Release notes](https://github.com/ConductionNL/.github/releases) - [Commits](ConductionNL/.github@v1.10.0...v1.16.0) --- updated-dependencies: - dependency-name: conduction/hydra-gates dependency-version: 1.16.0 dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [phpstan/phpstan](https://github.com/phpstan/phpstan-phar-composer-source) from 2.2.9 to 2.2.13. - [Commits](https://github.com/phpstan/phpstan-phar-composer-source/commits) --- updated-dependencies: - dependency-name: phpstan/phpstan dependency-version: 2.2.13 dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [jest](https://github.com/jestjs/jest/tree/HEAD/packages/jest) from 30.5.0 to 30.5.1. - [Release notes](https://github.com/jestjs/jest/releases) - [Changelog](https://github.com/jestjs/jest/blob/main/CHANGELOG.md) - [Commits](https://github.com/jestjs/jest/commits/v30.5.1/packages/jest) --- updated-dependencies: - dependency-name: jest dependency-version: 30.5.1 dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [sass-loader](https://github.com/webpack/sass-loader) from 17.0.0 to 17.0.1. - [Release notes](https://github.com/webpack/sass-loader/releases) - [Changelog](https://github.com/webpack/sass-loader/blob/main/CHANGELOG.md) - [Commits](webpack/sass-loader@v17.0.0...v17.0.1) --- updated-dependencies: - dependency-name: sass-loader dependency-version: 17.0.1 dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
#653) On 2026-09-08 a PHPUnit run in openregister took 19 GB of RAM because the CLI php.ini sets memory_limit=-1 and nothing stopped a runaway DI cycle. phpunit.xml and phpunit-unit.xml now set a hard 2G cap (the unit suite peaks at 46 MB). The psalm script gets --memory-limit=2G and each phpmd invocation runs under php -d memory_limit=2G. The test bootstrap never loads lib/base.php (pure-unit with stubs), so it needs no installed-root guard and is untouched. Co-authored-by: Conduction Release Bot <release-bot@conduction.nl> Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
Bumps [eslint](https://github.com/eslint/eslint) from 10.9.1 to 10.10.0. - [Release notes](https://github.com/eslint/eslint/releases) - [Commits](eslint/eslint@v10.9.1...v10.10.0) --- updated-dependencies: - dependency-name: eslint dependency-version: 10.10.0 dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [stylelint](https://github.com/stylelint/stylelint) from 17.14.1 to 17.15.0. - [Release notes](https://github.com/stylelint/stylelint/releases) - [Changelog](https://github.com/stylelint/stylelint/blob/main/CHANGELOG.md) - [Commits](stylelint/stylelint@17.14.1...17.15.0) --- updated-dependencies: - dependency-name: stylelint dependency-version: 17.15.0 dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) from 26.4.0 to 26.4.1. - [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases) - [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node) --- updated-dependencies: - dependency-name: "@types/node" dependency-version: 26.4.1 dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [@playwright/test](https://github.com/microsoft/playwright) from 1.62.1 to 1.63.0. - [Release notes](https://github.com/microsoft/playwright/releases) - [Commits](microsoft/playwright@v1.62.1...v1.63.0) --- updated-dependencies: - dependency-name: "@playwright/test" dependency-version: 1.63.0 dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [@conduction/nextcloud-vue](https://github.com/ConductionNL/nextcloud-vue) from 2.36.2 to 2.38.0. - [Release notes](https://github.com/ConductionNL/nextcloud-vue/releases) - [Changelog](https://github.com/ConductionNL/nextcloud-vue/blob/main/CHANGELOG.md) - [Commits](ConductionNL/nextcloud-vue@v2.36.2...v2.38.0) --- updated-dependencies: - dependency-name: "@conduction/nextcloud-vue" dependency-version: 2.38.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
) Bumps [conduction/hydra-gates](https://github.com/ConductionNL/.github) from 1.16.0 to 1.16.1. - [Release notes](https://github.com/ConductionNL/.github/releases) - [Commits](ConductionNL/.github@v1.16.0...v1.16.1) --- updated-dependencies: - dependency-name: conduction/hydra-gates dependency-version: 1.16.1 dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…k` (#663) Creating a zaakinformatieobject 500s where dossiq is installed: ZGWLogicService::createOio(): Argument #1 ($objectUrl) must be of type string, null given Two producers write a ZIO and they disagree about the property name. This app's own ZaakInformatieObjectenController requires `zaak`. Dossiq's ZgwZrcZaakinformatieobjectRules stores `case` (storedKey: 'case'). Reading only `zaak` therefore handed null into a parameter typed string, and the error named createOio's argument rather than the property that was missing. It reproduces only where both apps are installed, which is why CI does not see it and why it survived this long. A single zioCaseUrl() helper now resolves either key, and both ZIO sites use it: createObjectInformatieObjectZaak, and the ZIO branch of deleteObjectInformatieObject, which would otherwise have left the OIO behind instead of failing loudly. When neither key is present it throws naming both, because that is a broken record rather than a producer disagreement. createZaakBesluit reads a besluit's own `zaak` and is untouched: dossiq ships no besluit rules. Verified: three new tests cover the dossiq key, this app's key, and the neither-key case. Reverting the fix makes the dossiq one fail, so the guard is real. Full suite 290 tests exit 0 at 46 MB; phpcs exit 0 with 37 pre-existing warnings on untouched lines. Co-authored-by: Conduction Release Bot <release-bot@conduction.nl>
The ZGW event listener subscribed on schema slug alone, so any app on the same OpenRegister instance that names a schema zaakinformatieobject, besluitinformatieobject or zaaktypeInformatieobjecttype had this app's ZGW rules run against its data. That is what happened. dossiq writes its own zaakinformatieobject, this app's cascade ran on the row, read a key dossiq had renamed, and the null reached a typed string parameter. The create answered 500. All five handler entry points were exposed, not only the one that threw. Ownership is now decided before any rule runs, from the application stamp OpenRegister already records. The narrowing is one-directional on purpose: an absent stamp is treated as ours, because instances that build the ZGW registers by hand carry no stamp and treating those as foreign would be an outage rather than a fix. Verified by exit code: composer check:strict clean, phpmd swept per directory across both rulesets, 300 tests and 926 assertions. The skip logic is mutation checked, and the two positive tests deliberately survive the mutation so the narrowing cannot silently become an outage. E2E skips on pull_request, so this pull request says nothing about E2E either way. The end to end proof is the dossiq documents spec that surfaced the defect.
Cleaning up after myself. #663 was mine and it was the shallower of two fixes for the same 500. #665 found the real defect: the ZGW listener subscribed on schema slug alone, so this app's whole cascade ran against another app's rows. Reading the key dossiq writes only made the wrong thing succeed further, into a register that does not exist on that instance. #665 left the branch in place with a comment and the decision to me, and named the question to answer first: does any producer in THIS app's registers write `case`? It does not. ZaakInformatieObjectenController is the only producer and validateZioUrls rejects a body without `zaak` with a 400. The `case` spelling only ever came from dossiq, whose objects ZGWObjectScopeService now skips. Removed rather than commented out, because it was worse than dead. The scope check treats an ABSENT application stamp as ours, deliberately, so hand-built ZGW registers keep working; a foreign row can therefore still arrive wherever a producer stops stamping. Accepting `case` there would write an OIO into a register that may not exist. Failing names the missing property and reports the scoping bug instead, which is what that situation is. testCreateObjectInformatieObjectZaakAcceptsTheCaseKey goes with it: #665 correctly identified it as the one thing holding the branch alive, and it called the method directly rather than through the listener, so it said nothing about live behaviour. The neither-key test stays, with its message assertion narrowed. Verified: 299 tests exit 0 at 47 MB, phpcs exit 0. Co-authored-by: Conduction Release Bot <release-bot@conduction.nl>
The webpack alias forced `@nextcloud/axios` to `node_modules/@nextcloud/axios/dist/index.cjs`, so the shared component library's import resolved to this app's copy and interceptors and the CSRF token stayed shared. 2.6.0 dropped CommonJS. It deleted dist/index.cjs, removed `main`, and its exports map now declares only `types` and `import\', with the build at dist/index.js. The alias therefore points at a file that no longer exists, and because it is an exact-match rule it takes down EVERY consumer of the bare specifier at once. webpack names the issuer rather than the alias, so the errors read as @conduction/nextcloud-vue/dist/esm/... and look like a broken library. They are not: that library emits only bare specifiers, externalises axios, declares it peer-only, and its own CI is green on 2.6.0. The single-copy guarantee the alias was written for does not need the alias: peer-only means npm hoists exactly one copy and the bare specifier already resolves to it. Verified in planninq, where the identical alias is the only variable between a build that exits 1 with 72 resolution errors and one that exits 0 on the same checkout (ConductionNL/planninq#606). Three of the 21 fleet apps aliased the deleted path: planninq, larpinq and zaakafhandelapp. Three more alias the package ROOT, which resolves through the exports map and is unaffected. Not verified locally: this is a build-config change and the app's own Frontend Build job is what proves it. I did not install this app's dependencies to build it here. Co-authored-by: Conduction Release Bot <release-bot@conduction.nl>
Bumps [gridstack](https://github.com/gridstack/gridstack.js) from 12.6.0 to 13.2.0. - [Release notes](https://github.com/gridstack/gridstack.js/releases) - [Changelog](https://github.com/gridstack/gridstack.js/blob/master/doc/CHANGES.md) - [Commits](gridstack/gridstack.js@v12.6.0...v13.2.0) --- updated-dependencies: - dependency-name: gridstack dependency-version: 13.2.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [@vitest/coverage-v8](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8) from 4.1.11 to 5.0.0. - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md) - [Commits](https://github.com/vitest-dev/vitest/commits/v5.0.0/packages/coverage-v8) --- updated-dependencies: - dependency-name: "@vitest/coverage-v8" dependency-version: 5.0.0 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Supersedes #613, which fails Frontend Tests on two zod 4 breaking changes. Both are in our code, not in the bump. 1. `SafeParseReturnType` is gone. zod 4 exports `ZodSafeParseResult<T>`, with ONE type parameter where the old one took two. Eleven entity `validate()` methods declared `SafeParseReturnType<TX, unknown>`. THE PARAMETER THAT SURVIVES IS THE SECOND ONE. zod 3 read `SafeParseReturnType<Input, Output>` as `SafeParseSuccess<Output> | SafeParseError<Input>`, so these methods have always returned `unknown` on success. Translating them to `ZodSafeParseResult<TX>` looks like the obvious move and is wrong: it tightens the success type, and tsc rejected it because the schemas do not match their entity types — `id` is optional in the schema and required in `TZaak`. `ZodSafeParseResult<unknown>` is the faithful translation and leaves every caller reading exactly what it read before. Whether those annotations SHOULD be tightened is a separate question from a dependency bump. 2. `z.record()` now requires an explicit key type. One site, `z.record(z.any())` -> `z.record(z.string(), z.any())`. Found by the compiler, not by reading release notes: the first attempt went 18 failing suites -> 12, and the remaining 24 diagnostics were all TS2554 on that one `z.record` line. Verified locally rather than left to CI: `npm test` (jest, the runner that was failing) — 24 suites, 43 tests, all passing, exit 0. Co-authored-by: Conduction Release Bot <release-bot@conduction.nl>
Bumps [@nextcloud/axios](https://github.com/nextcloud-libraries/nextcloud-axios) from 2.5.2 to 2.6.0. - [Release notes](https://github.com/nextcloud-libraries/nextcloud-axios/releases) - [Changelog](https://github.com/nextcloud-libraries/nextcloud-axios/blob/main/CHANGELOG.md) - [Commits](nextcloud-libraries/nextcloud-axios@v2.5.2...v2.6.0) --- updated-dependencies: - dependency-name: "@nextcloud/axios" dependency-version: 2.6.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…required (#686) `@vitest/coverage-v8` was bumped to 5.0.0 while `vitest` stayed on 4.1.11. coverage-v8 declares `peer vitest: "5.0.0"`, an exact pin rather than a caret, so development has been shipping a plugin mismatched to the runner it plugs into. This finishes the move rather than reverting it. `vite` is declared explicitly because vitest 5 resolves it from the project where 4 did not; 8.2.2 was already in the lock transitively, so nothing new is pulled in. npm run test:unit -> 3 files, 21 tests passed, exit 0 npm run test:coverage -> same, plus a v8 report, exit 0 Co-authored-by: Conduction Release Bot <release-bot@conduction.nl>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
The box runs one Nextcloud on localhost:8080 that bind-mounts everybody's checkout and holds data colleagues are working on. The fixture helpers create and delete OpenRegister objects, so a run aimed there edits someone else's environment. No default is not the same as no accident: an explicit PLAYWRIGHT_BASE_URL can name the shared container too. tests/e2e/shared-instance.ts refuses loopback port 80 or 8080 unless the run set ZAAKAFHANDELAPP_E2E_ALLOW_SHARED_INSTANCE or E2E_ALLOW_SHARED_INSTANCE to that same origin. CI is exempt, where 8080 is the job's own throwaway instance. The guard sits on the resolved value in resolveBaseUrl(), which both playwright configs, global-setup.ts and workflows/fixtures.ts already call, so there is one place a target enters the suite. The unit test lives under tests/vitest/ because the vitest config excludes tests/e2e/** on purpose; there it is actually collected.
…60912202725 chore(release): 0.3.2-unstable.20260912202725
…tegriq's registry (#693) * docs(openspec): adopt-connection-registry change for the ZGW connections page * feat(connections): declare the eight ZGW and storage sources for integriq's registry * feat(connections): Integrations page over integriq's connection registry * feat(connections): report ZRC and BRC call outcomes and refresh after a configuration save * test(e2e): Integrations page spec, and integriq in the CI instance * fix(connections): split refused and gateway statuses so psalm reads no paradox
…3.2.0 (#710) nextcloud-vue 3.2.0 ships connectionStatus and connectionSettingsLabel as built-ins, including the seventh status, disabled (Switched off). The local copy knew six statuses and would have shadowed the built-in, so it goes, and so do the tests that only covered it. One test now proves App.vue passes no formatter of its own and the built-in labels disabled as Switched off. Refs ConductionNL/hydra#677, ConductionNL/nextcloud-vue#1173, #1175
…for the connection strings (#712) Prettier 3.9.6 over the three files the connection-registry wave merged unformatted. ConnectionsDeclarationTest and AppstoreMetadataTest now read appinfo/info.xml as bytes: Nextcloud's lib/base.php installs an external entity loader that returns null, so simplexml_load_file() returns false in every CI cell. The thirteen connection-registry strings gain translations in the 35 locales that were short them, ten of the thirteen taken from openregister's catalogues so the same word reads the same in both apps. Verified locally: composer check:strict ALL CHECKS PASSED (328 tests), npm run format exit 0, npm run lint 0 errors, npm run test:l10n full parity, npm run check:l10n-js up to date.
| for (const { title } of DECLARED) { | ||
| await expect( | ||
| page.getByRole('row', { | ||
| name: new RegExp(title.replace(/[()]/g, '\\$&'), 'i'), |
The 3.x majors were withdrawn on 2026-09-19. Only v2.* git tags survive and .releaserc.json maps a breaking footer to a minor, so 2.x is the line that still gets releases. A ^3.2.0 range matches only 3.x, which means this app was pinned to a line nobody publishes to. Range set to ^2.56.0, npm's current latest, and the lockfile regenerated with npm install.
chore(deps): move nextcloud-vue back to the living 2.x line
Dexie refuses to run when two bundles on one page ship different versions, and openregister's integration-global bundle loads on every page, so every app must ship exactly openregister's dexie. Moves together with ConductionNL/openregister#3788.
Five systems, 225 rows reused by id from dossiq's matrix at ecfdfa39e1 with their competitor cells cited, and row z.0 for the register nothing provisions. Our own column is unknown on every row a reader has not yet read.
Packs r1 (40 of 47 rows) and r2 (56 rows): intake, case-core, decisions, tasks-and-phases, documents, parties-and-contacts.
…earch, reporting (wip)
…, access-and-privacy (wip)
…s (wip) z.21, 11.1 and 8.1 drop to partial: the mail, the case type editor and the deadline derivation rest on fields the only known schema lacks or on routes no page calls. 1.3, 5.8 and 13.7 keep their rating with the reachedOn corrected to the surface that actually opens them.
Rated from the 2026-03-13 research in concurrentie-analyse procest/openzaak/, graded docs-only: 48 yes, 47 partial, 128 no, 2 unknown, each with a file and line.
Also strips an em-dash from reader prose at build time.
feat(parity): add the capability matrix against ZAC, GZAC, xxllnc Zaken, OpenCase and Open Zaak
- appinfo/info.xml: max-version 34 -> 35 (min stays 32) - composer.json: nextcloud/ocp ^34.0 -> ^35.0, composer.lock refreshed (ocp v35.0.1; pulls symfony/polyfill-php84/85/86 as ocp deps) - code-quality.yml: drop the hard-coded nextcloud-test-refs override so the shared quality.yml derives the matrix (incl. stable35) from info.xml Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01M7DxSg7d7wqqZsUppLWf7J
chore(nc35): declare Nextcloud 35 support
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automated PR to sync development changes to beta for beta release.
Merging this PR will trigger the beta release workflow.