assertEquals("instance3", transformer3.getName());

        // Change one instance's name
        transformer2.setName("changed2");

        // Others should remain unchanged
        assertEquals("instance1", transformer1.getName());
        assertEquals("changed2", transformer2.getName());
        assertEquals("instance3", transformer3.getName());
    }

    /**

name: Latest Changes

on:
  pull_request_target:
    branches:
      - master
    types:
      - closed
  workflow_dispatch:
    inputs:
      number:
        description: PR number
        required: true
      debug_enabled:
        description: 'Run the build with tmate debugging enabled (https://github.com/marketplace/actions/debugging-with-tmate)'
        required: false
        default: 'false'

jobs:
  latest-changes:

                warnings << "Return nullability changed from nullable to null-unmarked"
            }
        }

        if (!errors.isEmpty()) {
            def changes = errors + warnings
            return acceptOrReject(member, changes, Violation.error(member, changes.join(" ")))
        }
        if (!warnings.isEmpty()) {

                <a class="btn btn-info" role="button" data-toggle="collapse" href="#accept-${changeId}" aria-expanded="false" aria-controls="collapseExample">Accept this change</a>
                <div class="collapse" id="accept-${changeId}">
                  <div class="well">

   - Include context in the summary: what changed, why, and any issue references.
   - Use `[WIP]` for in-progress PRs to avoid premature merging or choose GitHub draft PRs.

2. **Commits**:
   - Write clear messages: what changed and why (e.g., “Refactor S3 API handler to reduce latency so that requests process 20% faster”).

        // Initial update - should mark as changed
        entry.updateChild(childName, 1024L, 1000L, false, 0x20, 500L, 800L);
        assertTrue(entry.hasChanges());

        // Clear changes to test next scenario
        entry.markComplete();
        assertFalse(entry.hasChanges());

        // Update with same values - should not mark as changed (no actual change)

So, having a nice PR title will not only look nice in GitHub, but also in the release notes. 📝

## Add Labels to PRs

  - [Changes by Kind](#changes-by-kind-9)
    - [API Change](#api-change)
    - [Feature](#feature-6)
    - [Bug or Regression](#bug-or-regression-9)
  - [Dependencies](#dependencies-9)
    - [Added](#added-9)
    - [Changed](#changed-9)
    - [Removed](#removed-9)
- [v1.31.4](#v1314)
  - [Downloads for v1.31.4](#downloads-for-v1314)

/**
 * Enumeration of SMB Witness Event Types as defined in MS-SWN specification.
 * These events represent different types of cluster state changes that clients
 * can be notified about.
 */
public enum WitnessEventType {
    /**
     * Resource state changed - general resource state modification
     */
    RESOURCE_CHANGE(1),

    /**
     * Client should move to different node - directed failover
     */

            for (JApiCompatibilityChange change : member.getCompatibilityChanges()) {
                if (IGNORED_CHANGE_TYPES.contains(change.getType())) {
                    return null;
                }
            }
            if (member instanceof JApiHasAnnotations) {
                if (isIncubating((JApiHasAnnotations) member)) {
                    return Violation.warning(member, "Changed public API (@Incubating)");
                }