Skip to content

chore(deps): refresh the shared Conduction locks - #376

Merged
rubenvdlinde merged 2 commits into
developmentfrom
chore/fleet-shared-deps-20260821
Aug 21, 2026
Merged

chore(deps): refresh the shared Conduction locks#376
rubenvdlinde merged 2 commits into
developmentfrom
chore/fleet-shared-deps-20260821

Conversation

@rubenvdlinde

Copy link
Copy Markdown
Contributor

Weekly refresh of the two shared Conduction packages. Lock-only - both are
already declared with caret ranges that permit these versions, so what this app
accepts is unchanged; only what it currently resolves to moves.

package was now
conduction/hydra-gates v1.8.1 v1.8.2
@conduction/nextcloud-vue 2.9.2 2.9.2

Why this is automated. Nothing here was ever pinned on purpose. The caret
always allowed the newer release; the lockfile is what froze it, and nobody
re-resolves a lock unless they happen to be touching dependencies. Measured
across the fleet on 2026-08-20: every app sat on hydra-gates v1.8.0 while
v1.8.1 was out, and fourteen sat below nc-vue 2.7.0 - twelve of them on 2.3.0.
Neither number was a decision.

Why it is a PR and not a push. Because a shared bump is not always safe and
this repository's suite is what knows. Taking hydra-gates v1.8.1 added
patchObject() to a published interface, which is a load-time fatal for any
concrete test double implementing it without the method - the suite dies before
a single test runs. Two apps needed stub updates first.

If this PR is red, fix it on this branch. While it stays open the weekly run
skips this app entirely and will not touch your commits - it never force-pushes
and never reuses a branch.

Opened by fleet-shared-dep-bump.yml in ConductionNL/.github.

hydra-gates v1.8.1 -> v1.8.2
nc-vue      2.9.2 -> 2.9.2

Lock-only: both packages are already declared with caret ranges that
permit these versions, so nothing about what this app ACCEPTS changes
- only what it currently resolves to. Opened by the weekly fleet
shared-dependency bump, because a lock nobody re-resolves is a pin
nobody chose.

Merging is gated by this repository's own suite, deliberately: taking
hydra-gates v1.8.1 added patchObject() to a published interface, which
is a load-time fatal for any concrete double that implements it without
the method. CI is the only thing that can tell a safe bump from that.
@github-actions

Copy link
Copy Markdown
Contributor

Quality Report — ConductionNL/nldesign @ 90ded38

Check PHP Vue Security License Tests
lint
phpcs
phpmd
psalm
phpstan
phpmetrics
eslint
stylelint
build
check-manifest
test-l10n
format
composer ✅ 104/104
npm ✅ 2/2
app:check-code ⏭️
info.xml
REUSE
PHPUnit
Newman
Playwright
Hydra gates

Quality workflow — 2026-08-21 10:54 UTC

Download the full PDF report from the workflow artifacts.

2.9.2/2.10.0 carry a CnDashboardPage regression: an `object-table` dashboard
widget canonicalised to `table` and rendered the wrong component
(ConductionNL/nextcloud-vue#722). 2.10.1 is the fix.

Lock-only; added 0, removed 0, dev-flag changes 0.
@github-actions

Copy link
Copy Markdown
Contributor

Quality Report — ConductionNL/nldesign @ 225f98a

Check PHP Vue Security License Tests
lint
phpcs
phpmd
psalm
phpstan
phpmetrics
eslint
stylelint
build
check-manifest
test-l10n
format
composer ✅ 104/104
npm ✅ 2/2
app:check-code ⏭️
info.xml
REUSE
PHPUnit
Newman
Playwright
Hydra gates

Quality workflow — 2026-08-21 13:33 UTC

Download the full PDF report from the workflow artifacts.

@rubenvdlinde
rubenvdlinde merged commit 26f4453 into development Aug 21, 2026
44 of 72 checks passed
@rubenvdlinde
rubenvdlinde deleted the chore/fleet-shared-deps-20260821 branch August 21, 2026 14:10
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.

1 participant