Repository navigation
Release: merge development into beta - #1269
Open
github-actions[bot] wants to merge 19 commits into
Open
github-actions[bot] wants to merge 19 commits into
github-actions[bot] wants to merge 19 commits into
Conversation
…0261008095136 chore(sync): carry beta back into development
…x 47 @SPEC paths Two findings from Thijn's re-review of the beta promotion (#1026), after #1261 restored the frozen widget id: Restoring `softwarecatalog_concept_organisaties_widget` keeps the widget for users from before the rename, but drops it for everyone who added it while stable 0.1.148 to 0.2.0 and beta registered it as `stackiq_concept_organisaties_widget`. The Dashboard app keeps that choice in `oc_preferences` under its own app id `dashboard`, key `layout`, as a comma-separated list of widget ids, which IConfig reaches like this app's own rows. The new post-migration repair step RepointDashboardWidgetId rewrites the renamed id to the frozen one for every seen user, in place and without listing the frozen id twice; a layout without the renamed id is left alone. The widget comment and the app-id-rename spec no longer claim the rows are out of reach. The archive pass (1aa2346, 7339b35) moved four changes without updating their @SPEC tags: wizard-dataset-card-load (4), portal-contribution (8), publication-field-rules (20) and rename-app-id-to-stackiq (14), 47 tags in 16 files now point at openspec/specs/<capability>/spec.md. The anchors were checked against the synced specs. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
… runs Hydra gate-110: a repair step added without moving <version> in appinfo/info.xml makes `occ upgrade` answer "No upgrade required." and run none of them. 0.2.4-unstable.20261001120000 → 0.2.5-unstable.20261008120000, the same shape as #997 for the EOL repair step. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
fix(dashboard): re-point dashboards from the renamed widget id and fix 47 @SPEC paths
chore(parity): normalise features in the capability matrix
…cations list by _ids The Applications page sent the facet/search match as a plain `id` filter, which OpenRegister's objects endpoint ignores (verified on 2.1.36: `id[]=` returns the whole list, `_ids[]=` narrows), so a search or GEMMA facet selection narrowed nothing while the counts said it did. The narrowing filter now uses `_ids` (and the no-match sentinel still yields an empty list); the helper has its own spec. Reference columns rendered the raw uuid: `provider` on Applications, the organisation on an application's Usages, the application on an organisation's usages, connections and compliance claims, and the module on Module versions and Applications in use. Those columns are now column objects with the library's `fkResolve` cell widget (uuid → name through the object store) and their own label — an object-typed property gets no schema-generated column, so a bare key showed the key as its header. An organisation's Applications list named no application (only licence and BBN level) and had no way to the rest beyond "+N more"; it now leads with the name and links to the Applications page filtered on the organisation. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Review of #1275 (f1): "In development since" and "In use since" were the only two of the thirteen new column labels missing from nl.json, so Dutch users saw them in English. Added to en.json and nl.json and the browser files rebuilt with `npm run l10n:build`; `npm run test:l10n` passes (every used key present in en.json). Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
chore(parity): every spec under a feature, every capability on a screen
CI on #1275: `quality / Frontend Check (format)` flagged the three new or changed JS/Vue files (`npx prettier --write` on them; no semantic change, `npm run format` now clean) and Hydra gate-16 spec-coverage flagged `facetNarrowingFilter` as a changed method without an @SPEC tag — the tag now sits on the function docblock (both anchors are requirement headings in openspec/specs/gemma-faceted-search/spec.md). eslint 0 errors; the helper's spec still passes (3 tests). Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…ings fix(ui): name references in the catalogue tables and narrow the Applications list by _ids
Bumps [guzzlehttp/guzzle](https://github.com/guzzle/guzzle) from 7.15.2 to 8.2.0. - [Release notes](https://github.com/guzzle/guzzle/releases) - [Changelog](https://github.com/guzzle/guzzle/blob/8.2/CHANGELOG.md) - [Commits](guzzle/guzzle@7.15.2...8.2.0) --- updated-dependencies: - dependency-name: guzzlehttp/guzzle dependency-version: 8.2.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>
The release build runs npm ci, so it bundles the version in the lock. 2.73.1 carries nextcloud-vue#1390: the page-size selector of an index page works again, and the Related panel of a detail page opens the related object and shows names instead of uuids. The floor in package.json moves with it, so an install can never resolve below the version that has those fixes. The lock also drops "dev": true from five optional platform binaries; that is the newer npm writing the lock, not a dependency change. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…-2.73.1 chore(deps): bump @conduction/nextcloud-vue from 2.65.0 to 2.73.1
Status: code reviewed (Thorough), approval once #1295 is merged and the E2E run is greenCode: no blockers. Of the seven merged PRs in this release, only the authors had reviewed them, so each code PR was read at full depth.
One minor: Why the required
Next: once #1295 is merged into Gates: CI |
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
2 participants
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.