git 5.0.0.beta.5 → 5.0.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: dd627f8c88fec64de6a0bd1f809fec1415ec503b3e2a79cf0701d7dcea27f7af
-  data.tar.gz: 9d40f48b1b9fc7b9fee24b8092d540e32221b9cf8f63e01f8c600141b39382f1
+  metadata.gz: '08c43ba7ae36ad5b41333b4c5a4d1890ff32c32ad07074145ee75d71cde61b8d'
+  data.tar.gz: 1380d2019f14ec54339aec4d7fced236098072794747edd38de8559aee8a6b66
 SHA512:
-  metadata.gz: 9feb3e0cecb9bf51472690c3824719da82e66711466a83e5a3328d209c4a1bdebb134c5ed7a26c023097dfca6d78234b835f2abab08e6a07d714699c79e608e8
-  data.tar.gz: fa8013e041f2e7d73d73c1ddc18bb9e9d5b59e5d960154e1af1da759401782c288cce90646bf3fa4914738415611ee07dcdbcd7b314958bf85ba06c1fe190cb4
+  metadata.gz: fe650cffb57c334881cda31e8f5a2e062c090bb1028c423647d5a429504c8d3ad96a6cb58812a3373ca0733f9c325e8dda3392bcd5ef4e53e561e80a17c5fa9d
+  data.tar.gz: c66b6ccf6e4644c09550d035c0b90ad1eb7dfbf91fc7509f8461329e6a33ac55d7324653a1c7770101a20156b4297304f14098a4fb8f97d48e7b6409b751b6d7

data/.github/copilot-instructions.md

@@ -2,95 +2,41 @@
 
 ## Project Overview
 
-ruby-git is a Ruby gem providing a Ruby interface to Git repositories. It wraps
-system calls to the `git` CLI and exposes an API for creating and manipulating repos,
-working with branches/commits/tags/remotes, inspecting history and objects, and
-performing all standard Git operations.
+A Ruby gem providing an interface to Git repositories by wrapping system calls to the
+`git` CLI.
 
-**Status:** Stable. Minimum Ruby 3.2.0, minimum Git 2.28.0. MRI on macOS/Linux/Windows;
-JRuby and TruffleRuby on Linux (JRuby/TruffleRuby on Windows are not tested).
+Read the "Project Context" skill (`.github/skills/project-context/SKILL.md`) for
+design philosophy, technical details, and compatibility requirements.
 
-For architecture details, coding standards, design philosophy, key technical details,
-and compatibility requirements see the
-[Project Context](skills/project-context/SKILL.md) skill.
+This project enforces Conventional Commits. See `.commitlintrc.yml` for allowed types
+and scopes. Never use `#` in the commit message body. Doing so will cause
+commitlint to incorrectly parse the commit message body as a footer. If you need to
+refer to an issue in the body, use `issue 999` instead of `issue #999`. It is still
+fine to use `#` in footer values such as `Closes: #999` or `Refs: #999`.
 
 ## Terminology & Writing Style
 
-- Use American English always. Avoid British English spellings and idioms.
-- **Version strings** — use the most precise form appropriate to the context:
-  - `vN.x` (e.g. `v5.x`, `v4.x`) — the whole major series; use for compatibility
-    statements and upgrade guide scope ("v4.x code works on v5.x").
-  - `vN.0.0` (e.g. `v5.0.0`, `v6.0.0`) — a specific first release; use when
-    precision matters ("removed in v5.0.0", "the foundation delivered in v5.0.0").
-  - `vN.0` — avoid; ambiguous between "minor version 0" and "shorthand for vN.0.0".
-- **RuboCop** — correct capitalization when referring to the tool by name in prose,
-  documentation, or comments.
-- **`rubocop`** — correct form when referring to the command-line executable or gem
-  name (e.g., `gem 'rubocop'`, `bundle exec rubocop`).
-- **Rubocop** — incorrect; never use this form.
-
-## Skill Loading
-
-When a skill applies to a request, read the entire `SKILL.md` file before taking
-any other action. Read from line 1 through EOF with no gaps. Simple code review
-or explanation does not require a skill.
+- Use American English.
+- **Version strings:** Use `vN.x` for major series compatibility (e.g., `v4.x`) and
+  `vN.0.0` for specific releases (e.g., `v5.0.0`). Never use the ambiguous `vN.0`.
+- **RuboCop:** Use `RuboCop` for prose and `rubocop` for CLI or gem names. Never use
+  `Rubocop`.
 
 ## Project Commands
 
 | Purpose | Command |
 | --- | --- |
-| First-time setup | `bin/setup` |
-| Run all tests and linters (CI-equivalent) | `bundle exec rake default` |
-| Run all tests and linters (force parallel) | `bundle exec rake default:parallel` |
-| Run all RSpec tests | `bundle exec rake spec:parallel` |
-| Run RSpec unit tests | `bundle exec rake spec:unit:parallel` |
-| Run RSpec integration tests | `bundle exec rake spec:integration:parallel` |
+| First-time project or new worktree setup | `bin/setup` |
+| Run all tests and linters (CI-equivalent) | `bundle exec rake` |
+| Run all RSpec tests | `bundle exec rake spec` |
+| Run RSpec unit tests | `bundle exec rake spec:unit` |
+| Run RSpec integration tests | `bundle exec rake spec:integration` |
 | Run a specific RSpec spec | `bundle exec rspec <path>` |
 | Run linters | `bundle exec rake rubocop yard build` |
 
-**Test suite:** `spec/` (RSpec) is the sole test suite — all new tests go here.
-
-## Commit Conventions
-
-This project uses [Conventional Commits](https://www.conventionalcommits.org/).
-Automated releases via [release-please](https://github.com/googleapis/release-please).
-
-**Format:** `type[optional scope][!]: description`
-
-**Types:** `feat`, `fix`, `docs`, `style`, `refactor`, `perf`, `test`, `chore`,
-`revert`, `ci`, `build`
-
-**Breaking changes:** Add `!` before `:` and a `BREAKING CHANGE: <description>`
-footer.
-
-**Version bumps:** breaking change → major; `feat` → minor; others → patch.
-
-**Pre-commit hook:** Run `bin/setup` to install a validator.
-
 ## Branch & PR Strategy
 
 | Target | When |
 | --- | --- |
 | `main` | New features, breaking changes, all active development |
 | `4.x` | Security fixes and backward-compatible bug fixes for the v4.x series |
-
-> **Never commit directly to `main` or `4.x`** — this rule must never be violated.
-> Always check `git branch --show-current` before committing. If on a release branch,
-> run `git switch -c <type>/<short-description>` first.
-
-All changes go through a PR from a topic branch.
-
-**Creating a PR:** Use `gh pr create`. Read `.github/pull_request_template.md` for
-the body structure. Complete the [PR Readiness Review](skills/pr-readiness-review/SKILL.md)
-skill first.
-
-## Key Documents
-
-| Document | Purpose |
-| --- | --- |
-| `CONTRIBUTING.md` | Design philosophy, contribution guidelines |
-| `CHANGELOG.md` | Version history (auto-updated by release-please) |
-| `MAINTAINERS.md` | Maintainer list and responsibilities |
-| `AI_POLICY.md` | AI usage policy for this project |
-| `redesign/` | Architecture redesign plans and implementation guide |
-| `.github/skills/` | All Copilot skills |

data/.gitignore

@@ -20,3 +20,5 @@ rubocop-report.json
 
 # generated git reference docs
 git-reference/
+
+tmp

data/.husky/pre-commit

@@ -7,7 +7,7 @@ protected_branches="main 4.x"
 for protected in $protected_branches; do
   if [ "$branch" = "$protected" ]; then
     echo "ERROR: Direct commits to '$branch' are not allowed."
-    echo "       Create a topic branch first:  git switch -c <branch-name>"
+    echo "       Create a topic branch first:  git switch -c <type>/<short-description>"
     exit 1
   fi
 done

data/.release-please-manifest.json

@@ -1,3 +1,3 @@
 {
-  ".": "4.1.2"
+  ".": "5.0.1"
 }

data/CHANGELOG.md

@@ -5,6 +5,52 @@
 
 # Change Log
 
+## [5.0.1](https://github.com/ruby-git/ruby-git/compare/v5.0.0...v5.0.1) (2026-07-30)
+
+
+### Other Changes
+
+* Review and streamline AI agent instructions ([536eb86](https://github.com/ruby-git/ruby-git/commit/536eb865440da8c0e74de0dfc32828b82fc675db))
+* Summarize v5.0.0 as architectural redesign in CHANGELOG ([712c93e](https://github.com/ruby-git/ruby-git/commit/712c93ea237490be3b037250af44cd6633baf68f))
+
+## [5.0.0](https://github.com/ruby-git/ruby-git/compare/v4.1.2...v5.0.0) (2026-07-28)
+
+v5.0.0 is a complete architectural redesign of the `git` gem. The monolithic
+`Git::Base` and `Git::Lib` classes have been replaced by a layered design:
+`Git::Commands::*` for git command execution, `Git::Repository` as the public
+API surface, and dedicated parser classes. Most v4.x code requires **no
+changes** — compatibility shims emit deprecation warnings pointing to the v5.x
+equivalents.
+
+For a full migration guide, including deprecated method renames and code
+examples, see [UPGRADING.md](UPGRADING.md).
+
+### ⚠ BREAKING CHANGES
+
+* **`Git::Base` class removed; constant remains as a deprecated shim.**
+  `Git::Base.new` raises an error and `require 'git/base'` raises `LoadError`.
+  The `Git::Base` constant still exists as a deprecated module included in
+  `Git::Repository`, so `is_a?(Git::Base)` checks and monkeypatches continue to
+  work but emit deprecation warnings. Update explicit `Git::Base` class
+  references to use `Git::Repository`; the shim is removed in v6.0.0.
+* **`Git::Lib` removed.** Calling `#lib` on a repository object returns `self`
+  with a deprecation warning (forwarding to `Git::Repository` methods where
+  possible), but `Git::Lib` itself no longer exists. Methods unique to
+  `Git::Lib` with no `Git::Repository` counterpart raise `NoMethodError`.
+* **`Git.open`, `Git.bare`, `Git.clone`, and `Git.init` return `Git::Repository`
+  instead of `Git::Base`.** For most callers this is transparent. Code that
+  explicitly checks `is_a?(Git::Base)` must be updated to `is_a?(Git::Repository)`.
+* **Unsupported options now raise `ArgumentError`.** Unknown keyword options
+  that were silently ignored in v4.x may now raise `ArgumentError`. Check
+  option names against the documented API when upgrading.
+* **`Git::Log#object` is not a path limiter.** Use `Git::Log#path` to filter
+  log results by file path.
+* **`Git::CommandLineResult` is deprecated** (removed in v6.0.0). Use
+  `Git::CommandLine::Result` instead.
+
+For the full list of commits included in this release, see the
+[v5.0.0 commit history](https://github.com/ruby-git/ruby-git/compare/v4.1.2...v5.0.0).
+
 ## [4.1.2](https://github.com/ruby-git/ruby-git/compare/v4.1.1...v4.1.2) (2026-01-10)