chore(release): sync v1.7.0 to master

.changeset/README.md

@@ -6,3 +6,23 @@ find the full documentation for it [in our repository](https://github.com/change
 
 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).
+
+## How this repo is configured
+
+`config.json` cannot carry comments, so the two non-default settings are
+explained here.
+
+**`linked`** holds all four published packages. They are one product released
+together — `release.yml` writes a changeset for every package unless its
+`packages` input names a subset — but `core` had fewer releases early on and
+ended up a whole minor behind the three adapters (core 1.3.0 against adapter
+1.4.0). `linked` makes every package that is released in the same pass take the
+same version, which closes that gap once and keeps it closed. It is deliberately
+not `fixed`: a patch that only touches angular still must not bump and republish
+three packages whose tarballs did not change.
+
+**`onlyUpdatePeerDependentsWhenOutOfRange`** stops a core release from
+rewriting each adapter's `@dynamic-field-kit/core` peer range. The adapters use
+only core APIs that have existed since 1.3.0, so `^1.3.0` is the honest range —
+tightening it on every core release would force consumers to upgrade core for
+features their adapter does not call.

.changeset/config.json

@@ -3,9 +3,16 @@
   "changelog": "@changesets/cli/changelog",
   "commit": false,
   "fixed": [],
-  "linked": [],
+  "linked": [
+    [
+      "@dynamic-field-kit/core",
+      "@dynamic-field-kit/react",
+      "@dynamic-field-kit/vue",
+      "@dynamic-field-kit/angular"
+    ]
+  ],
   "access": "public",
-  "baseBranch": "master",
+  "baseBranch": "develop",
   "updateInternalDependencies": "patch",
   "___experimentalUnsafeOptions_WILL_CHANGE_IN_PATCH": {
     "onlyUpdatePeerDependentsWhenOutOfRange": true

.git-blame-ignore-revs

@@ -0,0 +1,14 @@
+# Revisions that only reformat. `git blame --ignore-revs-file .git-blame-ignore-revs`
+# skips them, and `git config blame.ignoreRevsFile .git-blame-ignore-revs` makes
+# that the default for this clone. GitHub reads this file automatically.
+#
+# Add a commit here only when it changes formatting and nothing else.
+#
+# Currently empty, deliberately. The prettier 2 -> 3 reformat (105 files, pure
+# formatting) was written as its own commit precisely so it could be listed
+# here, but #44 was squash-merged, so that commit does not exist on develop -
+# its changes are inside e4f8dbd alongside the vitest 4 and eslint 10
+# migrations. Listing e4f8dbd would hide the authorship of real changes, which
+# is the opposite of what this file is for, so the reformat stays visible in
+# blame. A future formatting-only commit should be merged without squashing and
+# added here.

.github/CODEOWNERS

@@ -0,0 +1,10 @@
+# Branch protection on master enables require_code_owner_reviews, which does
+# nothing without this file. Every path needs an owner for that rule to bite.
+* @vannt-dev
+
+# Anything that decides what ships, or what a release does.
+/.github/ @vannt-dev
+/.changeset/ @vannt-dev
+/scripts/ @vannt-dev
+package.json @vannt-dev
+package-lock.json @vannt-dev

.github/pull_request_template.md

@@ -0,0 +1,25 @@
+## What
+
+<!-- What changed, in one or two sentences. -->
+
+## Why
+
+<!-- The problem this solves. Link the issue if there is one. -->
+
+## How to test
+
+<!-- Commands or steps a reviewer can actually run. -->
+
+---
+
+- [ ] Added a changeset (`npx changeset`) if any package under `packages/` changed
+- [ ] Tests cover the change — a bug fix has a test that failed before it
+- [ ] Public API changes are reflected in the README / package README
+- [ ] Behaviour is consistent across react, vue and angular, or the difference is explained above
+
+<!--
+CI runs: lint, format, prod audit, build x4, typecheck, type tests,
+per-package tests with coverage floors, the three example apps, the built
+package smoke test, and the cross-framework verify scripts.
+Run locally with: npm run lint && npm run typecheck && npm test
+-->

.github/workflows/ci.yml

@@ -10,136 +10,42 @@ concurrency:
   cancel-in-progress: true
 
 jobs:
-  lint-and-build:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-
-      - name: Setup Node.js
-        uses: actions/setup-node@v4
-        with:
-          node-version: '20'
-          cache: 'npm'
-
-      - name: Install dependencies
-        run: npm ci
-
-      - name: Lint & Format
-        run: npm run lint && npm run format-check
-
-      - name: Build packages
-        run: |
-          npm run build --workspace=@dynamic-field-kit/core
-          npm run build --workspace=@dynamic-field-kit/react
-          npm run build --workspace=@dynamic-field-kit/vue
-          npm run build --workspace=@dynamic-field-kit/angular
-
-      # Share the built dist with the verify job so it doesn't rebuild all four
-      # packages (ng-packagr's Angular build especially). Common ancestor of the
-      # four paths is `packages`, so the artifact stores `<pkg>/dist/...`.
-      - name: Upload built dist
-        uses: actions/upload-artifact@v4
-        with:
-          name: package-dist
-          path: |
-            packages/core/dist
-            packages/react/dist
-            packages/vue/dist
-            packages/angular/dist
-          retention-days: 1
-          if-no-files-found: error
-
-      - name: Typecheck
-        run: npm run typecheck
-
-      - name: Type tests
-        run: npm run test:types --workspace=@dynamic-field-kit/core
-
-      - name: Show bundle sizes
-        run: node scripts/show-sizes.js
+  gates:
+    uses: ./.github/workflows/quality-gates.yml
 
-  test:
-    name: Test ${{ matrix.package }}
+  changeset:
+    name: Changeset present
     runs-on: ubuntu-latest
-    strategy:
-      fail-fast: false
-      matrix:
-        include:
-          - package: core
-            test-cmd: npm run test --workspace=@dynamic-field-kit/core -- --coverage
-            coverage-file: packages/core/coverage/lcov.info
-            coverage-name: core
-          - package: react
-            build-cmd: npm run build --workspace=@dynamic-field-kit/core
-            test-cmd: npm run test --workspace=@dynamic-field-kit/react -- --coverage
-            coverage-file: packages/react/coverage/lcov.info
-            coverage-name: react
-          - package: vue
-            build-cmd: npm run build --workspace=@dynamic-field-kit/core
-            test-cmd: npm run test --workspace=@dynamic-field-kit/vue -- --coverage
-            coverage-file: packages/vue/coverage/lcov.info
-            coverage-name: vue
-          - package: angular
-            build-cmd: npm run build --workspace=@dynamic-field-kit/core
-            test-cmd: npm run test --workspace=@dynamic-field-kit/angular -- --coverage
-            coverage-file: packages/angular/coverage/lcov.info
-            coverage-name: angular
+    # Only PRs into develop can be missing a changeset, because develop is where
+    # unreleased work accumulates. Skipped elsewhere:
+    #
+    # - the release PR changesets itself opens, which consumes the changesets
+    #   and bumps versions, so it changes packages while legitimately having
+    #   none left;
+    # - any PR into master, which carries changes that were already released
+    #   from develop - their changesets are gone by definition, and demanding a
+    #   new one would mean releasing the same work twice.
+    if: >-
+      github.event_name == 'pull_request' &&
+      github.base_ref == 'develop' &&
+      !startsWith(github.head_ref, 'changeset-release/')
     steps:
-      - uses: actions/checkout@v4
-
-      - name: Setup Node.js
-        uses: actions/setup-node@v4
-        with:
-          node-version: '20'
-          cache: 'npm'
-
-      - name: Install dependencies
-        run: npm ci
-
-      - name: Build core
-        if: matrix.build-cmd != ''
-        run: ${{ matrix.build-cmd }}
-
-      - name: Run tests
-        run: ${{ matrix.test-cmd }}
-
-      - name: Upload coverage
-        if: matrix.coverage-file != '' && success()
-        uses: codecov/codecov-action@v4
+      - uses: actions/checkout@v7
         with:
-          files: ${{ matrix.coverage-file }}
-          flags: unittests
-          name: ${{ matrix.coverage-name }}
-          fail_ci_if_error: false
-
-  verify:
-    runs-on: ubuntu-latest
-    needs: [lint-and-build, test]
-    steps:
-      - uses: actions/checkout@v4
+          # changeset status diffs against the base branch, so it needs history.
+          fetch-depth: 0
 
       - name: Setup Node.js
-        uses: actions/setup-node@v4
+        uses: actions/setup-node@v7
         with:
-          node-version: '20'
+          node-version-file: '.nvmrc'
           cache: 'npm'
 
       - name: Install dependencies
         run: npm ci
 
-      # Reuse the dist built by lint-and-build instead of rebuilding all four
-      # packages. Extract into `packages/` so paths become packages/<pkg>/dist.
-      - name: Download built dist
-        uses: actions/download-artifact@v4
-        with:
-          name: package-dist
-          path: packages
-
-      - name: Smoke test built packages
-        run: npm run test --workspace=@dynamic-field-kit/smoke
-
-      - name: Run verification scripts
-        run: |
-          node scripts/verify-framework-deps.js
-          node scripts/check-cross-framework-imports.js
-          node scripts/integration-cross-registry.js
+      # Fails when a PR changes a publishable package without adding a
+      # changeset, which would otherwise merge and silently never be released.
+      # Add one with `npx changeset`.
+      - name: Check for a changeset
+        run: npx changeset status --since=origin/${{ github.base_ref }}