Update README and CONTRIBUTING for new maintainership

[renecannao]

Summary

• Removed the "end of dbdeployer" notice from README.md and added a "New Maintainer" section explaining the project is now actively maintained by the ProxySQL team, with roadmap highlights and a link to the Phase 1 milestone
• Added a "Development Setup" section to CONTRIBUTING.md with Go 1.22+ requirement and golangci-lint instructions
• Updated issue tracker and badge links to point to ProxySQL/dbdeployer

Closes #8

Test plan

• Verify README.md renders correctly on GitHub
• Verify CONTRIBUTING.md renders correctly on GitHub
• Confirm milestone link resolves properly

[Copilot]

Pull request overview

Updates project documentation to reflect new maintainership under the ProxySQL organization, and refreshes the Go toolchain/dependencies accordingly.

Changes:

• README: remove “end of dbdeployer” notice; add “New Maintainer” + roadmap; update repo/badge links.
• CONTRIBUTING: add development setup notes (Go 1.22+; golangci-lint guidance) and update issue tracker link.
• Go module: bump minimum Go version to 1.22 and update dependency set (go.mod/go.sum); remove an obsolete build tag from an embedded-registry file.

Reviewed changes

Copilot reviewed 4 out of 5 changed files in this pull request and generated 5 comments.

Show a summary per file

File	Description
go.mod	Raises Go version to 1.22 and bumps multiple dependencies.
go.sum	Updates checksums to match the refreshed dependency graph.
downloads/tarball_registry.go	Removes a Go 1.16 build constraint header.
README.md	Updates maintainership messaging and adjusts links/badge.
CONTRIBUTING.md	Adds development setup section and updates issue tracker link.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

CONTRIBUTING says golangci-lint is "required", but there’s no golangci-lint config in the repo and CI doesn’t appear to run it. To avoid contributor confusion, either add/configure golangci-lint (and enforce it in CI) or soften the wording to make it optional/recommended.

Suggested change

	- **[golangci-lint](https://golangci-lint.run/)** is required for linting:
	- **[golangci-lint](https://golangci-lint.run/)** is recommended for linting (optional):

[Copilot]

The "features comparison" link still points to the old datacharmer repository/branch (github.com/datacharmer/dbdeployer/blob/master/...). Since the README now identifies ProxySQL/dbdeployer as the canonical repo, this link should be updated (or made relative) to avoid sending readers to an outdated fork/branch.

Suggested change

	This is a port of [MySQL-Sandbox](https://github.com/datacharmer/mysql-sandbox), originally written in Perl, and re-designed from the ground up in [Go](https://golang.org). See the [features comparison](https://github.com/datacharmer/dbdeployer/blob/master/docs/features.md) for more detail.
	This is a port of [MySQL-Sandbox](https://github.com/datacharmer/mysql-sandbox), originally written in Perl, and re-designed from the ground up in [Go](https://golang.org). See the [features comparison](docs/features.md) for more detail.

[Copilot]

The build status badge URL format looks incorrect for GitHub Actions (it uses /workflows/.github/workflows/all_tests.yml/badge.svg). Consider switching to the supported badge endpoint under /actions/workflows/<workflow_file>/badge.svg (optionally with a branch query) so the badge renders reliably.

Suggested change

	
	

[Copilot]

go.mod now declares Go 1.22, but the GitHub Actions workflow in this repo still sets up Go ^1.18. Unless CI is updated accordingly, the build/test job will likely fail (or use an unintended toolchain). Please align CI (and any scripts) with the new minimum Go version, or lower the go directive if 1.22 is not required.

Suggested change

	go 1.22
	go 1.18

[Copilot]

This PR’s description focuses on documentation/maintainership updates, but go.mod also bumps multiple direct dependencies (cobra, mysql driver, testify, x/*). If that dependency refresh is intentional, it would help to call it out explicitly in the PR description (or split into a separate PR) because it changes the risk/rollback profile beyond docs.

[renecannao]

@gemini-code-assist review

[renecannao]

@claude review

[gemini-code-assist]

Code Review

This pull request updates the project's documentation and configuration to reflect the new maintainership under the ProxySQL team. The changes include updating the README and CONTRIBUTING files with new information, development setup instructions, and updated links. The Go module is also updated to version 1.22 along with its dependencies.

My review has identified a couple of important issues:

• The Go module path in go.mod has not been updated to the new repository location (github.com/ProxySQL/dbdeployer). This is a critical issue that affects dependency management.
• The README.md file was edited directly, but the project's contribution guidelines state that it should be generated from a template. This means the changes will be lost on the next generation.

Please address these points to ensure the project is correctly set up under its new maintainership.

[gemini-code-assist]

Since the repository has been moved to ProxySQL/dbdeployer, the module path should be updated to reflect the new location. This is crucial for Go's dependency management to correctly resolve the module.

Without this change, go get and other Go tools will still fetch the module from the old datacharmer location.

After changing the module path, you will also need to update all internal import paths throughout the project to use the new module path. This can be a significant change, but it's necessary for the project's long-term health under new maintainership.

Suggested change

	module github.com/datacharmer/dbdeployer
	module github.com/ProxySQL/dbdeployer

[gemini-code-assist]

According to CONTRIBUTING.md, this README.md file is generated from mkreadme/readme_template.md and should not be edited directly. Your changes will be lost the next time the README is generated.

Please apply your changes to mkreadme/readme_template.md and then run ./mkreadme/build_readme.sh to regenerate README.md.

Also, when you move the changes to the template, please double-check the year in 'As of 2026', as it seems to be a typo referring to a future date.

[renecannao]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[coderabbitai]

Warning

Rate limit exceeded

@renecannao has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 11 minutes and 32 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, 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 have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 1b77402c-bbb4-4421-9f59-314f595486b4

📥 Commits

Reviewing files that changed from the base of the PR and between 35df06d and 0c1827a.

📒 Files selected for processing (2)

• CONTRIBUTING.md
• README.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch phase1/task8-docs-update

---

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.}