}
            """
        ) {
            assertHasErrors(
                "Field nonFinalField: Nullability breaking change.",
                "Field finalField: From non-nullable to nullable breaking change.",
                "Method com.example.Source.foo(): From non-null returning to null returning breaking change."
            )
            assertHasNoWarning()
            assertHasNoInformation()
        }
    }

                    errors << "From non-nullable to nullable breaking change"
                } else if (oldNullability && !newNullability) {
                    warnings << "Nullability changed from nullable to non-nullable"
                }
            } else if (oldNullability != newNullability) {
                errors << "Nullability breaking change"
            }

         * Checks if this lease is currently in a breaking state
         * @return true if lease is currently breaking
         */
        public boolean isBreaking() {
            return breaking;
        }

        /**
         * Sets the breaking state for this lease
         * @param breaking set breaking state
         */
        public void setBreaking(boolean breaking) {
            this.breaking = breaking;

 *  Breaking: `RecordedRequest.body` is now nullable. Null is used when the request does not have a
    body.

 *  Breaking: `RecordedRequest.chunkSizes` is now nullable. Null is used when the request does not
    use chunked encoding. This is different from an empty list - that indicates the request is
    chunked but has no data.

Make sure you use a supported label from the [latest-changes list of labels](https://github.com/tiangolo/latest-changes#using-labels):

* `breaking`: Breaking Changes
    * Existing code will break if they update the version without changing their code. This rarely happens, so this label is not frequently used.
* `security`: Security Fixes

         * the case of the Samsung bug, and we do that by breaking AtomicReferenceFieldUpdater.
         * Breaking AtomicReferenceFieldUpdater not only forces AggregateFutureState to fall back to
         * another implementation but also forces AbstractFutureState to be able to do the
         * same—hence the try-catch here.
         *
         * (Really, we're fortunate that breaking AtomicReferenceFieldUpdater doesn't break _even

        private volatile boolean breaking;
        
        public LeaseEntry(Smb2LeaseKey key, String path, int state) {
            this.leaseKey = key;
            this.path = path;
            this.leaseState = state;
            this.createTime = System.currentTimeMillis();
            this.lastAccessTime = createTime;
            this.epoch = 1;
            this.breaking = false;
        }
        

						</goals>
					</execution>
				</executions>
				<configuration>
					<addDefaultLicenseMatchers>true</addDefaultLicenseMatchers>
					<excludes>
						<exclude>pom.xml</exclude>
						<exclude>breaking-changes.xml</exclude>
						<exclude>*.md</exclude>
						<exclude>*.sh</exclude>
						<exclude>build.properties</exclude>
						<exclude>docs/**</exclude>
						<exclude>src/test/resources/**</exclude>

    subgraph azkaban-project[prisoner-of-azkaban project]
        azkaban(prisoner-of-azkaban) --> |requires| harry-3
    end
```

/// tip

It's very common in Python packages to try the best to **avoid breaking changes** in **new versions**, but it's better to be safe, and install newer versions intentionally and when you can run the tests to check everything is working correctly.

///

// This should be always:
String value = getSomeProperty().get()
```

## Consequences

* We are incurring debt that will need to be paid later via deprecations or breaking changes to existing classes. The implementation for some Gradle types will be more complicated than an equivalent clean-sheet implementation.