nusz-1.9.11.47 · vuer-release @13

Release issue: ASSNUSZ-116 — “NÚSZ Release 1.9.11.47” (authoritative manifest; version comes from its summary) · internal FKITDEV-8938 Delivery: 🅼 Harbor (vuer-release) — active · 🅻 legacy vuer_build — standby Predecessor: nusz-1.9.11.46 / @12 (2026-04-27) YouTrack: read-only for scope; post-release ticket updates are manual (see below).

Cut & publishing — 2026-07-03

nusz@13 is cut and pushed; the self-hosted autobuild CI is publishing app 1.9.11.47 to Harbor. The .47→.48 / @14 renumber once planned (older memo) was overtaken by events — it shipped as .47 / @13. Reusable how-to: vuer-release-cut-recipe. Details in Cut record — 2026-07-03.

Cut record — 2026-07-03

As-shipped code payload (source tag nusz-1.9.11.47):

• FKITDEV-8747 — daily-statistics / SL video-calls report fix (empty-period SL → null not 0; Sum-column SL aligned; locale plumbed end-to-end through the RPC queue). PR #7929. CORE (not customization/nusz). This is the ASSNUSZ-58 / SLANUSZ-28 discrepancy work.
• FKITDEV-8959 — self-healing NÚSZ image-deletion cron (RemoveAttachmentDataCronJob; key-guarded; image-scoped batched query). PR #8010. customization/nusz only. Folded into .47 scope after the 2026-06-15 planning.

Planned-vs-shipped reconciliation

The 2026-06-15 planned 3-ticket scope (see Payload (as of 2026-06-15)) resolved as: ASSNUSZ-58 / SLANUSZ-28 → FKITDEV-8747 (shipped); CRNUSZ-102 → FKITDEV-8794 / FKITDEV-8801 — no code/PR in the source tag (content/frontend; verify separately); plus FKITDEV-8959 (image-deletion) folded in.

Source tags (already existed — NOT created at cut time):

Repo	Tag	Commit
vuer_oss	nusz-1.9.11.47	d426cc6ae1278e473afbc3484598d83105f3840d
vuer_css	nusz-1.9.11.47	cef991e71836cd4ff3105142f38996fa84540091

vuer-release cut (@13):

• Added projects/nusz/release/13/release.json — COMPONENT_LIST = vuer_oss + vuer_css, VERSION 1.9.11.47, TAG nusz-1.9.11.47.
• Commit 712000cd9353baa71d7e45f851244c84adce6332 (Release: nusz, version: 13), solo-author wowjeeez, direct to master (clean FF over d7ebb37).
• Tag nusz@13 (== master tip == the commit) pushed → fires autobuild.yml on [self-hosted, docker].
• CI run 28667229191 — parse_tag ✅ green (6 s); build in progress at handoff. Watch: gh run watch 28667229191 --repo TechTeamer/vuer-release.

janus pin — @13 ships 1.4.1 / cc0fdca8b52916873f0280a03e15bf5fca0da906, NOT 60ed394f

This supersedes the “keep janus 60ed394f” line in Version & repo plan. The janus security update #27 (commit 4e256d4) is already on master’s projects/nusz/components/vuer_oss/component_env_values.json, and the CI’s release-tool gen snapshots component config into release.json — so a cut necessarily carries whatever the component config holds. release/13/release.json was made to agree with master (cc0fdca8) to remove any gen/overwrite ambiguity. Net: @13 = app .47 (8747 + 8959) plus the janus 1.4.1 security bump. (The old 60ed394f note predates #27 landing on master.)

Still-dangling (NOT part of .47): chore/FKITDEV-8966-nusz-devel-update (vuer_oss 809bebc9 / vuer_css a51ea9fd8 — the 27-ticket devel-sync incl. the CRNUSZ-102 revert) remains unmerged. Decide whether it becomes a future real .48.

Remaining manual post-build steps (YouTrack is read-only for the agent — do by hand):

• Verify Harbor has nusz/{vuer_oss,vuer_css}:1.9.11.47-…
• Strip Ready for release from the payload tickets
• Resolve FKITDEV-8747 / FKITDEV-8959
• Mark ASSNUSZ-116 → Solved

Scope — how the payload is determined

Authoritative source = tickets Package-linked to the open release issue ASSNUSZ-116. Readiness is checked per member via tag or status. Re-derive before cutting; /fk-release will automate this.

Collection = (A ∪ B1 ∪ B2), all #Unresolved:

• A — tagged: project: CRNUSZ,BUGNUSZ,SLANUSZ,ASSNUSZ tag: {Ready for release}
• B1 — CR deploy-ready, untagged: project: CRNUSZ {CR Pipeline}: {Ready for Deployment} #Unresolved -{Ready for release}
• B2 — SLA/ASS/Bug, untagged: project: CRNUSZ,BUGNUSZ,SLANUSZ,ASSNUSZ Blocker: {Release needed} #Unresolved -{Ready for release}

#Unresolved excludes already-shipped (ship = resolved state + tag stripped; Blocker is sticky, so the unresolved filter is mandatory).

Payload (as of 2026-06-15)

Ticket	Summary	Status	Implementation (FKITDEV)	Merged to customization/nusz?
CRNUSZ-102	NÚSZ - Videóchat oldal aktualizálása a honlapon	Pending · CR Pipeline: Ready for Deployment · tagged	FKITDEV-8794, FKITDEV-8801	⬜ verify
ASSNUSZ-58	Napi statisztika eltérés	Blocked · Blocker: Release needed · tagged	confirm FKITDEV link	⬜ verify
SLANUSZ-28	SL riport eltérés	Blocked · Blocker: Release needed · tagged	FKITDEV-8639	⬜ verify

Status-only delta (untagged but status-ready): none today — payload = the 3 tagged tickets.

Version & repo plan

• nusz-1.9.11.46 / @12 → nusz-1.9.11.47 / @13 (version confirmed by the ASSNUSZ-116 summary).
• Source tag nusz-1.9.11.47 on both vuer_oss + vuer_css.
• vuer-release: new projects/nusz/release/13/release.json — copy release/12, bump VERSION+TAG → 1.9.11.47 / nusz-1.9.11.47; components = vuer_oss + vuer_css only; keep janus 60ed394f… (constant since @2).

Release checklist

Shared core

• [PREPARE] Re-derive scope (A∪B1∪B2, #Unresolved) + reconcile with ASSNUSZ-116 Package links — flag mismatches
• [PREPARE] Per payload ticket: confirm its FKITDEV impl ticket is Resolved AND FKITDEV-NNNN appears in customization/nusz history (merge proof)
• [PREPARE] Sync customization/nusz ← devel if a core update is due (update/customization/nusz-<date>)
• [PREPARE] Update changelog (customization/RELEASE.md on customization/nusz) with the FKITDEV IDs — confirm the file’s exact heading format on that branch first
• [PREPARE] ⚠️ git ls-remote to confirm tips — vuer_css has a narrowed fetch refspec (local refs go stale)
• [GATE] Approve source-tag cut (approver: operator)
• [CUT] Tag vuer_oss → nusz-1.9.11.47, push
• [CUT] Tag vuer_css → nusz-1.9.11.47, push

🅼 Modern publish (active)

• [PREPARE] Create vuer-release/projects/nusz/release/13/release.json (copy @12, bump)
• [GATE] Approve release tag
• [CUT] Commit + tag vuer-release nusz@13, push → self-hosted CI fires
• [VERIFY] autobuild Actions run green + Harbor tags harbor.techteamer.com/nusz/{vuer_oss,vuer_css}:1.9.11.47-… present
• [DONE] Status → released

🅻 Legacy publish (standby — only if on-prem handover)

• On fk-dev (command ssh ops@fk-dev.taild4189d.ts.net — the old ssh Facekom box is decommissioned, see dev-build-host), keys in place: ./build.sh -b nusz-1.9.11.47 then ./sign-partner.sh -t nusz-1.9.11.47 -k cosign.key

Manual post-release (YouTrack — read-only tool, do by hand)

• Strip Ready for release tag from each payload ticket
• Transition each payload ticket → resolved (CR: Done / SLA·ASS: Solved)
• Mark release issue ASSNUSZ-116 → Solved

Failure handling: if CI fails after a tag is pushed, fix-forward to the next @N — do not delete pushed tags. (Precedent: @8 was skipped, never created.)

Changelog draft (# 1.9.11.47)

References the FKITDEV implementation tickets (confirm heading format on customization/nusz):

• FKITDEV-8794 / FKITDEV-8801 — CRNUSZ-102 NÚSZ videóchat oldal aktualizálása a honlapon
• FKITDEV-8639 — SLANUSZ-28 SL riport eltérés
• (ASSNUSZ-58 Napi statisztika eltérés — add its FKITDEV ID)

Status log

• 2026-06-15 — Hub created; scope mechanism (ASSNUSZ-116 manifest + tag/status union) defined; payload = 3 tickets; FKITDEV impl links mapped; version @13 / 1.9.11.47 confirmed. Next: verify FKITDEV merges, then cut.

Related

release-automation-design · release-process · youtrack-ready-for-release-nusz-query

Payload detail — implementation, PR & test notes

Merge status (2026-06-15): payload code is NOT yet confirmed in customization/nusz — resolving this is the first cut-prep step. Version target also needs confirming (ticket threads reference .45/.46/.46.1).

CRNUSZ-102 — NÚSZ videóchat oldal aktualizálása a honlapon

• Impl: FKITDEV-8794 (becslés/estimate), FKITDEV-8801 (screenshots) — ⚠️ no code/branch/PR found in vuer_oss or vuer_css; implementation source unclear (possibly frontend/content/another ticket). Resolve before cut.
• Business state: client-accepted (“A képek alapján minden rendben”); routed here (“kerüljön ki az 1.9.11.47 release keretében… Az installnak support oldalról semmi akadálya”); UAT 06.18.
• Test evidence (screenshots, Ferenc Jurkiewicz): image.png, Screenshot from 2026-05-11 13-49-32.png, image1.png, Screenshot from 2026-05-11 13-57-26.png

SLANUSZ-28 — SL riport eltérés

• Impl: FKITDEV-8639 → PR #7862, branch feature/FKITDEV-8639 (3 commits: empty-cell SL fix; count silently-disconnected as exits; Sum column in Excel). ⚠️ NOT merged to customization/nusz.
• Test notes: split from ASSNUSZ-58; “fix done, delivered in 1.9.11.45 release”; “Az 1.9.11.45-öt az 1.9.11.46-tal fogjuk élesre telepíteni.” → ⚠️ may already be in .45/.46 — confirm new-for-.47 vs already-shipped.

ASSNUSZ-58 — Napi statisztika eltérés

• Impl: related to SLANUSZ-28 (same fix area); andras.lederer handled the stat-export part.
• Test notes (UAT/QA):
  • Bence László: “Több hiba van: a hívások + vesztett hívások + időn túl felvett hívások összege nem stimmel…” (split off SLANUSZ-28)
  • peter.szollar: “ez a fix a 1.9.11.46.1-os release-el fog kikerülni, már UAT-on van… akkor megyünk tovább PROD-ra” (UAT→PROD gate; ⚠️ targeted .46.1)
  • client: “Az UAT-on teszteltem… Az SL eltérés itt is jelentkezett… A napi stat eltérés most nem jelentkezett…” 📎 image2.png, image3.png

Devel update — 2026-06-16 (PRs pending merge)

Conducted the devel → customization/nusz core sync for both repos in isolated git worktrees (protecting the unpushed instacash WIP on the main checkouts). Branch chore/FKITDEV-8938-nusz-devel-update (ruleset-compliant), commit chore(customization/nusz): devel update 2026-06-16 (solo-author), pushed — PRs pending review/merge (base customization/nusz).

• vuer_oss @ 809bebc9 — 36 devel commits. Conflicts (2): config/dev.json → kept nusz’s 12 flows, dropped devel’s test flows and the new extraCreatableProtoType key (per decision); yarn.lock regenerated. Plus a merge-hidden lint break — cron.js:46 extensionless require('./server/service/FFmpegService') broke after devel renamed it .js→.ts; fixed to .ts. Lint green; remaining jest failures all pre-existing/environmental. See nusz-devel-update-2026-06-16-lint-merge-fix.
• vuer_css @ bb7fec60 — 11 devel commits incl. FKITDEV-8537 CSS TS support [BREAKING]. Zero conflicts. Lint + build + scoped jest (115 suites / 1040 tests) green; yarn.lock install-churn folded in.

Ruleset gotcha (new): TechTeamer/vuer_oss + vuer_css now enforce GitHub rulesets — branch names must match ^(feature|feat|chore|fix|release)/(FKITDEV|FKQA)-\d+… and commit messages must be conventional-commits. Plain update/customization/<client>-<date> branches + default merge messages are REJECTED (push error GH013). Use chore/FKITDEV-<n>-… + chore(customization/nusz): devel update <date>.