TECHOPS-366: Deprecate liquibase/docker repo

[jandroav]

Summary

Final story under DAT-22522. The Community (DAT-22523) and Secure (DAT-22524) Dockerfile migrations have landed, so this PR begins deprecating liquibase/docker.

This PR covers the repo-content portion of TECHOPS-366:

• ✅ README.md — prominent DEPRECATED banner redirecting Community users to liquibase/liquibase and Secure users to support
• ✅ README-secure.md — DEPRECATED banner redirecting Secure users to support
• ✅ .github/ISSUE_TEMPLATE/config.yml — disables blank issues and redirects new issues to the product repo / support

Docker Hub images (liquibase/liquibase, liquibase/liquibase-secure), tags, history, and signatures are unaffected.

⚠️ Merge ordering note

On merge, publish-oss-readme.yml and publish-liquibase-secure-readme.yml will push these updated READMEs to Docker Hub — this satisfies AC "Docker Hub README updated on both images". Keep these workflows until that publish has run. Workflow removal + repo archive happen as follow-up steps (see ticket).

Remaining (outside this PR — tracked on TECHOPS-366)

• GitHub repo description → [DEPRECATED] ...
• Triage / close open issues + PRs with redirect comment
• Remove/disable remaining workflows (after Docker Hub publish)
• Update customer docs (docs.liquibase.com)
• Slack / GitHub Discussion announcement
• Archive repo (read-only) — LAST

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@jandroav, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 29 minutes and 46 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more credits in the billing tab to continue.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 31bc41a2-fe3e-419b-8a00-1000bd84df79

📥 Commits

Reviewing files that changed from the base of the PR and between 0909e3d and 5294ab5.

📒 Files selected for processing (1)

• README.md

📝 Walkthrough

Walkthrough

This PR communicates that the liquibase/docker repository is deprecated and no longer the source for Liquibase Docker Dockerfiles. Deprecation banners are added to the main README and secure README, directing users to liquibase/liquibase for Community images and noting that Secure images are internally maintained. A GitHub issue template configuration is added to disable blank issues and route users to appropriate support channels and repositories.

Changes

Repository Deprecation and Redirection

Layer / File(s)	Summary
Deprecation notices in README files README.md, README-secure.md	Deprecation banners added to both READMEs explaining that Dockerfiles are no longer sourced from this repository, directing Community users to liquibase/liquibase, noting Secure images are internally maintained, and clarifying that Docker Hub images and historical repository artifacts remain valid.
GitHub issue template configuration .github/ISSUE_TEMPLATE/config.yml	Issue template config disables blank issue creation and adds three contact links: one for community Docker image issues routing to liquibase/liquibase, one for Secure image support routing to Liquibase Support, and one for Docker Hub image information.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested reviewers

• sayaliM0412
• jnewton03

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the main change: deprecating the liquibase/docker repository, which is the primary objective of this PR.
Description check	✅ Passed	The description is directly related to the changeset, providing context about the deprecation, explaining the specific changes made to three files, and outlining merge considerations and follow-up tasks.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch techops-366-deprecate-docker-repo

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[claude]

Claude finished @jandroav's task in 31s —— View job

---

Code Review

LGTM - no significant issues found. The deprecation messaging is clear and well-organized, the issue template configuration correctly redirects users to appropriate resources, and all URLs are properly formatted. The table in README.md effectively communicates the migration path for both Community and Secure users.

---

[claude]

Claude finished @jandroav's task in 33s —— View job

---

Code Review

LGTM - no significant issues found. The deprecation implementation is clear and well-structured:

• README.md & README-secure.md deprecation banners (lines 3-16): Prominent warnings with proper redirects to liquibase/liquibase for Community users and Liquibase Support for Secure users, with clear reassurance that Docker Hub images remain unaffected.
• Issue template configuration: Properly disables blank issues and provides three helpful contact links routing users to appropriate channels (liquibase/liquibase repo for Community issues, support for Secure, Docker Hub for image info).
• All URLs are correct and properly formatted, including the /choose suffix for the GitHub issue template selector.
• YAML syntax is valid with proper indentation and structure.

The deprecation messaging effectively communicates the migration path while preserving user access to all existing Docker images and assets.