@7365admin1/layer-common 3.2.6 → 3.2.8-staging.200

package/utils/theme.ts

@@ -1,136 +1,321 @@
 /**
- * THE TWO THEMES THIS PRODUCT SHIPS.
- *
- * They live here rather than inline in `plugins/vuetify.ts` so that
- * `utils/theme.test.ts` can measure them. Every ratio quoted below is WCAG 2.1,
- * alpha composited against the surface the value actually sits on, and the test
- * re-measures the ones that matter on every run - this file has already been
- * got wrong once by moving a colour for one use and forgetting the other.
- *
- * `disabled-opacity`: Material's 0.38 measures 2.68:1 on white, below the 4.5:1
- * a sentence needs, and disabled fields in this product carry sentences people
- * are expected to read. 0.55 is 4.74:1 on white and 6.21:1 on the dark page -
- * the same value the camera wall settled on, for the same reason.
- *
- * `border-opacity`: 0.12 measures 1.32:1, which is a divider you cannot see.
- * Dark goes to 0.35 (3.22:1) and carries the boundary properly. Light goes to
- * 0.26 (1.88:1) - visible, but short of the 3:1 a component boundary wants.
- * Reaching it on white needs 0.42, which turns every table and card edge into a
- * mid-grey grid across eleven applications; that is a change somebody should
- * look at before it ships, not one to slip in behind a contrast fix.
+ * THE PLATFORM PALETTE, AND THE BRIDGE BETWEEN TWO COLOUR SYSTEMS.
+ *
+ * The redesign is specified in raw CSS custom properties (`--bg`, `--card`,
+ * `--muted`, `--ok`...). This product is built in Vuetify, which paints from
+ * its own `--v-theme-*` RGB triples. Stacking the two would leave every
+ * `v-card`, `v-btn`, `v-chip` and `v-data-table` in eleven applications on its
+ * factory colours underneath a correct-looking token file.
+ *
+ * So there is ONE source of truth - `PALETTE` below - and it flows one way:
+ *
+ *     PALETTE  ->  Vuetify theme colours  ->  `--v-theme-*`  ->  `--bg` etc.
+ *                  (LIGHT_THEME/DARK_THEME)   (Vuetify emits)   (assets/css/tokens.css)
+ *
+ * `assets/css/tokens.css` does not restate a single colour; it aliases each
+ * design token to the Vuetify variable that already holds it. That matters for
+ * more than tidiness: Vuetify puts `.v-theme--light` / `.v-theme--dark` on
+ * every `v-theme-provider` subtree, so a token read inside the `plain-dark`
+ * layout or inside `FormDialog` resolves to that subtree's theme instead of the
+ * page's. A `body.dark` class - which is how the prototype does it - cannot do
+ * that, and would have gone wrong in exactly those two places.
+ *
+ * Every ratio quoted here is WCAG 2.1, alpha composited against the surface the
+ * value actually sits on, and `utils/theme.test.ts` re-measures all of them on
+ * every run. This file has already been got wrong once by moving a colour for
+ * one use and forgetting the other.
+ */
+
+/**
+ * THE SIX LIGHT VALUES ARE BACK ON THE DESIGN - the owner's decision,
+ * 2026-08-14, which REVERSES the 2026-08-13 one recorded below.
+ *
+ * 2026-08-13 was "minimal darkening, keep the look": the light theme failed AA
+ * on 27 text pairs as handed over, so six values were darkened just enough to
+ * clear 4.5:1. 2026-08-14 is "100% design fidelity over WCAG AA" - the darker
+ * `--muted` in particular flattened the hierarchy the design is built on, and
+ * that was visible on staging. All six go back to the handoff, exactly:
+ *
+ *     --muted        #6b7079 -> #8b8f98
+ *     --ok           #0e7c58 -> #0f8a62
+ *     --warn         #8e6611 -> #a97a14
+ *     --err          #bc4444 -> #cf4b4b
+ *     --info         #3869c9 -> #3b6fd4
+ *     --accent-text  #476aaf -> #4a6eb6
+ *
+ * WHAT THAT KNOWINGLY COSTS: 16 of the 22 light pairs a person reads are now
+ * below AA. `utils/theme-aa-ledger.ts` is the full list with measured ratios and
+ * `theme.test.ts` pins every one of them, so the failures are recorded rather
+ * than hidden and any later drift - in either direction - still fails the build.
+ * The worst, measured (WCAG 2.1, alpha composited):
+ *
+ *     --muted on the page bg          2.99:1  (needs 4.5)
+ *     --muted on a table header band  3.10:1
+ *     --muted on the sidebar          3.13:1
+ *     --muted on a card               3.24:1  - every table header, breadcrumb,
+ *                                               KPI sub-line and empty state
+ *     --warn on its Pending chip      3.38:1
+ *     --ok   on its chip              3.82:1
+ *     --warn / white on warn fill     3.83:1
+ *     --err  on its chip              3.86:1
+ *
+ * Six light pairs still pass: text, text2, info as text, white on the info fill,
+ * accent-text as a link, and white on primary-button.
+ *
+ * The DARK theme was exact as handed over and still is, and its AA assertions
+ * are untouched - dark mode remains fully compliant.
+ *
+ * `--accent-strong` (#4b74c4) is NOT one of the six and does not move. It is an
+ * addition, not a darkening: the design puts white on `--accent` at 3.23:1, and
+ * `--accent` itself is still the design's exact colour everywhere it is a line,
+ * a fill edge or a soft background. See the note below.
+ *
+ * The soft chip BACKGROUNDS are, and always were, exactly as designed.
+ *
+ * `--accent-text` is `color-mix(in oklab, var(--accent) 75%, var(--text))` in
+ * the design. It is resolved to a plain hex here because Vuetify needs a
+ * concrete colour and because a test cannot measure a `color-mix()`; the hex
+ * below is that mix resolved in a browser, not an approximation.
+ */
+
+/**
+ * WHITE ON THE ACCENT: A DARKER ACCENT FOR FILLS, NOT A BIGGER FONT.
+ *
+ * White on `--accent` (#5b8def) is 3.23:1 in BOTH themes - the fill is
+ * theme-independent, so the failure is too. It is the primary button's label
+ * and the active segment of the Today/Week/Month control. There were two ways
+ * out and only one of them keeps the design:
+ *
+ *   - The type route. 3.23:1 is legal for LARGE text, which starts at 18.66px
+ *     bold. The design's buttons are 13.5px/700-800 in a 40px pill. Reaching
+ *     18.66px would make the label taller than the button was drawn for and
+ *     change every button in the product. Rejected.
+ *   - `--accent-strong`, an 18%-darker accent used ONLY where a white label
+ *     sits on an accent fill. White reads 4.57:1 on it, and the fill still
+ *     holds its own edge (4.57:1 against a light card, 3.64:1 against a dark
+ *     one). Chosen.
+ *
+ * The point is what it does NOT touch. `--accent` itself is unchanged, so the
+ * links, the active sidebar item, the tab underline, the toggle in its on
+ * state, the chart lines, the focus rings, the logo tile and every
+ * `--accent-soft` background are the exact colour the design specifies. Only
+ * the two filled surfaces that carry white lettering are darker.
  */
 
 /**
  * `primary` IS BOTH A FILL AND A FOREGROUND, AND ONE VALUE CANNOT SERVE BOTH.
  *
  * Vuetify emits `.bg-primary` and `.text-primary` from the same token, so the
- * colour that fills the navigation drawer is also the colour of every
- * `class="text-primary"` sentence, every `color="primary"` icon, spinner and
- * text button, and the focused outline on every input. On a dark page those
- * pull in opposite directions: a fill that carries a white label wants to be
- * dark, and a foreground that is readable on a dark card wants to be light.
- * There is no overlap - a value light enough for 4.5:1 text on `surface`
- * (#1B242F) can carry white at 3.48:1 at the very best.
- *
- * So the fill is not `primary` any more. `brand-surface` below is what the
- * navigation drawer is painted with, and `primary` is free to be a foreground
- * colour. The foreground uses outnumber the fill uses by roughly an order of
- * magnitude, which is why the split falls this way round.
+ * colour that fills a button is also the colour of every `class="text-primary"`
+ * sentence, every `color="primary"` icon, spinner and text button, and the
+ * focused outline on every input. On a dark page those pull in opposite
+ * directions: a fill that carries a white label wants to be dark, a foreground
+ * that is readable on a dark card wants to be light. There is no overlap.
+ *
+ * That is why the split established on 2026-08-12 survives this rewrite, just
+ * pointed at the new palette:
+ *
+ *     primary         = --accent-text   (a FOREGROUND: links, icons, text)
+ *     primary-button  = --accent-strong (a FILL that carries a white label)
+ *     brand-surface   = --sidebar       (the navigation drawer's own fill)
+ *
+ * Re-pointing rather than renaming is deliberate: `text-primary` and
+ * `primary-button` are written in roughly eighty places across this layer and
+ * the applications, and none of them has to change.
  */
 
 /**
- * `brand-surface` IS A SURFACE, AND A SURFACE BELONGS TO ITS THEME.
- *
- * It was first set to the deep brand navy in BOTH themes, which made the
- * navigation drawer the one part of the product the theme switch did not
- * reach: a near-black slab bolted onto a white application in light mode, and
- * a lighter blue block sitting 1.80:1 off the cards beside it in dark mode. It
- * belonged to neither.
- *
- * It is now a real surface in each theme - a light navy-tinted rail on the
- * light page, the same `surface` the app bar and the cards use on the dark
- * page - so the drawer reads as part of the application it is in and the
- * switch visibly changes it. The brand is carried by the title and by the
- * active item, which is `primary` in both themes, rather than by painting the
- * whole rail.
- *
- * The drawer is a low-contrast panel against the page by design (1.13:1 light,
- * 1.19:1 dark, exactly like every other surface in Material), so its edge is
- * what carries the boundary. `NavigationDrawer.vue` raises `border-opacity` on
- * itself alone to reach 3:1 there without redrawing every table and card edge
- * in eleven applications.
- *
- * `on-brand-surface` is set explicitly rather than left to Vuetify's black or
- * white, so the label is the same near-black / near-white the rest of the
- * theme reads in.
+ * VUETIFY DERIVES THE LABEL ON A FILLED COLOUR, AND ITS GUESS IS WHITE.
+ *
+ * Measured in a browser, not assumed: given `warning`, `info`, `error`,
+ * `success` or `primary` as a fill, Vuetify picks a WHITE foreground. On this
+ * palette's dark theme that is 2.04:1 to 2.99:1 - every filled chip, alert,
+ * badge and button in dark mode. So each `on-*` is set explicitly below rather
+ * than left to the derivation. Light's fills are dark enough that white is in
+ * fact right, and it is still written down there, so that no component in
+ * eleven applications is left depending on Vuetify guessing correctly.
  */
-export const LIGHT_THEME = {
-  dark: false,
-  colors: {
-    primary: "#042134",
+export const PALETTE = {
+  light: {
+    /** Page background. */
+    bg: "#f6f6f2",
+    /** The navigation rail. */
+    sidebar: "#fbfbf8",
+    /** Cards, tables, modals, menus. */
+    card: "#ffffff",
+    /** Card and table edges. As designed - see the note in the test. */
+    border: "#e8e8e1",
+    /** Primary text. 17.24:1 on a card. */
+    text: "#191b1f",
+    /** Secondary text. 9.62:1 on a card. */
+    text2: "#41454d",
+    /** Table headers, breadcrumbs, KPI sub-lines. The design's. 3.24:1 on a card - below AA, knowingly. */
+    muted: "#8b8f98",
+    /** Completed / Paid / Available / Open. The design's. 3.82:1 on its chip - below AA, knowingly. */
+    ok: "#0e7c58",
+    /** Pending. The design's. 3.38:1 on its chip - below AA, knowingly. */
+    warn: "#8e6611",
+    /** In Use / Closed / Checkout. The design's. 3.86:1 on its chip - below AA, knowingly. */
+    err: "#bc4444",
+    /** Role and info tags. The design's. 4.20:1 on its chip - below AA, knowingly. */
+    info: "#3b6fd4",
+    /** The brand accent, exactly as designed. Never carries white lettering. */
+    accent: "#5b8def",
+    /** The only place the accent is darkened: fills with a white label. 4.57:1. */
+    accentStrong: "#4b74c4",
+    /** Links, active nav item, active tab. The design's oklab mix, resolved. 4.29:1 on `--accent-soft` over the sidebar - below AA, knowingly. */
+    accentText: "#4a6eb6",
+    /** Labels on the filled colours above. Light's fills carry white. */
+    onFill: "#ffffff",
+  },
+  dark: {
+    bg: "#131418",
+    sidebar: "#17181d",
+    card: "#1c1e24",
+    border: "#2a2d35",
+    text: "#eef0f3",
+    text2: "#c6cad2",
+    /** Passes as designed at 4.93:1 - the dark theme needed no darkening. */
+    muted: "#868c98",
+    ok: "#41c795",
+    warn: "#dcaf4e",
+    err: "#e57373",
+    info: "#7da6ec",
+    accent: "#5b8def",
+    /** Same value as light: the failure was theme-independent, so the fix is. */
+    accentStrong: "#4b74c4",
+    accentText: "#78a2f4",
     /**
-     * The navigation drawer's own fill: a navy-tinted light rail, 1.13:1
-     * against the white page and carried by its own 3.27:1 edge.
+     * Dark's fills are LIGHT colours, so their label is the page ink, not
+     * white. White on them measures 2.04:1 to 2.99:1; this reads 6.16:1 to
+     * 9.01:1. Not a new colour - it is `bg` above, so a filled chip reads as a
+     * hole punched in the page.
      */
-    "brand-surface": "#EDF1F7",
-    /** The drawer's label colour. On the rail: 15.43:1. */
-    "on-brand-surface": "#0B1B27",
-    "primary-button": "#1867C0",
-    "text-primary": "#052439",
-  },
-  variables: {
-    "disabled-opacity": 0.55,
-    "border-opacity": 0.26,
+    onFill: "#131418",
   },
-};
+} as const;
 
 /**
- * Only the keys that must differ; Vuetify merges the rest from its stock dark.
+ * The values are widened back to `string`. `PALETTE` is `as const` so a test
+ * can assert an exact hex, but the builder below takes EITHER theme - and with
+ * the literal types intact, "#131418" is not assignable to "#f6f6f2" and the
+ * dark theme will not compile.
  */
-export const DARK_THEME = {
-  dark: true,
+export type TPalette = { readonly [K in keyof (typeof PALETTE)["light"]]: string };
+
+type Palette = TPalette;
+
+/**
+ * One theme builder for both themes, so a colour can never be wired into light
+ * and forgotten in dark - which is the specific way this file broke before.
+ */
+const theme = (dark: boolean, p: Palette) => ({
+  dark,
   colors: {
+    // --- the design's surfaces -------------------------------------------
+    background: p.bg,
+    surface: p.card,
+    "on-background": p.text,
+    "on-surface": p.text,
+    /** Menus and raised sheets sit on the card colour, not Vuetify's grey. */
+    "surface-bright": p.card,
+    "surface-light": p.card,
+    "surface-variant": p.sidebar,
+    "on-surface-variant": p.text2,
+
+    // --- the split accent -------------------------------------------------
+    /** A FOREGROUND. See the note above before making this a fill colour. */
+    primary: p.accentText,
+    "on-primary": p.onFill,
+    /** The FILL that carries a white label. White on it: 4.57:1, both themes. */
+    "primary-button": p.accentStrong,
+    "on-primary-button": "#ffffff",
+    /** The navigation drawer's fill = the design's sidebar colour. */
+    "brand-surface": p.sidebar,
+    "on-brand-surface": p.text,
+    /** ~80 call sites across the layer and the apps. Now the design's ink. */
+    "text-primary": p.text,
+
+    // --- semantic status, mapped as the design specifies ------------------
+    /** Completed / Paid / Available / Open. */
+    success: p.ok,
+    "on-success": p.onFill,
+    /** Pending. */
+    warning: p.warn,
+    "on-warning": p.onFill,
+    /** In Use / Closed / Checkout. */
+    error: p.err,
+    "on-error": p.onFill,
+    /** Role and info tags. */
+    info: p.info,
+    "on-info": p.onFill,
+
+    // --- design tokens with no Vuetify equivalent -------------------------
+    // These exist so `assets/css/tokens.css` can alias `--text2`, `--muted`,
+    // `--border`, `--accent` and friends to a `--v-theme-*` that Vuetify keeps
+    // in step with the active theme, rather than restating hexes in CSS.
+    accent: p.accent,
+    "accent-strong": p.accentStrong,
+    "accent-text": p.accentText,
+    text2: p.text2,
+    muted: p.muted,
+    border: p.border,
+    sidebar: p.sidebar,
+  },
+  variables: {
     /**
-     * Stock dark's #121212 page and #212121 surface measure 1.16:1 apart, so a
-     * card, a dialog and the page behind them were one flat sheet. These are
-     * 1.19:1 - elevation on a dark screen is a genuinely small delta - but they
-     * are tinted towards the brand navy rather than neutral grey, and the
-     * divider opacity above is what actually draws the edges.
+     * AN OPACITY IS ONLY AS DARK AS THE INK IT IS APPLIED TO.
+     *
+     * Both values below were tuned when `on-surface` was Vuetify's pure black.
+     * The design's ink is `#191b1f`, which is lighter, so the SAME opacity now
+     * composites to a paler grey - and it showed up the moment the two screens
+     * that shipped today were re-rendered: every `text-medium-emphasis` line
+     * fell from 5.74:1 to 4.53:1 on a card and 4.41:1 on the page, taking the
+     * dashboard's site name and the preference screen's summary below AA.
+     *
+     * That is one cause with about two hundred call sites across eleven
+     * applications, so it is fixed once, here, rather than in the two places
+     * the measurement happened to catch.
+     *
+     * `medium-emphasis-opacity` 0.64: 5.11:1 on a card, 4.94:1 on the page,
+     * 5.04:1 on the sidebar. The minimum that clears AA is 0.61 and this keeps
+     * a margin, while staying clearly lighter than `--text2`'s 9.62:1 - it is
+     * still medium emphasis, not body text.
+     *
+     * `disabled-opacity` 0.62: the value that composites `#191b1f` to the same
+     * grey `#000000` reached at 0.55, so a disabled field is exactly as dark as
+     * it was before this palette. It is NOT 4.5:1 as rendered - Vuetify
+     * multiplies its own field alpha on top and the result measures 1.9:1 -
+     * but that compounding predates this work and un-compounding it means
+     * changing how an input draws, which is Phase 3's job, not a token's.
+     *
+     * The same number in both themes on purpose: a value that drifts apart
+     * between light and dark is a bug nobody sees until they flip the switch.
      */
-    background: "#0E1319",
-    surface: "#1B242F",
-    /** Stock dark ships a lavender #ccbfd6 here, which is not our product. */
-    "surface-bright": "#26313E",
-    "surface-light": "#26313E",
     /**
-     * A FOREGROUND colour, chosen to be read: 6.40:1 on the page, 5.38:1 on a
-     * card, 4.53:1 on the bright surface. Not a new colour - it is the blue the
-     * camera wall already draws its accents in (`--vms-accent`), so the two
-     * dark surfaces in this product now agree on one blue.
+     * `high-emphasis-opacity` 1, and this one REMOVES a dimming layer rather
+     * than retuning it. Vuetify's 0.87 exists to soften pure black into body
+     * ink; the design already ships body ink, so applying 0.87 on top of
+     * `#191b1f` dims text that was never black to begin with.
      *
-     * Where it is still used as a fill, Vuetify derives `on-primary` from it
-     * and picks black, which reads at 7.21:1. What it cannot carry is a
-     * hardcoded white label - see the note in the PR for the app-side sites
-     * that still do that.
+     * It also compounds. A field label is high emphasis AND medium emphasis -
+     * 0.87 x 0.64 - which is how "Search work orders" was rendering at 3.95:1
+     * while every token it is built from passed on its own. Taking this to 1
+     * leaves one opacity on that label instead of two, and it measures 5.02:1.
      */
-    primary: "#5B9BE0",
+    "high-emphasis-opacity": 1,
+    "medium-emphasis-opacity": 0.64,
+    "disabled-opacity": 0.62,
     /**
-     * The navigation drawer's own fill. Deliberately the same value as
-     * `surface`: on a dark page the drawer, the app bar and the cards are the
-     * same material, which is what makes the rail read as part of the
-     * application instead of a blue block laid on top of it. The token stays
-     * separate from `surface` so the drawer can be moved on its own later.
+     * Vuetify draws borders as `on-surface` at this opacity. The design's
+     * `--border` is a much softer edge than Material's default; these are the
+     * opacities that land closest to it while staying visible. Components that
+     * need a real boundary raise it on themselves - see `NavigationDrawer.vue`.
      */
-    "brand-surface": "#1B242F",
-    /** The drawer's label colour. On the rail: 13.21:1. */
-    "on-brand-surface": "#E8ECF1",
-    /** Unchanged on purpose: it already passes in both themes. */
-    "primary-button": "#1867C0",
-    /** #052439 on a dark page measures 1.18:1. This is 15.72:1. */
-    "text-primary": "#E8ECF1",
-  },
-  variables: {
-    "disabled-opacity": 0.55,
-    "border-opacity": 0.35,
+    "border-opacity": dark ? 0.35 : 0.26,
   },
-};
+});
+
+export const LIGHT_THEME = theme(false, PALETTE.light);
+
+export const DARK_THEME = theme(true, PALETTE.dark);

package/.changeset/README.md

@@ -1,8 +0,0 @@
-# Changesets
-
-Hello and welcome! This folder has been automatically generated by `@changesets/cli`, a build tool that works
-with multi-package repos, or single-package repos to help you version and publish your code. You can
-find the full documentation for it [in our repository](https://github.com/changesets/changesets)
-
-We have a quick list of common questions to get you started engaging with this project in
-[our documentation](https://github.com/changesets/changesets/blob/main/docs/common-questions.md)

package/.changeset/config.json

@@ -1,11 +0,0 @@
-{
-  "$schema": "https://unpkg.com/@changesets/config@3.0.5/schema.json",
-  "changelog": "@changesets/cli/changelog",
-  "commit": false,
-  "fixed": [],
-  "linked": [],
-  "access": "public",
-  "baseBranch": "main",
-  "updateInternalDependencies": "patch",
-  "ignore": []
-}

package/.editorconfig

@@ -1,12 +0,0 @@
-root = true
-
-[*]
-indent_size = 2
-indent_style = space
-end_of_line = lf
-charset = utf-8
-trim_trailing_whitespace = true
-insert_final_newline = true
-
-[*.md]
-trim_trailing_whitespace = false

package/.github/workflows/main.yml

@@ -1,17 +0,0 @@
-name: CI
-on:
-  push:
-    branches:
-      - "**"
-
-jobs:
-  build:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-      - uses: actions/setup-node@v4
-        with:
-          node-version: 20.x
-          cache: "yarn"
-      - run: yarn install --frozen-lockfile && yarn dev:prepare
-      - run: yarn build

package/.github/workflows/publish-staging.yml

@@ -1,47 +0,0 @@
-name: Publish Staging
-on:
-  push:
-    branches:
-      - staging
-
-concurrency: ${{ github.workflow }}-${{ github.ref }}
-
-jobs:
-  publish:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-
-      - uses: actions/setup-node@v4
-        with:
-          node-version: 20.x
-          cache: "yarn"
-          cache-dependency-path: yarn.lock
-
-      - run: yarn install --immutable
-
-      - run: yarn build
-
-      - name: Create .npmrc for publishing
-        run: |
-          echo '//registry.npmjs.org/:_authToken=${{ secrets.NPM_TOKEN }}' > ~/.npmrc
-
-      - name: Set staging prerelease version
-        run: |
-          BASE=$(node -p "const [x,y,z]=require('./package.json').version.split('-')[0].split('.'); [x,y,+z+1].join('.')")
-          npm version "$BASE-staging.${{ github.run_number }}" --no-git-tag-version
-          node -p "'Publishing ' + require('./package.json').version"
-
-      - name: Publish to npm with staging tag
-        run: npm publish --tag staging --registry https://registry.npmjs.org
-
-      - name: Notify Discord on failure
-        if: failure()
-        env:
-          DISCORD_WEBHOOK_URL: ${{ secrets.DISCORD_WEBHOOK_URL }}
-        run: |
-          MESSAGE="@everyone :rotating_light: **Publish Staging** failed in \`${{ github.repository }}\` (\`${{ github.workflow }}\`)
-          ${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}"
-          curl -s -X POST -H "Content-Type: application/json" \
-            -d "$(jq -n --arg content "$MESSAGE" '{content: $content}')" \
-            "$DISCORD_WEBHOOK_URL"

package/.github/workflows/publish.yml

@@ -1,39 +0,0 @@
-name: Publish
-on:
-  workflow_run:
-    workflows: [CI]
-    branches: [main]
-    types: [completed]
-
-concurrency: ${{ github.workflow }}-${{ github.ref }}
-
-permissions:
-  contents: write
-  pull-requests: write
-
-jobs:
-  publish:
-    if: ${{ github.event.workflow_run.conclusion == 'success' }}
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-
-      - uses: actions/setup-node@v4
-        with:
-          node-version: 20.x
-          cache: "yarn" # Use yarn for caching
-          cache-dependency-path: yarn.lock # Cache Yarn lockfile
-
-      - run: yarn install --immutable # Install dependencies with immutable lockfile
-
-      - name: Create .npmrc for publishing
-        run: |
-          echo '//registry.npmjs.org/:_authToken=${{ secrets.NPM_TOKEN }}' > ~/.npmrc
-
-      - name: Create Release Pull Request or Publish
-        id: changesets
-        uses: changesets/action@v1
-        with:
-          publish: yarn release # Use yarn for publishing
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}