chore(sync): record nuxt/ui@2aa1702 as not applicable - #596
Merged
Merged
Conversation
Upstream appends a `v5:` rule to `.github/labeler.yml` so `actions/labeler` tags an incoming PR with the major version of the branch it targets. There is no labeler config here. `.github/` holds `ISSUE_TEMPLATE`, `PULL_REQUEST_TEMPLATE.md`, `contributing`, `dependabot.yml`, `scripts` and `workflows`, and nothing else; a grep for `labeler` or `base-branch` across the directory returns nothing, so no workflow consumes such a file either. And there are no major-version branches to label. This fork develops on `main` and ships from it — the sync tracks upstream's `v4` from the outside rather than mirroring their branch layout, so a `v5:` rule would name a branch that does not exist here. Worth noting for the sync rather than for this file: `.sync/nuxt-ui.json` tracks `v4`, and if upstream's development moves to `v5` the cursor stops advancing silently rather than loudly. Nothing to do yet — these four commits are still landing on `v4`. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JS8ypVfQSFzYVZzkTHhURb
IgorShevchik
added a commit
that referenced
this pull request
Sep 17, 2026
`packageManager` pnpm@11.20.0 → 12.4.2, and the lockfile pnpm 12 rewrites on the next install. The format is not migrated — `lockfileVersion` stays '9.0'. What changes is that the file becomes two YAML documents: doc 0 is new and holds pnpm managing itself (`configDependencies`, `packageManagerDependencies` and the 14 `@pnpm/exe.*` platform binaries), doc 1 is the previous file with `settings` and `overrides` intact. The result is structurally identical to upstream's: `---` at lines 1 and 158 in both, same top-level key order in both documents, valid multi-document YAML. No dependency moved. Extracting every `name@version` key from the lockfile before and after gives 2239 → 2254: 15 added (pnpm@12.4.2 and its 14 `@pnpm/exe.*` binaries), zero removed. The load-bearing pins were checked individually rather than inferred from that count, because each has an incident behind it — happy-dom 20.12.0 (the exact pin from the dep-parity bisection), vite 8.2.1, rolldown 1.2.3, tailwind-variants 3.2.2, @tiptap/pm 3.31.3, prosemirror-view 1.42.3, @nuxt/image 2.0.0, and a single @nuxtjs/mdc 0.23.1. All held. `pnpm install --frozen-lockfile` passes under 12.4.2 and prints an explicit supply-chain verification of 1801 entries. Nothing in the repo parses the lockfile, so the new `---` preamble cannot break a local tool; dep-parity.mjs reads the manifests and assert-lockfile-frozen.py reads the workflows, and both pass. All five workflows use `pnpm/action-setup` with no version input, so they follow `packageManager` — that line is the only place the version is named. One real failure, caught by a guard: `governance-files.spec.ts > CONTRIBUTING.md > quotes the pinned pnpm version` went red because CONTRIBUTING.md:58 still said 11.20.0. Updated to 12.4.2. No mutation was needed to show the guard is meaningful — it went red on a real bump and green on the real fix, which is what its docblock says it exists for. Left alone deliberately: the sentence in the content integration page about pnpm 11 removing `onlyBuiltDependencies` in favour of the approve-builds map. It describes when that happened, is still true, and `allowBuilds` still works under 12. Also closes a divergence: this fork was on 11.20.0 against upstream's 11.27.0, recorded in the 69b075aa log as predating that commit. Both trees are now on 12.4.2. Also reconciles the `2aa1702a` entry with #596 / 17b46d1. Claude-Session: https://claude.ai/code/session_01JS8ypVfQSFzYVZzkTHhURb Co-authored-by: Shevchik Igor <noreply@anthropic.com>
This was referenced Sep 17, 2026
IgorShevchik
added a commit
that referenced
this pull request
Sep 21, 2026
Upstream trims `renovate.json` down to what their shared preset already provides: `$schema` is added, and `timezone`, `schedule`, `lockFileMaintenance`, the `resolutions` package rule, `postUpdateOptions: [pnpmDedupe]` and `ignoreDeps: ["actions/stale"]` all go. That last removal is a follow-on from a581357a (#616, recorded n/a two commits ago), which deleted `stale.yml` — the action it pinned no longer exists to ignore. The file is not here. A grep for `renovate` across the tree, excluding node_modules, .git and .nuxt, matches only `.sync/log/*.md` — earlier journals describing upstream's renovate commits. Nothing in this repository is configured by, or refers to, renovate. And the policy it configures is not ours. Dependencies run through `.github/dependabot.yml`, whose own comments record the reasoning: github-actions only, monthly, grouped into one PR, with npm deliberately excluded because this repository tracks nuxt/ui and takes dependency bumps as ports of upstream's own through `.sync/`. A renovate config would duplicate that pipeline or compete with it. So there is no line here to update, and every removed key is about scheduling, lockfile maintenance and dedupe for a bot this fork does not run. Noted for the sync rather than for this file: that dependabot config already names the condition under which its npm exclusion should be revisited — if `cursor` stops advancing for a month while nuxt/ui@v4 moves. This commit changes nothing about that, and the cursor is current as of this run. Same shape as 2aa1702a (#596) and a581357a (#616): an upstream repository-process file with no counterpart here. Claude-Session: https://claude.ai/code/session_01JS8ypVfQSFzYVZzkTHhURb
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
2 participants
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.
Records
nuxt/ui@2aa1702a—chore(github): add v5 base branch to labeler (#6949)— as n/a.Journal:
.sync/log/2aa1702a9944444f5994be003af1b8af51af0dc2.mdFirst of four new upstream commits; the other three are being processed in order behind it.
Upstream change
Three lines appended to
.github/labeler.yml:actions/labelerreads this to tag an incoming PR with the major version of thebranch it targets. Upstream keeps one long-lived branch per major —
v2,v3,v4— and is openingv5.Why it does not apply
There is no labeler config.
.github/holdsISSUE_TEMPLATE,PULL_REQUEST_TEMPLATE.md,contributing,dependabot.yml,scriptsandworkflows, and nothing more. A grep forlabelerorbase-branchacross thewhole directory returns nothing, so no workflow consumes such a file either.
And there are no major-version branches to label. This fork develops on
mainand ships from it; the sync tracks upstream's
v4from the outside rather thanmirroring their branch layout. A
v5:rule here would name a branch that does notexist.
Worth flagging
Upstream opening
v5matters for the sync itself rather than for this file..sync/nuxt-ui.jsontracksbranch: "v4", so if upstream's development moves tov5the cursor will stop advancing silently rather than loudly — no error,just an empty queue that looks like "nothing new".
Nothing to do yet: all four of these commits landed on
v4, which is still theiractive branch. Recording it here so it is not a surprise later.
Gate
dev:prepare·lint·typecheck·build·test:coverage(353 files, 8067passed) ·
test:module— green..sync/dep-parity.jsonrefreshed; the diff is thecursorline alone, which isthe evidence that no dependency drifted.
Cursor advances
35c74bb4→2aa1702a. The35c74bb4entry was reconciled in #595.🤖 Generated with Claude Code
https://claude.ai/code/session_01JS8ypVfQSFzYVZzkTHhURb
Generated by Claude Code