## Consequences

* The configuration cache serialization infrastructure should be used for all serialization.
* Existing usages of Serializer outside of this infrastructure should be migrated to use it.
* Existing usages of Java serialization should be migrated to use it.
* It is ok for Serializer to be used as a replacement for Java serialization as a migration step.

load("@python_version_repo//:py_version.bzl", "REQUIREMENTS")
load("@rules_python//python:pip.bzl", "compile_pip_requirements")

# TODO(ybaturina): Remove once TF is migrated to CUDA 12.9.
genrule(
    name = "nvidia_constraints",
    srcs = ["nvidia-requirements.txt"],
    outs = ["nvidia-constraints.txt"],
    cmd = """sed -E "s/>=/==/" $(location nvidia-requirements.txt) > $@;""",
)

- Migrated Memory Manager to contextual logging. ([#130727](https://github.com/kubernetes/kubernetes/pull/130727), [@swatisehgal](https://github.com/swatisehgal))
- Migrated `pkg/kubelet/status` to use contextual logging. ([#130852](https://github.com/kubernetes/kubernetes/pull/130852), [@Chulong-Li](https://github.com/Chulong-Li))

  config migrate" command. For both commands unknown APIs or fields will throw errors. ([#118013](https://github.com/kubernetes/kubernetes/pull/118013), [@neolit123](https://github.com/neolit123))

	// The Send() method will then re-direct entries
	// to the new target when the current one
	// has been set to status "statusClosed".
	// Once the glogal target slice has been migrated
	// the current target will stop receiving entries.
	migrateTarget *Target

	// Number of events per HTTP send to webhook target
	// this is ideally useful only if your endpoint can

	if err := json.Unmarshal(b, format); err != nil {
		return "", err
	}
	return format.Erasure.Version, nil
}

// Migrates all previous versions to latest version of `format.json`,
// this code calls migration in sequence, such as V1 is migrated to V2
// first before it V2 migrates to V3.n
func formatErasureMigrate(export string) ([]byte, fs.FileInfo, error) {
	formatPath := pathJoin(export, minioMetaBucket, formatConfigFile)

    are changed; the old `okhttp3.mockwebserver` APIs remain as they always have been.


## Version 5.0.0-alpha.7

_2022-04-26_

**This release introduces new Kotlin-friendly APIs.** When we migrated OkHttp from Java to Kotlin in
OkHttp 4.0, we kept our Java-first APIs. With 5.0 we're continuing to support Java and adding
additional improvements for Kotlin users. In this alpha we're excited to skip-the-builder for

Bucket replication is designed to replicate selected objects in a bucket to a destination bucket.

- Migrated validation in `resource.k8s.io` to declarative validation.
  When the `DeclarativeValidation` feature gate is enabled, mismatches with existing validation are reported via metrics.

- [ ] Transform documents to Fess format
- [ ] Validate NDJSON format
- [ ] Import documents via Admin UI or API
- [ ] Verify document count after import
- [ ] Test search queries on migrated data
- [ ] Configure document boost/relevance (if needed)

### Search Integration

- [ ] Enable required APIs (GSA, JSON)
- [ ] Update client applications with new endpoints