fix: edge indexes become invalid when deleting and recreating same ed… by robfrank · Pull Request #3512 · ArcadeData/arcadedb

robfrank · 2026-02-23T12:31:56Z

fix: edge indexes become invalid when deleting and recreating same edge (Edge indexes become invalid in certain scenario #2 #3097)

In TransactionIndexContext.addIndexKeyLock(), when a unique index entry is deleted (REMOVE) and recreated (ADD) with the same key within the same transaction on the same bucket-level index, the REMOVE entry was silently replaced by a REPLACE entry — losing the old RID. At commit time the old persisted index entry was never removed, causing stale entries to accumulate. After 2+ iterations, checkUniqueIndexKeys detected >2 entries for the same unique key and threw DuplicatedKeyException.

Fix: store the old RID in the REPLACE entry (IndexKey.oldRid). At commit time, call index.remove(key, oldRid) for REPLACE entries with a non-null oldRid to properly clean up the old persisted entry. Also fix getTxDeletedEntries() to use oldRid as the deleted RID for correctness in checkUniqueIndexKeys. Update TxForwardRequest serialization to include oldRid for HA replication.

fix: propagate oldRid through chained REPLACE operations (Edge indexes become invalid in certain scenario #2 #3097)

When the same unique key undergoes REMOVE → ADD → ADD in the same transaction on the same bucket, the second ADD finds an existing REPLACE entry. The oldRid from that REPLACE must be propagated to the new REPLACE so the original persisted index entry is still properly removed at commit time.

test: assert edge count equals 1 after delete-recreate loop (Edge indexes become invalid in certain scenario #2 #3097)

(cherry picked from commit dffb415)

…ge (#3097) (#3482) * fix: edge indexes become invalid when deleting and recreating same edge (#3097) In TransactionIndexContext.addIndexKeyLock(), when a unique index entry is deleted (REMOVE) and recreated (ADD) with the same key within the same transaction on the same bucket-level index, the REMOVE entry was silently replaced by a REPLACE entry — losing the old RID. At commit time the old persisted index entry was never removed, causing stale entries to accumulate. After 2+ iterations, checkUniqueIndexKeys detected >2 entries for the same unique key and threw DuplicatedKeyException. Fix: store the old RID in the REPLACE entry (IndexKey.oldRid). At commit time, call index.remove(key, oldRid) for REPLACE entries with a non-null oldRid to properly clean up the old persisted entry. Also fix getTxDeletedEntries() to use oldRid as the deleted RID for correctness in checkUniqueIndexKeys. Update TxForwardRequest serialization to include oldRid for HA replication. * fix: propagate oldRid through chained REPLACE operations (#3097) When the same unique key undergoes REMOVE → ADD → ADD in the same transaction on the same bucket, the second ADD finds an existing REPLACE entry. The oldRid from that REPLACE must be propagated to the new REPLACE so the original persisted index entry is still properly removed at commit time. * test: assert edge count equals 1 after delete-recreate loop (#3097) (cherry picked from commit dffb415)

gemini-code-assist · 2026-02-23T12:32:32Z

Summary of Changes

Hello @robfrank, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request resolves a critical issue where unique edge indexes could become invalid after an edge was deleted and then immediately recreated within the same transaction. The fix ensures that the database correctly tracks and cleans up the original record IDs during these REPLACE operations, preventing the accumulation of stale index entries and avoiding DuplicatedKeyException errors. This significantly improves the reliability and data integrity of transactional operations involving unique edge indexes.

Highlights

Index Key Tracking Enhancement: Introduced an oldRid field in TransactionIndexContext.IndexKey to correctly track the original Record ID during index key replacements, especially for REPLACE operations resulting from same-bucket REMOVE → ADD merges.
Transactional Index Cleanup: Modified the transaction commit process to explicitly remove the oldRid from persisted indexes when a REPLACE operation with a non-null oldRid is encountered, preventing stale index entries.
Old RID Propagation: Enhanced addIndexKeyLock to save the oldRid from a REMOVE operation when it merges into a REPLACE operation, and to propagate the oldRid through chained REPLACE operations (e.g., REMOVE → ADD → ADD).
Accurate Deleted Entry Detection: Updated getTxDeletedEntries to use the oldRid for REPLACE entries, ensuring that checkUniqueIndexKeys correctly identifies the actual deleted RID for unique index validation.
HA Replication Support: Extended TxForwardRequest serialization and deserialization to include the oldRid for REPLACE index keys, ensuring proper High Availability replication of these transactional changes.
Regression Test Addition: Added a new test case, EdgeIndexDuplicateKeyTest, which repeatedly deletes and recreates an edge within transactions, asserting that no DuplicatedKeyException is thrown and the final edge count remains correct.
Version Updates: Updated the parent POM version across all modules to 26.2.2-SNAPSHOT.
NPM Audit Configuration: Adjusted the npm audit configuration in the studio module, changing the security-check script's audit level to none and commenting out the npm audit execution block in studio/pom.xml.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

bolt/pom.xml
- Updated parent version to 26.2.2-SNAPSHOT.
console/pom.xml
- Updated parent version to 26.2.2-SNAPSHOT.
coverage/pom.xml
- Updated parent version to 26.2.2-SNAPSHOT.
e2e-perf/pom.xml
- Updated parent version to 26.2.2-SNAPSHOT.
e2e/pom.xml
- Updated parent version to 26.2.2-SNAPSHOT.
engine/pom.xml
- Updated parent version to 26.2.2-SNAPSHOT.
engine/src/main/java/com/arcadedb/database/TransactionIndexContext.java
- Added oldRid field to IndexKey class.
- Modified commit() method to remove oldRid for REPLACE operations.
- Updated addIndexKeyLock() to store and propagate oldRid for REPLACE entries.
- Adjusted getTxDeletedEntries() to use oldRid for REPLACE entries.
engine/src/test/java/com/arcadedb/graph/EdgeIndexDuplicateKeyTest.java
- Imported Result and assertThat.
- Converted database.command("sql", ...) to database.command("sqlscript", """...""") for schema creation and edge operations.
- Added a loop to perform delete and recreate operations multiple times.
- Added an assertion to verify the final edge count is 1.
graphql/pom.xml
- Updated parent version to 26.2.2-SNAPSHOT.
gremlin/pom.xml
- Updated parent version to 26.2.2-SNAPSHOT.
grpc-client/pom.xml
- Updated parent version to 26.2.2-SNAPSHOT.
grpc/pom.xml
- Updated parent version to 26.2.2-SNAPSHOT.
grpcw/pom.xml
- Updated parent version to 26.2.2-SNAPSHOT.
integration/pom.xml
- Updated parent version to 26.2.2-SNAPSHOT.
metrics/pom.xml
- Updated parent version to 26.2.2-SNAPSHOT.
mongodbw/pom.xml
- Updated parent version to 26.2.2-SNAPSHOT.
network/pom.xml
- Updated parent version to 26.2.2-SNAPSHOT.
package/pom.xml
- Updated parent version to 26.2.2-SNAPSHOT.
pom.xml
- Updated parent version to 26.2.2-SNAPSHOT.
postgresw/pom.xml
- Updated parent version to 26.2.2-SNAPSHOT.
redisw/pom.xml
- Updated parent version to 26.2.2-SNAPSHOT.
server/pom.xml
- Updated parent version to 26.2.2-SNAPSHOT.
server/src/main/java/com/arcadedb/server/ha/message/TxForwardRequest.java
- Added serialization of oldRid for REPLACE index keys.
- Added deserialization of oldRid for REPLACE index keys.
studio/package.json
- Modified the security-check script to use --audit-level=none.
studio/pom.xml
- Commented out the npm audit execution block.
test-utils/pom.xml
- Updated parent version to 26.2.2-SNAPSHOT.

Activity

No human activity has been recorded on this pull request yet.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	`/gemini review`	Performs a code review for the current pull request in its current state.
Pull Request Summary	`/gemini summary`	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	`/gemini help`	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

gemini-code-assist

Code Review

This pull request successfully addresses a bug concerning edge index invalidation when an edge is deleted and recreated within the same transaction. The core logic changes in TransactionIndexContext.java are sound and effectively fix the issue by tracking the old record ID. The necessary updates for High Availability replication in TxForwardRequest.java are also correctly implemented. The accompanying test case has been significantly improved and now robustly verifies the fix.

However, I've identified two high-severity security issues related to disabling the npm audit checks for frontend dependencies in studio/pom.xml and studio/package.json. These changes weaken the project's security posture and should be reverted. I've also included a medium-severity suggestion to improve code readability in TransactionIndexContext.java.

gemini-code-assist · 2026-02-23T12:34:11Z

studio/package.json

    "update": "npm update",
    "outdated": "npm outdated",
-    "security-check": "npm audit --audit-level=moderate",
+    "security-check": "npm audit --audit-level=none",


The security-check script has been changed to use npm audit --audit-level=none. This setting reports vulnerabilities but does not fail the build, effectively weakening the security gate. The previous setting of --audit-level=moderate is recommended to ensure that vulnerabilities of moderate severity or higher are addressed before merging.

Suggested change

"security-check": "npm audit --audit-level=none",

"security-check": "npm audit --audit-level=moderate",

gemini-code-assist · 2026-02-23T12:34:11Z

studio/pom.xml

+<!--                    <execution>-->
+<!--                        <id>npm audit</id>-->
+<!--                        <goals>-->
+<!--                            <goal>npm</goal>-->
+<!--                        </goals>-->
+<!--                        <phase>compile</phase>-->
+<!--                        <configuration>-->
+<!--                            <arguments>audit &#45;&#45;audit-level=none</arguments>-->
+<!--                        </configuration>-->
+<!--                    </execution>-->


The npm audit execution has been commented out, which disables security vulnerability scanning for frontend dependencies during the Maven build process. This poses a security risk by potentially allowing known vulnerabilities into the application. It is strongly recommended to re-enable this check. The corresponding security-check script in package.json has also been weakened. Both should be reverted to maintain security standards.

Suggested change





















<execution>

<id>npm audit</id>

<goals>

<goal>npm</goal>

</goals>

<phase>compile</phase>

<configuration>

<arguments>audit --audit-level=moderate</arguments>

</configuration>

</execution>

gemini-code-assist · 2026-02-23T12:34:11Z

engine/src/main/java/com/arcadedb/database/TransactionIndexContext.java

+                final RID deletedRid = (entry.getValue().operation == IndexKey.IndexKeyOperation.REPLACE && entry.getValue().oldRid != null)
+                    ? entry.getValue().oldRid
+                    : entry.getKey().rid;
+                entries.put(key, deletedRid);


For improved readability and maintainability, this dense ternary operator can be refactored into a more explicit if-else block.

final RID deletedRid; if (entry.getValue().operation == IndexKey.IndexKeyOperation.REPLACE && entry.getValue().oldRid != null) { deletedRid = entry.getValue().oldRid; } else { deletedRid = entry.getKey().rid; } entries.put(key, deletedRid);

mergify · 2026-02-23T12:34:46Z

🧪 CI Insights

Here's what we observed from your CI run for 7c24bf9.

🟢 All jobs passed!

But CI Insights is watching 👀

codacy-production · 2026-02-23T17:58:55Z

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation	Diff coverage
Report missing for `ced6531`¹	✅ 59.09%

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (`ced6531`)	Report Missing	Report Missing	Report Missing
Head commit (`d4308e1`)	85725	61930	72.24%

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#3512)	22	13	59.09%

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings Change summary preferences

Codacy didn't receive coverage data for the commit, or there was an error processing the received data. Check your integration for errors and validate that your coverage setup is correct. ↩

codecov · 2026-02-23T18:51:10Z

Codecov Report

❌ Patch coverage is 36.36364% with 14 lines in your changes missing coverage. Please review.
✅ Project coverage is 63.27%. Comparing base (02cf473) to head (d4308e1).
⚠️ Report is 99 commits behind head on main.

Files with missing lines	Patch %	Lines
...m/arcadedb/server/ha/message/TxForwardRequest.java	0.00%	8 Missing and 2 partials ⚠️
...com/arcadedb/database/TransactionIndexContext.java	66.66%	1 Missing and 3 partials ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3512      +/-   ##
==========================================
+ Coverage   62.87%   63.27%   +0.40%     
==========================================
  Files        1295     1295              
  Lines       85705    85725      +20     
  Branches    17619    17630      +11     
==========================================
+ Hits        53884    54246     +362     
+ Misses      24151    23821     -330     
+ Partials     7670     7658      -12

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Bumps [pg](https://github.com/brianc/node-postgres/tree/HEAD/packages/pg) from 8.18.0 to 8.19.0. Changelog *Sourced from [pg's changelog](https://github.com/brianc/node-postgres/blob/master/CHANGELOG.md).* > pg@8.19.0 > --------- > > * [Deprecate interal query queue](https://redirect.github.com/brianc/node-postgres/pull/3603). > * Pass connection parameters [to password callback](https://redirect.github.com/brianc/node-postgres/pull/3602). Commits * [`f2d7d11`](brianc/node-postgres@f2d7d11) Publish * [`5a4bafc`](brianc/node-postgres@5a4bafc) Deprecate Client's internal query queue ([#3603](https://github.com/brianc/node-postgres/tree/HEAD/packages/pg/issues/3603)) * [`a215bfb`](brianc/node-postgres@a215bfb) Typo fix in PgPass deprecation (funciton) ([#3605](https://github.com/brianc/node-postgres/tree/HEAD/packages/pg/issues/3605)) * [`01e0556`](brianc/node-postgres@01e0556) fix(pg-query-stream): invoke `this.callback` on cursor end/error ([#2810](https://github.com/brianc/node-postgres/tree/HEAD/packages/pg/issues/2810)) * [`e6e3692`](brianc/node-postgres@e6e3692) Pass connection parameters to password callback ([#3602](https://github.com/brianc/node-postgres/tree/HEAD/packages/pg/issues/3602)) * [`d80d883`](brianc/node-postgres@d80d883) test: Fix TLS connection test ending too early * [`f332f28`](brianc/node-postgres@f332f28) fix: Connection timeout handling for native clients in connected state ([#3512](https://github.com/brianc/node-postgres/tree/HEAD/packages/pg/issues/3512)) * [`b2e9cb1`](brianc/node-postgres@b2e9cb1) Remove testAsync - its redundant ([#3588](https://github.com/brianc/node-postgres/tree/HEAD/packages/pg/issues/3588)) * [`46cdf9e`](brianc/node-postgres@46cdf9e) [fix] fix unhandled callback error for submittables ([#3589](https://github.com/brianc/node-postgres/tree/HEAD/packages/pg/issues/3589)) * See full diff in [compare view](https://github.com/brianc/node-postgres/commits/pg@8.19.0/packages/pg) [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility\_score?dependency-name=pg&package-manager=npm\_and\_yarn&previous-version=8.18.0&new-version=8.19.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps the github-actions group with 5 updates: | Package | From | To | | --- | --- | --- | | [anthropics/claude-code-action](https://github.com/anthropics/claude-code-action) | `1.0.64` | `1.0.70` | | [github/codeql-action](https://github.com/github/codeql-action) | `4.32.4` | `4.32.6` | | [dorny/test-reporter](https://github.com/dorny/test-reporter) | `2.5.0` | `2.6.0` | | [actions/setup-node](https://github.com/actions/setup-node) | `6.2.0` | `6.3.0` | | [actions/dependency-review-action](https://github.com/actions/dependency-review-action) | `4.8.3` | `4.9.0` | Updates `anthropics/claude-code-action` from 1.0.64 to 1.0.70 Release notes *Sourced from [anthropics/claude-code-action's releases](https://github.com/anthropics/claude-code-action/releases).* > v1.0.70 > ------- > > **Full Changelog**: <anthropics/claude-code-action@v1...v1.0.70> > > v1.0.69 > ------- > > **Full Changelog**: <anthropics/claude-code-action@v1...v1.0.69> > > v1.0.68 > ------- > > **Full Changelog**: <anthropics/claude-code-action@v1...v1.0.68> > > v1.0.67 > ------- > > What's Changed > -------------- > > * Improve gh.sh wrapper: stricter validation and better error messages by [`@OctavianGuzu`](https://github.com/OctavianGuzu) in [anthropics/claude-code-action#996](https://redirect.github.com/anthropics/claude-code-action/pull/996) > > **Full Changelog**: <anthropics/claude-code-action@v1...v1.0.67> > > v1.0.66 > ------- > > What's Changed > -------------- > > * Only expose permission\_denials count in sanitized output by [`@ddworken`](https://github.com/ddworken) in [anthropics/claude-code-action#993](https://redirect.github.com/anthropics/claude-code-action/pull/993) > > **Full Changelog**: <anthropics/claude-code-action@v1...v1.0.66> > > v1.0.65 > ------- > > What's Changed > -------------- > > * Change the default `display_report` option to false to restrict exposed data by [`@ddworken`](https://github.com/ddworken) in [anthropics/claude-code-action#992](https://redirect.github.com/anthropics/claude-code-action/pull/992) > > **Full Changelog**: <anthropics/claude-code-action@v1...v1.0.65> Commits * [`26ec041`](anthropics/claude-code-action@26ec041) chore: bump Claude Code to 2.1.70 and Agent SDK to 0.2.70 * [`1fc90f3`](anthropics/claude-code-action@1fc90f3) chore: bump Claude Code to 2.1.69 and Agent SDK to 0.2.69 * [`e763fe7`](anthropics/claude-code-action@e763fe7) chore: bump Claude Code to 2.1.68 and Agent SDK to 0.2.68 * [`5f8e5bf`](anthropics/claude-code-action@5f8e5bf) chore: bump Claude Code to 2.1.66 and Agent SDK to 0.2.66 * [`7336720`](anthropics/claude-code-action@7336720) Improve gh.sh wrapper: stricter validation and better error messages ([#996](https://redirect.github.com/anthropics/claude-code-action/issues/996)) * [`64c7a0e`](anthropics/claude-code-action@64c7a0e) Only expose permission\_denials count in sanitized output ([#993](https://redirect.github.com/anthropics/claude-code-action/issues/993)) * [`220272d`](anthropics/claude-code-action@220272d) Change the default `display_report` option to false to restrict exposed data ... * See full diff in [compare view](anthropics/claude-code-action@ba7fa4b...26ec041) Updates `github/codeql-action` from 4.32.4 to 4.32.6 Release notes *Sourced from [github/codeql-action's releases](https://github.com/github/codeql-action/releases).* > v4.32.6 > ------- > > * Update default CodeQL bundle version to [2.24.3](https://github.com/github/codeql-action/releases/tag/codeql-bundle-v2.24.3). [#3548](https://redirect.github.com/github/codeql-action/pull/3548) > > v4.32.5 > ------- > > * Repositories owned by an organization can now set up the `github-codeql-disable-overlay` custom repository property to disable [improved incremental analysis for CodeQL](https://redirect.github.com/github/roadmap/issues/1158). First, create a custom repository property with the name `github-codeql-disable-overlay` and the type "True/false" in the organization's settings. Then in the repository's settings, set this property to `true` to disable improved incremental analysis. For more information, see [Managing custom properties for repositories in your organization](https://docs.github.com/en/organizations/managing-organization-settings/managing-custom-properties-for-repositories-in-your-organization). This feature is not yet available on GitHub Enterprise Server. [#3507](https://redirect.github.com/github/codeql-action/pull/3507) > * Added an experimental change so that when [improved incremental analysis](https://redirect.github.com/github/roadmap/issues/1158) fails on a runner — potentially due to insufficient disk space — the failure is recorded in the Actions cache so that subsequent runs will automatically skip improved incremental analysis until something changes (e.g. a larger runner is provisioned or a new CodeQL version is released). We expect to roll this change out to everyone in March. [#3487](https://redirect.github.com/github/codeql-action/pull/3487) > * The minimum memory check for improved incremental analysis is now skipped for CodeQL 2.24.3 and later, which has reduced peak RAM usage. [#3515](https://redirect.github.com/github/codeql-action/pull/3515) > * Reduced log levels for best-effort private package registry connection check failures to reduce noise from workflow annotations. [#3516](https://redirect.github.com/github/codeql-action/pull/3516) > * Added an experimental change which lowers the minimum disk space requirement for [improved incremental analysis](https://redirect.github.com/github/roadmap/issues/1158), enabling it to run on standard GitHub Actions runners. We expect to roll this change out to everyone in March. [#3498](https://redirect.github.com/github/codeql-action/pull/3498) > * Added an experimental change which allows the `start-proxy` action to resolve the CodeQL CLI version from feature flags instead of using the linked CLI bundle version. We expect to roll this change out to everyone in March. [#3512](https://redirect.github.com/github/codeql-action/pull/3512) > * The previously experimental changes from versions 4.32.3, 4.32.4, 3.32.3 and 3.32.4 are now enabled by default. [#3503](https://redirect.github.com/github/codeql-action/pull/3503), [#3504](https://redirect.github.com/github/codeql-action/pull/3504) Changelog *Sourced from [github/codeql-action's changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md).* > CodeQL Action Changelog > ======================= > > See the [releases page](https://github.com/github/codeql-action/releases) for the relevant changes to the CodeQL CLI and language packs. > > [UNRELEASED] > ------------ > > No user facing changes. > > 4.32.6 - 05 Mar 2026 > -------------------- > > * Update default CodeQL bundle version to [2.24.3](https://github.com/github/codeql-action/releases/tag/codeql-bundle-v2.24.3). [#3548](https://redirect.github.com/github/codeql-action/pull/3548) > > 4.32.5 - 02 Mar 2026 > -------------------- > > * Repositories owned by an organization can now set up the `github-codeql-disable-overlay` custom repository property to disable [improved incremental analysis for CodeQL](https://redirect.github.com/github/roadmap/issues/1158). First, create a custom repository property with the name `github-codeql-disable-overlay` and the type "True/false" in the organization's settings. Then in the repository's settings, set this property to `true` to disable improved incremental analysis. For more information, see [Managing custom properties for repositories in your organization](https://docs.github.com/en/organizations/managing-organization-settings/managing-custom-properties-for-repositories-in-your-organization). This feature is not yet available on GitHub Enterprise Server. [#3507](https://redirect.github.com/github/codeql-action/pull/3507) > * Added an experimental change so that when [improved incremental analysis](https://redirect.github.com/github/roadmap/issues/1158) fails on a runner — potentially due to insufficient disk space — the failure is recorded in the Actions cache so that subsequent runs will automatically skip improved incremental analysis until something changes (e.g. a larger runner is provisioned or a new CodeQL version is released). We expect to roll this change out to everyone in March. [#3487](https://redirect.github.com/github/codeql-action/pull/3487) > * The minimum memory check for improved incremental analysis is now skipped for CodeQL 2.24.3 and later, which has reduced peak RAM usage. [#3515](https://redirect.github.com/github/codeql-action/pull/3515) > * Reduced log levels for best-effort private package registry connection check failures to reduce noise from workflow annotations. [#3516](https://redirect.github.com/github/codeql-action/pull/3516) > * Added an experimental change which lowers the minimum disk space requirement for [improved incremental analysis](https://redirect.github.com/github/roadmap/issues/1158), enabling it to run on standard GitHub Actions runners. We expect to roll this change out to everyone in March. [#3498](https://redirect.github.com/github/codeql-action/pull/3498) > * Added an experimental change which allows the `start-proxy` action to resolve the CodeQL CLI version from feature flags instead of using the linked CLI bundle version. We expect to roll this change out to everyone in March. [#3512](https://redirect.github.com/github/codeql-action/pull/3512) > * The previously experimental changes from versions 4.32.3, 4.32.4, 3.32.3 and 3.32.4 are now enabled by default. [#3503](https://redirect.github.com/github/codeql-action/pull/3503), [#3504](https://redirect.github.com/github/codeql-action/pull/3504) > > 4.32.4 - 20 Feb 2026 > -------------------- > > * Update default CodeQL bundle version to [2.24.2](https://github.com/github/codeql-action/releases/tag/codeql-bundle-v2.24.2). [#3493](https://redirect.github.com/github/codeql-action/pull/3493) > * Added an experimental change which improves how certificates are generated for the authentication proxy that is used by the CodeQL Action in Default Setup when [private package registries are configured](https://docs.github.com/en/code-security/how-tos/secure-at-scale/configure-organization-security/manage-usage-and-access/giving-org-access-private-registries). This is expected to generate more widely compatible certificates and should have no impact on analyses which are working correctly already. We expect to roll this change out to everyone in February. [#3473](https://redirect.github.com/github/codeql-action/pull/3473) > * When the CodeQL Action is run [with debugging enabled in Default Setup](https://docs.github.com/en/code-security/how-tos/scan-code-for-vulnerabilities/troubleshooting/troubleshooting-analysis-errors/logs-not-detailed-enough#creating-codeql-debugging-artifacts-for-codeql-default-setup) and [private package registries are configured](https://docs.github.com/en/code-security/how-tos/secure-at-scale/configure-organization-security/manage-usage-and-access/giving-org-access-private-registries), the "Setup proxy for registries" step will output additional diagnostic information that can be used for troubleshooting. [#3486](https://redirect.github.com/github/codeql-action/pull/3486) > * Added a setting which allows the CodeQL Action to enable network debugging for Java programs. This will help GitHub staff support customers with troubleshooting issues in GitHub-managed CodeQL workflows, such as Default Setup. This setting can only be enabled by GitHub staff. [#3485](https://redirect.github.com/github/codeql-action/pull/3485) > * Added a setting which enables GitHub-managed workflows, such as Default Setup, to use a [nightly CodeQL CLI release](https://github.com/dsp-testing/codeql-cli-nightlies) instead of the latest, stable release that is used by default. This will help GitHub staff support customers whose analyses for a given repository or organization require early access to a change in an upcoming CodeQL CLI release. This setting can only be enabled by GitHub staff. [#3484](https://redirect.github.com/github/codeql-action/pull/3484) > > 4.32.3 - 13 Feb 2026 > -------------------- > > * Added experimental support for testing connections to [private package registries](https://docs.github.com/en/code-security/how-tos/secure-at-scale/configure-organization-security/manage-usage-and-access/giving-org-access-private-registries). This feature is not currently enabled for any analysis. In the future, it may be enabled by default for Default Setup. [#3466](https://redirect.github.com/github/codeql-action/pull/3466) > > 4.32.2 - 05 Feb 2026 > -------------------- > > * Update default CodeQL bundle version to [2.24.1](https://github.com/github/codeql-action/releases/tag/codeql-bundle-v2.24.1). [#3460](https://redirect.github.com/github/codeql-action/pull/3460) > > 4.32.1 - 02 Feb 2026 > -------------------- > > * A warning is now shown in Default Setup workflow logs if a [private package registry is configured](https://docs.github.com/en/code-security/how-tos/secure-at-scale/configure-organization-security/manage-usage-and-access/giving-org-access-private-registries) using a GitHub Personal Access Token (PAT), but no username is configured. [#3422](https://redirect.github.com/github/codeql-action/pull/3422) > * Fixed a bug which caused the CodeQL Action to fail when repository properties cannot successfully be retrieved. [#3421](https://redirect.github.com/github/codeql-action/pull/3421) > > 4.32.0 - 26 Jan 2026 > -------------------- > > * Update default CodeQL bundle version to [2.24.0](https://github.com/github/codeql-action/releases/tag/codeql-bundle-v2.24.0). [#3425](https://redirect.github.com/github/codeql-action/pull/3425) > > 4.31.11 - 23 Jan 2026 > --------------------- > > * When running a Default Setup workflow with [Actions debugging enabled](https://docs.github.com/en/actions/how-tos/monitor-workflows/enable-debug-logging), the CodeQL Action will now use more unique names when uploading logs from the Dependabot authentication proxy as workflow artifacts. This ensures that the artifact names do not clash between multiple jobs in a build matrix. [#3409](https://redirect.github.com/github/codeql-action/pull/3409) ... (truncated) Commits * [`0d579ff`](github/codeql-action@0d579ff) Merge pull request [#3551](https://redirect.github.com/github/codeql-action/issues/3551) from github/update-v4.32.6-72d2d850d * [`d4c6be7`](github/codeql-action@d4c6be7) Update changelog for v4.32.6 * [`72d2d85`](github/codeql-action@72d2d85) Merge pull request [#3548](https://redirect.github.com/github/codeql-action/issues/3548) from github/update-bundle/codeql-bundle-v2.24.3 * [`23f983c`](github/codeql-action@23f983c) Merge pull request [#3544](https://redirect.github.com/github/codeql-action/issues/3544) from github/dependabot/github\_actions/dot-github/wor... * [`832e97c`](github/codeql-action@832e97c) Merge pull request [#3545](https://redirect.github.com/github/codeql-action/issues/3545) from github/dependabot/github\_actions/dot-github/wor... * [`5ef38c0`](github/codeql-action@5ef38c0) Merge pull request [#3546](https://redirect.github.com/github/codeql-action/issues/3546) from github/dependabot/npm\_and\_yarn/tar-7.5.10 * [`80c9cda`](github/codeql-action@80c9cda) Add changelog note * [`f2669dd`](github/codeql-action@f2669dd) Update default bundle to codeql-bundle-v2.24.3 * [`bd03c44`](github/codeql-action@bd03c44) Merge branch 'main' into dependabot/github\_actions/dot-github/workflows/actio... * [`102d762`](github/codeql-action@102d762) Bump tar from 7.5.7 to 7.5.10 * Additional commits viewable in [compare view](github/codeql-action@89a39a4...0d579ff) Updates `dorny/test-reporter` from 2.5.0 to 2.6.0 Release notes *Sourced from [dorny/test-reporter's releases](https://github.com/dorny/test-reporter/releases).* > v2.6.0 > ------ > > We updated all dependency packages to latest versions to fix reported security vulnerabilities. > > What's Changed > -------------- > > * Fix: For `workflow_run` events, resolve the commit of the check run from related pull request head commits first (matching `workflow_run.head_branch`, then first PR), and fall back to `workflow_run.head_sha` for non-PR runs [dorny/test-reporter#673](https://redirect.github.com/dorny/test-reporter/pull/673) > * Change: The `test-reporter` action will listed all artifacts associated with the build run [dorny/test-reporter#693](https://redirect.github.com/dorny/test-reporter/pull/693) > * Maintenance: Upgrade to ESLint v9 [dorny/test-reporter#629](https://redirect.github.com/dorny/test-reporter/pull/629) > > New Contributors > ---------------- > > * [`@azchohfi`](https://github.com/azchohfi) made their first contribution in [dorny/test-reporter#673](https://redirect.github.com/dorny/test-reporter/pull/673) > > **Full Changelog**: <dorny/test-reporter@v2.5.0...v2.6.0> Changelog *Sourced from [dorny/test-reporter's changelog](https://github.com/dorny/test-reporter/blob/main/CHANGELOG.md).* > Changelog > ========= > > 2.6.0 > ----- > > * Fix: For `workflow_run` events, resolve the commit of the check run from related pull request head commits first (matching `workflow_run.head_branch`, then first PR), and fall back to `workflow_run.head_sha` for non-PR runs [dorny/test-reporter#673](https://redirect.github.com/dorny/test-reporter/pull/673) > * Change: The `test-reporter` action will listed all artifacts associated with the build run [dorny/test-reporter#693](https://redirect.github.com/dorny/test-reporter/pull/693) > * Maintenance: Upgrade to ESLint v9 [dorny/test-reporter#629](https://redirect.github.com/dorny/test-reporter/pull/629) > > 2.5.0 > ----- > > * Feature: Add Nette Tester support with `tester-junit` reporter [dorny/test-reporter#707](https://redirect.github.com/dorny/test-reporter/pull/707) > * Maintenance: Bump actions/upload-artifact from 5 to 6 [dorny/test-reporter#695](https://redirect.github.com/dorny/test-reporter/pull/695) > > 2.4.0 > ----- > > * Feature: Add PHPUnit support with JUnit XML dialect parser [dorny/test-reporter#422](https://redirect.github.com/dorny/test-reporter/pull/422) > * Feature: Add JUnit XML sample files and tests for validation [dorny/test-reporter#701](https://redirect.github.com/dorny/test-reporter/pull/701) > * Fix: Refactor deprecated `String.substr()` function to use `String.substring()` [dorny/test-reporter#704](https://redirect.github.com/dorny/test-reporter/pull/704) > > 2.3.0 > ----- > > * Feature: Add Python support with `python-xunit` reporter (pytest) [dorny/test-reporter#643](https://redirect.github.com/dorny/test-reporter/pull/643) > * Feature: Add pytest traceback parsing and `directory-mapping` option [dorny/test-reporter#238](https://redirect.github.com/dorny/test-reporter/pull/238) > * Performance: Update sax.js to fix large XML file parsing [dorny/test-reporter#681](https://redirect.github.com/dorny/test-reporter/pull/681) > * Documentation: Complete documentation for all supported reporters [dorny/test-reporter#691](https://redirect.github.com/dorny/test-reporter/pull/691) > * Security: Bump js-yaml and mocha in /reports/mocha (fixes prototype pollution) [dorny/test-reporter#682](https://redirect.github.com/dorny/test-reporter/pull/682) > > 2.2.0 > ----- > > * Feature: Add collapsed option to control report summary visibility [dorny/test-reporter#664](https://redirect.github.com/dorny/test-reporter/pull/664) > * Fix badge encoding for values including underscore and hyphens [dorny/test-reporter#672](https://redirect.github.com/dorny/test-reporter/pull/672) > * Fix missing `report-title` attribute in action definition [dorny/test-reporter#637](https://redirect.github.com/dorny/test-reporter/pull/637) > * Refactor variable names to fix shadowing issues [dorny/test-reporter#630](https://redirect.github.com/dorny/test-reporter/pull/630) > > 2.1.1 > ----- > > * Fix error when a TestMethod element does not have a className attribute in a trx file [dorny/test-reporter#623](https://redirect.github.com/dorny/test-reporter/pull/623) > * Add stack trace from trx to summary [dorny/test-reporter#615](https://redirect.github.com/dorny/test-reporter/pull/615) > * List only failed tests [dorny/test-reporter#606](https://redirect.github.com/dorny/test-reporter/pull/606) > * Add type definitions to `github-utils.ts` [dorny/test-reporter#604](https://redirect.github.com/dorny/test-reporter/pull/604) > * Avoid split on undefined [dorny/test-reporter#258](https://redirect.github.com/dorny/test-reporter/pull/258) > * Return links to summary report [dorny/test-reporter#588](https://redirect.github.com/dorny/test-reporter/pull/588) > * Add step summary short summary [dorny/test-reporter#589](https://redirect.github.com/dorny/test-reporter/pull/589) > * Fix for empty TRX TestDefinitions [dorny/test-reporter#582](https://redirect.github.com/dorny/test-reporter/pull/582) > * Increase step summary limit to 1MiB [dorny/test-reporter#581](https://redirect.github.com/dorny/test-reporter/pull/581) > * Fix input description for list options [dorny/test-reporter#572](https://redirect.github.com/dorny/test-reporter/pull/572) > > 2.1.0 > ----- > > * Feature: Add summary title [dorny/test-reporter#568](https://redirect.github.com/dorny/test-reporter/pull/568) > * Feature: Add Golang test parser [dorny/test-reporter#571](https://redirect.github.com/dorny/test-reporter/pull/571) > * Increase step summary limit to 1MiB [dorny/test-reporter#581](https://redirect.github.com/dorny/test-reporter/pull/581) > * Fix for empty TRX TestDefinitions [dorny/test-reporter#582](https://redirect.github.com/dorny/test-reporter/pull/582) > * Fix input description for list options [dorny/test-reporter#572](https://redirect.github.com/dorny/test-reporter/pull/572) > * Update npm packages [dorny/test-reporter#583](https://redirect.github.com/dorny/test-reporter/pull/583) > > 2.0.0 > ----- ... (truncated) Commits * [`3d76b34`](dorny/test-reporter@3d76b34) Merge pull request [#730](https://redirect.github.com/dorny/test-reporter/issues/730) from dorny/feature/166-list-all-artifacts * [`a71adbe`](dorny/test-reporter@a71adbe) Update changelog * [`34ed02c`](dorny/test-reporter@34ed02c) Merge pull request [#728](https://redirect.github.com/dorny/test-reporter/issues/728) from dorny/dependabot/npm\_and\_yarn/ts-jest-29.4.6 * [`5204d85`](dorny/test-reporter@5204d85) Bump ts-jest from 29.4.5 to 29.4.6 * [`6658c27`](dorny/test-reporter@6658c27) Merge pull request [#727](https://redirect.github.com/dorny/test-reporter/issues/727) from dorny/feature/fix\_vulnerabilities * [`9b46772`](dorny/test-reporter@9b46772) Use `npm audit fix` to update sub dependencies * [`b3a9df8`](dorny/test-reporter@b3a9df8) Merge pull request [#629](https://redirect.github.com/dorny/test-reporter/issues/629) from dorny/feature/601\_eslint\_v9 * [`deb1d02`](dorny/test-reporter@deb1d02) Rebuild the `dist/index.js` file * [`69312b9`](dorny/test-reporter@69312b9) Update changelog * [`eed2d2d`](dorny/test-reporter@eed2d2d) Modernize ESLint configuration * Additional commits viewable in [compare view](dorny/test-reporter@b082adf...3d76b34) Updates `actions/setup-node` from 6.2.0 to 6.3.0 Release notes *Sourced from [actions/setup-node's releases](https://github.com/actions/setup-node/releases).* > v6.3.0 > ------ > > What's Changed > -------------- > > ### Enhancements: > > * Support parsing `devEngines` field by [`@susnux`](https://github.com/susnux) in [actions/setup-node#1283](https://redirect.github.com/actions/setup-node/pull/1283) > > > When using node-version-file: package.json, setup-node now prefers devEngines.runtime over engines.node. > > ### Dependency updates: > > * Fix npm audit issues by [`@gowridurgad`](https://github.com/gowridurgad) in [actions/setup-node#1491](https://redirect.github.com/actions/setup-node/pull/1491) > * Replace uuid with crypto.randomUUID() by [`@trivikr`](https://github.com/trivikr) in [actions/setup-node#1378](https://redirect.github.com/actions/setup-node/pull/1378) > * Upgrade minimatch from 3.1.2 to 3.1.5 by [`@dependabot`](https://github.com/dependabot) in [actions/setup-node#1498](https://redirect.github.com/actions/setup-node/pull/1498) > > ### Bug fixes: > > * Remove hardcoded bearer for mirror-url [`@marco-ippolito`](https://github.com/marco-ippolito) in [actions/setup-node#1467](https://redirect.github.com/actions/setup-node/pull/1467) > * Scope test lockfiles by package manager and update cache tests by [`@gowridurgad`](https://github.com/gowridurgad) in [actions/setup-node#1495](https://redirect.github.com/actions/setup-node/pull/1495) > > New Contributors > ---------------- > > * [`@susnux`](https://github.com/susnux) made their first contribution in [actions/setup-node#1283](https://redirect.github.com/actions/setup-node/pull/1283) > > **Full Changelog**: <actions/setup-node@v6...v6.3.0> Commits * [`53b8394`](actions/setup-node@53b8394) Bump minimatch from 3.1.2 to 3.1.5 ([#1498](https://redirect.github.com/actions/setup-node/issues/1498)) * [`54045ab`](actions/setup-node@54045ab) Scope test lockfiles by package manager and update cache tests ([#1495](https://redirect.github.com/actions/setup-node/issues/1495)) * [`c882bff`](actions/setup-node@c882bff) Replace uuid with crypto.randomUUID() ([#1378](https://redirect.github.com/actions/setup-node/issues/1378)) * [`774c1d6`](actions/setup-node@774c1d6) feat(node-version-file): support parsing `devEngines` field ([#1283](https://redirect.github.com/actions/setup-node/issues/1283)) * [`efcb663`](actions/setup-node@efcb663) fix: remove hardcoded bearer ([#1467](https://redirect.github.com/actions/setup-node/issues/1467)) * [`d02c89d`](actions/setup-node@d02c89d) Fix npm audit issues ([#1491](https://redirect.github.com/actions/setup-node/issues/1491)) * See full diff in [compare view](actions/setup-node@6044e13...53b8394) Updates `actions/dependency-review-action` from 4.8.3 to 4.9.0 Release notes *Sourced from [actions/dependency-review-action's releases](https://github.com/actions/dependency-review-action/releases).* > Dependency Review Action 4.9.0 > ------------------------------ > > This feature release contains a couple of notable changes: > > * There is a new configuration option `show_patched_versions` which will add a column to the output, showing the fix version of each vulnerable dependency. Thanks [`@felickz`](https://github.com/felickz)! > * Runs which do not display OpenSSF scorecards no longer fetch scorecard information; previously it was fetched regardless of whether or not it was displayed, causing unneccessary slowness. Great catch [`@jantiebot`](https://github.com/jantiebot)! > * There are a couple of fixes to purl parsing which should improve match accuracy for `allow-package-dependency` lists, including case (in)sensitivity and url-encoded namespaces Thanks [`@juxtin`](https://github.com/juxtin)! > > What's Changed > -------------- > > * Compare normalized purls to account for encoding quirks by [`@juxtin`](https://github.com/juxtin) in [actions/dependency-review-action#1056](https://redirect.github.com/actions/dependency-review-action/pull/1056) > * Make purl comparisons case insensitive by [`@juxtin`](https://github.com/juxtin) in [actions/dependency-review-action#1057](https://redirect.github.com/actions/dependency-review-action/pull/1057) > * Feat: Add `Patched Version` to `Vulnerabilities` summary by [`@felickz`](https://github.com/felickz) in [actions/dependency-review-action#1045](https://redirect.github.com/actions/dependency-review-action/pull/1045) > * fix: only get scorecard levels if user wants to see the OpenSSF scorecard by [`@jantiebot`](https://github.com/jantiebot) in [actions/dependency-review-action#1060](https://redirect.github.com/actions/dependency-review-action/pull/1060) > * Bump actions/stale from 10.1.0 to 10.2.0 by [`@dependabot`](https://github.com/dependabot)[bot] in [actions/dependency-review-action#1058](https://redirect.github.com/actions/dependency-review-action/pull/1058) > * Bump actions/checkout from 4 to 6 by [`@dependabot`](https://github.com/dependabot)[bot] in [actions/dependency-review-action#1021](https://redirect.github.com/actions/dependency-review-action/pull/1021) > * Updates for release 4.9.0 by [`@ahpook`](https://github.com/ahpook) in [actions/dependency-review-action#1064](https://redirect.github.com/actions/dependency-review-action/pull/1064) > > New Contributors > ---------------- > > * [`@jantiebot`](https://github.com/jantiebot) made their first contribution in [actions/dependency-review-action#1060](https://redirect.github.com/actions/dependency-review-action/pull/1060) > > **Full Changelog**: <actions/dependency-review-action@v4.8.3...v4.9.0> Commits * [`2031cfc`](actions/dependency-review-action@2031cfc) Merge pull request [#1064](https://redirect.github.com/actions/dependency-review-action/issues/1064) from actions/ahpook/release-4.9.0 * [`d02fa39`](actions/dependency-review-action@d02fa39) Updates for release 4.9.0 * [`4038a34`](actions/dependency-review-action@4038a34) Merge pull request [#1021](https://redirect.github.com/actions/dependency-review-action/issues/1021) from actions/dependabot/github\_actions/actions/check... * [`a632b83`](actions/dependency-review-action@a632b83) Merge pull request [#1058](https://redirect.github.com/actions/dependency-review-action/issues/1058) from actions/dependabot/github\_actions/actions/stale... * [`57a3d46`](actions/dependency-review-action@57a3d46) Merge pull request [#1060](https://redirect.github.com/actions/dependency-review-action/issues/1060) from jantiebot/main * [`5ecdc4b`](actions/dependency-review-action@5ecdc4b) Merge pull request [#1045](https://redirect.github.com/actions/dependency-review-action/issues/1045) from forks-felickz/main * [`e8c2f9a`](actions/dependency-review-action@e8c2f9a) fix: remove inferrable type annotation to pass eslint * [`0e129e1`](actions/dependency-review-action@0e129e1) Prettier - Refactor summary table rendering for improved readability * [`aa60746`](actions/dependency-review-action@aa60746) Add 'show-patched-versions' option to configuration and update summary handling * [`e404798`](actions/dependency-review-action@e404798) Merge upstream actions/dependency-review-action main * Additional commits viewable in [compare view](actions/dependency-review-action@05fe457...2031cfc) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore ` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions

gemini-code-assist bot reviewed Feb 23, 2026

View reviewed changes

robfrank added 2 commits February 24, 2026 09:00

remove upgrade of version

484414d

remove tagging of version

7c24bf9

robfrank closed this Feb 27, 2026

lvca added this to the 26.3.1 milestone Feb 27, 2026

lvca assigned robfrank Feb 27, 2026

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

fix: edge indexes become invalid when deleting and recreating same ed…#3512

fix: edge indexes become invalid when deleting and recreating same ed…#3512
robfrank wants to merge 3 commits intomainfrom
release-26.2.2

robfrank commented Feb 23, 2026

Uh oh!

gemini-code-assist bot commented Feb 23, 2026

Uh oh!

gemini-code-assist bot left a comment

Uh oh!

gemini-code-assist bot Feb 23, 2026

Uh oh!

gemini-code-assist bot Feb 23, 2026

Uh oh!

gemini-code-assist bot Feb 23, 2026

Uh oh!

mergify bot commented Feb 23, 2026 •

edited

Loading

Uh oh!

codacy-production bot commented Feb 23, 2026

Uh oh!

codecov bot commented Feb 23, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

	"security-check": "npm audit --audit-level=none",
	"security-check": "npm audit --audit-level=moderate",

Uh oh!

Conversation

robfrank commented Feb 23, 2026

Uh oh!

gemini-code-assist bot commented Feb 23, 2026

Summary of Changes

Highlights

Footnotes

Uh oh!

gemini-code-assist bot left a comment

Choose a reason for hiding this comment

Code Review

Uh oh!

gemini-code-assist bot Feb 23, 2026

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist bot Feb 23, 2026

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist bot Feb 23, 2026

Choose a reason for hiding this comment

Uh oh!

mergify bot commented Feb 23, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🧪 CI Insights

🟢 All jobs passed!

Uh oh!

codacy-production bot commented Feb 23, 2026

Coverage summary from Codacy

See diff coverage on Codacy

See your quality gate settings Change summary preferences

Footnotes

Uh oh!

codecov bot commented Feb 23, 2026

Codecov Report

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

mergify bot commented Feb 23, 2026 •

edited

Loading