@starci/eslint-canon-fe 9.14.3 → 9.14.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,9 @@
1
1
  # Changelog
2
2
 
3
+ ## 9.14.4 - 2026-11-05
4
+
5
+ - Changed: the runtime copy of the canon pins gives the Grammar family its same-minor range (decision grammar-patch-range) and names `@starci/hfs` 5.12.0 and the Grammar family 0.22.0.
6
+
3
7
  ## 9.14.3 - 2026-11-05
4
8
 
5
9
  - Changed: the runtime copy of the canon pins names `@starci/hfs` 5.11.3 and the Grammar family 0.21.38.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@starci/eslint-canon-fe",
3
- "version": "9.14.3",
3
+ "version": "9.14.4",
4
4
  "description": "Universal front-end lint laws for TypeScript and Next.js, independent of the selected Grammar family.",
5
5
  "type": "module",
6
6
  "license": "MIT",
@@ -1,7 +1,8 @@
1
1
  schema: starci/canon-pins@1
2
2
  purpose: >-
3
3
  The exact version of every shared dependency in the StarCi family, including package-owned runtime dependencies. One version per dependency for the whole
4
- family. The command line itself is not pinned here: an app's starci-harness is the version of the CLI that runs @starci/hfs to
4
+ family. The Grammar family alone also carries `range`, a same-minor range (~x.y.z) an app's exact pin must meet instead of `version`, which stays
5
+ the version a scaffold writes (decision grammar-patch-range): a Grammar patch then moves no other package. The command line itself is not pinned here: an app's starci-harness is the version of the CLI that runs @starci/hfs to
5
6
  judge or scaffold it (scripts/hfs/canon-pins.mjs), since that CLI depends on this package exactly. Raising a version is a change to this file first (with the package bump when it is a @starci package),
6
7
  then the repositories' own upgrade lane (each sets the exact version and reinstalls; nothing else installs a @starci package). Read on 2026-09-29 from the packages under
7
8
  .claude/packages and from the installed node_modules of the six product repositories; where they disagreed the
@@ -38,7 +39,8 @@ pins:
38
39
  source: packages/next-data/package.json
39
40
  why: 'the SWR data helpers of every front end (fe-stack data, owner:next-data-package): pollingRestart, the viewer and tenant key helpers, viewerSwrConfig and the viewer cache; each operation hook stays in the app and the package holds no component.'
40
41
  '@starci/grammar':
41
- version: 0.21.38
42
+ version: 0.22.0
43
+ range: '~0.22.0'
42
44
  group: starci
43
45
  install: registry
44
46
  side: fe
@@ -52,28 +54,30 @@ pins:
52
54
  source: packages/next-i18n/package.json
53
55
  why: 'the next-intl stack of every front end (fe-stack i18n, owner:next-i18n-package): defineI18n over the locales of the app, the locale-negotiating proxy, the locale-aware navigation, the request config that loads the catalogs of the app and the locale read of the [locale] layout; the app keeps its message catalogs and writes none of the stack.'
54
56
  '@starci/eslint-canon-be':
55
- version: 3.18.3
57
+ version: 3.18.4
56
58
  group: starci
57
59
  install: registry
58
60
  side: be
59
61
  source: packages/eslint-canon-be/package.json
60
62
  why: 'the back-end ESLint canon: `loadHfs(import.meta.url)` of be/eslint.config.mjs finds the app-root hfs.json (kind app) and gives every linted file the view of the be side, and the project graph is built per side; its bundled runtime copies (slots, canon-pins, failure codes, the architecture machine) put .starcistacks and .sops.yaml at the app root; `starciBeConfig({ hfs: loadHfs(import.meta.url) })` is the typed factory and the BE-CONVENTION laws are its rules.'
61
63
  '@starci/eslint-canon-fe':
62
- version: 9.14.3
64
+ version: 9.14.4
63
65
  group: starci
64
66
  install: registry
65
67
  side: fe
66
68
  source: packages/eslint-canon-fe/package.json
67
69
  why: 'the front-end ESLint canon: `loadHfs(import.meta.url)` of fe/eslint.config.mjs finds the app-root hfs.json (kind app) and gives every linted file the view of the fe side, and the project graph is built per side; its bundled runtime copies (slots, canon-pins, failure codes, the architecture machine) put .starcistacks and .sops.yaml at the app root; the front end has no tests (FE_NO_TESTS R97 in hfs) and no-vietnamese-in-source (R91) applies.'
68
70
  '@starci/eslint-grammar-core':
69
- version: 0.21.38
71
+ version: 0.22.0
72
+ range: '~0.22.0'
70
73
  group: starci
71
74
  install: registry
72
75
  side: fe
73
76
  source: packages/eslint-grammar-core/package.json
74
77
  why: 'the StarCi Grammar component API lint, versioned with @starci/grammar; front ends compose this family package with the universal FE canon.'
75
78
  '@starci/eslint-grammar-offset-pop':
76
- version: 0.21.38
79
+ version: 0.22.0
80
+ range: '~0.22.0'
77
81
  group: starci
78
82
  install: registry
79
83
  side: fe
@@ -155,7 +159,7 @@ pins:
155
159
  source: packages/mail/package.json
156
160
  why: 'outgoing mail of a back end: a NestJS module and the Mailer port over SMTP (connect, greeting, socket and total timeouts, STARTTLS required by default, recipient, message and attachment checks, a shared SMTP target policy, coded errors, typed escaping render helpers returning { subject, text, html }), with @starci/mail/testing for its specs; the only importer of nodemailer (R90).'
157
161
  '@starci/hfs':
158
- version: 5.11.3
162
+ version: 5.12.0
159
163
  group: starci
160
164
  install: registry
161
165
  side: both