docs: deprecate the standalone keep-common fork - #35
Open
mswilkison wants to merge 1 commit into
Open
mswilkison wants to merge 1 commit into
mswilkison wants to merge 1 commit into
Conversation
This was referenced Sep 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
keep-core's current dev release candidate has absorbed both the common runtime packages and generators, so it no longer needs this standalone fork. Add a prominent deprecation notice and a retirement plan that preserves the existing repository/module identity, tags, releases, and checksums for remaining consumers. No threshold-common replacement module is planned.
The plan makes archival conditional on the dev-to-main release, remaining-consumer retain/migrate decisions, and operational monitoring updates. CI stays active during that review, and maintenance publication remains available when agreed with affected owners. It also explains that keep-core's final in-tree layout is not a drop-in replacement module and that this decision does not deprecate the separate original Keep upstream. Correct the fork's build badge, contribution links, upstream link, and stale setup-go documentation.
Retirement work is tracked in #33. Related keep-core inventory: keep-core #4221. The source move is keep-core #4327, with the release tracked by keep-core #4256.
Validation:
a90ce1bf0738a35e4e3881f634f07520c2b8529e; imports, manifests, generator commands, and the resolvedgo mod graphcontain no common-module dependency. The sole remaining textual reference is the intentional original upstream issue #117 link.git diff --check.go.mod,go.sum, source code, and CI/release workflows are unchanged. This is a documentation-only PR; no runtime tests were needed for its final diff.Merging this PR announces the deprecation plan. It does not archive the repository, publish a tag, or change a consumer's dependency pin.