Merge branch 'master' into da4/solid-primitive-is-skew

Author: dassaf4

.github/agents/electron-version-bump.agent.md

@@ -115,7 +115,9 @@ grep -r '"electron":' --include='package.json' -l .
 
 Compare the results with the list above and include any additional files found.
 
-### Step 3: Review and apply breaking changes
+### Step 3: Review breaking changes and get approval
+
+**This step requires explicit invoker approval before proceeding to file modifications.**
 
 Fetch the Electron breaking changes documentation. Use the raw URL to avoid GitHub rate limiting:
 
@@ -144,10 +146,7 @@ grep -r "require(\"electron\")" --include='*.ts' --include='*.js' -l .
 For each breaking change listed in the Electron docs for the new major version:
 
 1. **Identify** whether the breaking change affects any API used in this codebase.
-2. **If affected**, apply the necessary code fix:
-   - Search the codebase for all usages of the affected API.
-   - Update the code to use the new API or pattern as prescribed by the Electron breaking changes doc.
-   - Ensure backward compatibility with the minimum supported Electron version (currently ^35.0.0) — use feature detection or version checks when the old API is removed and a polyfill is needed.
+2. **If affected**, describe the required code fix and which files need modification.
 3. **If not affected**, note it and move on.
 
 **Common breaking change categories to watch for:**
@@ -159,6 +158,24 @@ For each breaking change listed in the Electron docs for the new major version:
 - New required permissions or security policy changes
 - Deprecated APIs that are now removed
 
+#### Present findings and wait for approval
+
+After completing the analysis, present a summary table to the invoker:
+
+| Breaking change | Affected? | Proposed fix |
+| --- | --- | --- |
+| (change description) | Yes / No | (fix description or "N/A") |
+
+**STOP here and wait for the invoker's explicit go-ahead before making any file changes.** If the invoker requests modifications to the proposed approach, incorporate their feedback before proceeding.
+
+#### Apply breaking change fixes (after approval)
+
+Once approved, for each affected breaking change:
+
+- Search the codebase for all usages of the affected API.
+- Update the code to use the new API or pattern as prescribed by the Electron breaking changes doc.
+- Ensure backward compatibility with the minimum supported Electron version documented in docs/learning/SupportedPlatforms.md — use feature detection or version checks when the old API is removed and a polyfill is needed.
+
 If a breaking change requires a non-trivial migration (e.g., architectural changes), document the issue in the report. If triggered from a GitHub issue, add a comment to the issue describing the blocker and wait for guidance. Otherwise, ask the invoker before proceeding with the fix.
 
 ### Step 3.5: Update `@itwin/electron-authorization` if needed
@@ -290,10 +307,13 @@ gh pr create \
   --head electron-<NEW_MAJOR> \
   --title "Add support for Electron <NEW_MAJOR>" \
   --body "$(cat <<'EOF'
-Adds support for Electron <NEW_MAJOR>.
-
 ### Breaking changes review
-<Include the breaking changes assessment here — list each change with "affected" / "not affected" status>
+
+<Include the breaking changes assessment table from Step 3 here>
+
+### Notes
+
+<Include any relevant notes, e.g. unmet peer dependencies>
 
 See [Electron <NEW_MAJOR> release blog](https://www.electronjs.org/blog/electron-<NEW_MAJOR>-0) for details.
 EOF

common/api/core-backend.api.md

@@ -694,7 +694,7 @@ export class BriefcaseManager {
     // @internal (undocumented)
     static getChangedElementsPathName(iModelId: GuidString): LocalFileName;
     // @internal
-    static getChangedInstancesDataForTxn(db: BriefcaseDb, txnId: string): AsyncGenerator<ChangeInstance>;
+    static getChangedInstancesDataForTxn(db: BriefcaseDb, txnId: string): AsyncGenerator<InstancePatch>;
     // @internal (undocumented)
     static getChangeSetsPath(iModelId: GuidString): LocalDirName;
     static getFileName(briefcase: BriefcaseProps): LocalFileName;
@@ -4589,6 +4589,9 @@ export class IModelNative {
     static get platform(): typeof IModelJsNative;
 }
 
+// @internal (undocumented)
+export const _implicitTxn: unique symbol;
+
 // @beta
 export type ImplicitWriteEnforcement = "allow" | "log" | "throw";
 
@@ -4679,6 +4682,12 @@ export interface InstanceChange {
     summaryId: Id64String;
 }
 
+// @internal
+export interface InstancePatch extends Omit<ChangeInstance, "$meta"> {
+    // (undocumented)
+    $meta: Pick<ChangeMeta, "op" | "stage" | "isIndirectChange">;
+}
+
 // @beta
 export interface IntegrityCheckOptions {
     quickCheck?: boolean;

common/api/summary/core-backend.exports.csv

@@ -367,6 +367,7 @@ public;class;IModelJsFs
 public;class;IModelJsFsStats
 public;interface;IModelNameArg
 internal;class;IModelNative
+internal;const;_implicitTxn
 beta;type;ImplicitWriteEnforcement
 public;class;InformationContentElement
 preview;class;InformationContentElement
@@ -386,6 +387,7 @@ internal;function;initializeTracing
 beta;interface;InlineGeometryPartsResult
 public;interface;InsertElementOptions
 beta;interface;InstanceChange
+internal;interface;InstancePatch
 beta;interface;IntegrityCheckOptions
 public;class;IpcHandler
 public;class;IpcHost

common/changes/@itwin/certa/electron-42_2026-05-07-09-14.json

@@ -0,0 +1,10 @@
+{
+  "changes": [
+    {
+      "packageName": "@itwin/certa",
+      "comment": "Add support for Electron 42",
+      "type": "none"
+    }
+  ],
+  "packageName": "@itwin/certa"
+}

common/changes/@itwin/core-backend/2026-05-08-16-02.json

@@ -0,0 +1,10 @@
+{
+  "changes": [
+    {
+      "packageName": "@itwin/core-backend",
+      "comment": "",
+      "type": "none"
+    }
+  ],
+  "packageName": "@itwin/core-backend"
+}

common/changes/@itwin/core-backend/nam-fix-linear-referencing-deep-import_2026-05-08-15-23.json

@@ -0,0 +1,10 @@
+{
+  "changes": [
+    {
+      "packageName": "@itwin/core-backend",
+      "comment": "",
+      "type": "none"
+    }
+  ],
+  "packageName": "@itwin/core-backend"
+}

common/changes/@itwin/core-backend/soham-improving-semantic-rebase-temp-file-size_2026-05-06-12-15.json

@@ -0,0 +1,10 @@
+{
+  "changes": [
+    {
+      "packageName": "@itwin/core-backend",
+      "comment": "Added batching while writing instance patches to the file during semantic rebase. Also reduced the $meta field in instance patches to include only the necessary properties and skip unnecessary ones.",
+      "type": "none"
+    }
+  ],
+  "packageName": "@itwin/core-backend"
+}

common/changes/@itwin/core-electron/electron-42_2026-05-07-09-14.json

@@ -0,0 +1,10 @@
+{
+  "changes": [
+    {
+      "packageName": "@itwin/core-electron",
+      "comment": "Add support for Electron 42",
+      "type": "none"
+    }
+  ],
+  "packageName": "@itwin/core-electron"
+}

common/changes/@itwin/linear-referencing-backend/nam-fix-linear-referencing-deep-import_2026-05-08-15-23.json

@@ -0,0 +1,10 @@
+{
+  "changes": [
+    {
+      "packageName": "@itwin/linear-referencing-backend",
+      "comment": "",
+      "type": "none"
+    }
+  ],
+  "packageName": "@itwin/linear-referencing-backend"
+}

common/config/azure-pipelines/templates/integration-test-steps.yaml

@@ -34,6 +34,23 @@ steps:
       node ./common/scripts/install-run-rush webpack:test -v
     displayName: "Rush build"
 
+  # Electron 42+ no longer downloads the binary during npm install (postinstall removed).
+  # Ensure the binary is present before configuring the AppArmor profile.
+  - script: |
+      ELECTRON_DIR=$(find $PWD/common/temp/node_modules/.pnpm -path "*/electron@*/node_modules/electron" -type d 2>/dev/null | head -n 1)
+      if [ ! -d "$ELECTRON_DIR" ]; then
+        echo "##vso[task.logissue type=warning]Unable to find Electron package directory"
+      elif [ -f "$ELECTRON_DIR/dist/electron" ]; then
+        echo "Electron binary already present"
+      elif [ -f "$ELECTRON_DIR/install.js" ]; then
+        echo "Downloading Electron binary..."
+        node "$ELECTRON_DIR/install.js"
+      else
+        echo "##vso[task.logissue type=warning]Unable to find Electron install script at $ELECTRON_DIR/install.js"
+      fi
+    displayName: "Ensure Electron binary is downloaded"
+    condition: and(succeededOrFailed(), eq(variables['Agent.OS'], 'Linux'))
+
   # Starting Ubuntu 24.04, unprivileged user namespaces are restricted by default via AppArmor.
   # Electron's sandbox requires user namespaces, so we create an AppArmor profile that grants the 'userns' permission to the Electron binary.
   # See: https://discourse.ubuntu.com/t/ubuntu-24-04-lts-noble-numbat-release-notes/39890#p-99950-unprivileged-user-namespace-restrictions-15