Levandor

FaceKom Releases

3 min read

FaceKom Releases

Per-release tracking hubs + the release-automation design. Runbook: release-process. Cut recipe: vuer-release-cut-recipe. How the release tool works internally: vuer-release-build-flow. CLI pinning + toolchain traps: vuer-release-cli-pinning. What COMPONENT_LIST actually means: component-list-is-not-a-full-manifest. Design: release-automation-design. Client name/path map: client-registry.

How release scope is determined (YouTrack)

Authoritative manifest = tickets Package-linked to the open ASS<CLIENT> “Release” issue. Readiness union (merged client-side, #Unresolved):

  • project: <CLIENT projects> tag: {Ready for release}
  • project: CR<CLIENT> {CR Pipeline}: {Ready for Deployment} #Unresolved -{Ready for release}
  • project: <CLIENT projects> Blocker: {Release needed} #Unresolved -{Ready for release}

See youtrack-ready-for-release-nusz-query.

Release test records (tesztjegyzőkönyv)

Per-release test records (“Tesztelési jegyzőkönyv”) are PDF/DOCX attachments on the per-client ASS<CLIENT> release / BUG<CLIENT> tickets, not standalone issues. How to find + download any of them (read-only REST recipe), plus client-specific notes (InstaCash had none until 2026-06-26 — the eSign 1.3.0.11 one is the first, generated via fk-tjk; Raiffeisen is the only other eSign-tied one): youtrack-tesztjegyzokonyv-attachment-recipe.

TJK-source test runbooks (prioritized manual test plans drafted from the dev ticket, feeding the Tesztelési jegyzőkönyv): nusz-1.9.11.48-test-runbook — NÚSZ 1.9.11.48 payload (ASSNUSZ-76 webm/retention-cron + FKITDEV-8975 text) + devel-update regression by area + AI-Act (present, OFF by default).

Active releases

ReleaseClientTargetStatusHub
eSign 1.3.0.11instacashHarbor (eSign pipeline)PROD-approved (ASSICASH-96)instacash-esign-1.3.0.11
1.9.11.47 / @13nuszHarborplanningnusz-1.9.11.47
1.9.11.100raiffeisenunconfirmedcode on release branch, NOT tagged (ASSRAFIPI-135 / FKITDEV-9156)raiffeisen-1.9.11.100
1.9.11.102cibHarbor (cib-facekom)BLOCKED — cib@1 failed at the Harbor push 2026-09-04; source tags cib-1.9.11.102 in vuer_oss + vuer_css (ASSCIB-166 / FKITDEV-9197)cib-1.9.11.102

CIB 1.9.11.102 — cib@1 BUILT but could not PUBLISH

CIB’s first-ever vuer-release cut (commit ac8aa5cc55, tag cib@1, run 33855979398) built both images and logged into Harbor, then had docker push harbor.techteamer.com/cib-facekom/vuer_css:1.9.11.102.1-20221206 rejected. Root cause unconfirmed — hypothesis is that the cib-facekom Harbor project does not exist or the robot lacks push rights; needs a Harbor admin. cib@2 (adding portal_css 1.4.0.74) is prepared but uncommitted. The .102 changelog entry was never written in either repo and is deliberately left alone, since the source tags already point past it.

CIB 1.9.11.102 — merged by SQUASH, devel ancestry lost

Both release PRs (vuer_oss #8126, vuer_css #3152) were squash-merged, so devel is no longer an ancestor of customization/cib — the next devel→CIB update will re-present ~11 months / 334 commits as new changes with heavy conflicts. Tagged content is byte-identical to what was reviewed; only history shape changed. portal_css #712 is deliberately out of the train (components = vuer_oss + vuer_css per ASSCIB-166). See squash-merge-erases-partner-devel-ancestry.

Raiffeisen 1.9.11.100 — payload merged to a BRANCH, merge-back owed

FKITDEV-8827 (vuer_oss PR #7971) and FKITDEV-8787 (vuer_css PR #3064) both merged 2026-08-10 into chore/FKITDEV-9156-raiffeisen-release-1.9.11.100 — but raiffeisen-1.9.11.100 is not tagged, and neither fix is on customization/raiffeisen or devel. A new branch cut off customization/raiffeisen loses both. Note also that for this partner the customization/raiffeisen-targeted PRs (#3050/#3051) were closed unmerged in favour of release-branch PRs — so “merged” and “on the partner branch” are two different questions.

nusz release history (verified)

@Nversiondatenotes
@121.9.11.462026-04-27
@111.9.11.452026-04-21
@101.9.11.442026-04-14rebuild — same version as @9
@91.9.11.442026-04-10
@8——never created (UBI10-migration gap)
@71.9.11.432026-01-09”FIX EMAIL”
@61.9.11.422025-12-30”FIX NGINX GPG KEY”
@51.9.11.412025-12-01
@41.9.11.402025-10-22
@31.9.11.392025-10-09
@21.9.11.382025-09-29janus commit → 60ed394f
@11.9.11.382025-09-19initial

Model is client-generic; future releases (any client) get a note here.

release-automation-design · vuer-release-build-flow · vuer-release-cut-recipe · nusz-1.9.11.47 · client-registry · release-process · FaceKom

Graph View