chore(release): 0.6.1-unstable.20260824161455 - #448
Closed
github-actions[bot] wants to merge 1 commit into
Closed
Conversation
Contributor
|
Superseded. A newer version bump for this repo has been merged into development. These accumulated because the release workflow opened a bump PR nobody merged (ConductionNL/.github#562), now fixed in .github#566 — release.yml sets auto-merge on the PR it opens, withheld semver-aware when the new version would not sort above the branch's. Note for anyone auditing: release PRs carry NO quality checks at all. A PR opened with GITHUB_TOKEN triggers no workflows (anti-recursion), and release/** is outside the push allow-list, so 'zero checks' here is the expected state rather than a gate that passed. That gap is .github#567. |
rubenvdlinde
added a commit
that referenced
this pull request
Aug 28, 2026
#485 gave buildiq a settings section with Flows, which put `Flow` in the manifest. The manifest is data the renderer walks rather than source the l10n extractor scans, so it never reached the catalogue and rendered English for a Dutch user. Maps to itself: Dutch Nextcloud keeps the product term, and decidiq, dossiq, openregister, keepiq, portaliq, pipelinq and filinq all already carry `Flow -> "Flow"`. Matching the fleet beats inventing a Dutch word for a feature name nobody uses one for. This is the third time today the same gap has produced a regression within hours of a sweep: keepiq via #448, and now this. `check:l10n-js` cannot catch it and did not — nl.json and nl.js were in sync at 1,045 keys each, both simply missing the string. That check guards source-versus-artifact drift; this is manifest-versus-catalogue coverage, and only humaniq runs a check that asserts it. Verified: 0 manifest strings left without Dutch, keys DROPPED = 0, check:l10n-js PASS.
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
1 participant
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.
Version bump for 0.6.1-unstable.20260824161455, opened by the release workflow.
The tag v0.6.1-unstable.20260824161455 already names this commit, so the released
package and its label agree. Merging this brings development up
to the released version.
Raised as a pull request rather than pushed directly because
development requires one; a direct push is rejected with GH013
and takes the release down with it.