You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .claude/CLAUDE.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -56,11 +56,11 @@ Cursus is a Rust CLI tool for release management. The library is fully async (to
56
56
-`changeset/` - Changeset file I/O: Hugo-style `+++` TOML frontmatter format, parsing, writing to `.cursus/`, and editor integration
57
57
-`changelog/` - Changelog generation and formatting for releases
58
58
- `package_manager/` - Adapter pattern (`PackageManagerAdapter` trait: `enumerate_projects`, `write_version`, `update_dependency_version`, `update_lock_file`, `publish`, `registry_name`) for Cargo and npm/yarn/pnpm workspace enumeration. Versions are returned via `ProjectInfo` from `enumerate_projects()`. Both `write_version` and `update_dependency_version` return `Result<Vec<PathBuf>>` — the files actually written to disk (or that would be written in dry-run mode); callers must extend their `modified_files` list with these paths so they are staged for git. For Cargo crates using `version.workspace = true`, `write_version` returns the workspace-root `Cargo.toml` (not the member manifest). `Project` exposes two release-readiness query methods: `is_releasable_under(&Config)` (true if the project is publishable or listed in `[git].publish_private_packages`) and `is_prepared_for_release(&dyn Filesystem)` (true if `CHANGELOG.md` exists at the project root). The `matching` submodule exposes two public functions for file-to-project attribution: `match_files_to_projects` (primitive, pass the complete project list) and `match_files_to_projects_in_scope` (preferred when `projects` is a filtered subset — takes a wider `attribution_scope` so files inside ignored sub-projects are not mis-attributed to their releasable parents; used by `change`). The `name_validation` submodule (`pub(crate)`) provides `validate_cargo_package_name` and `validate_npm_package_name`, called during `enumerate_projects` for both adapters. Any new adapter must call the appropriate validator on each manifest-sourced package name before populating `ProjectInfo.name`.
59
-
-`git/` - `Git` trait abstracting all git operations; includes `head_sha()` returning the full SHA of the current HEAD commit. `GitWorkdir` is the production impl that delegates to the `git` binary via `CommandRunner`. `SignedCommitGit` is a decorator that wraps `GitWorkdir` and overrides `commit()`, `push()`, and `force_push_branch()` to route the prepare commit through the GitHub Git Data API, producing Verified commits via GitHub's web-flow GPG key (ADR-050). All alternative `Git` impls must implement `head_sha()`. The `ref_format` submodule (`pub(crate)`) provides `validate_branch_name`, `validate_tag_name`, and `validate_revision`; every `GitWorkdir` method that accepts a caller-supplied branch, tag, or revision string calls the appropriate validator before invoking the `CommandRunner`. Any new git operation that takes such a string must do the same. `diff_names` does not validate its `extra_args` slice — that is a caller contract documented on the method.
60
-
-`github/` - `CodeForgeClient` trait; `OctocrabGitHubClient` is the production impl. Handles release creation, PRs, asset uploads, and pre-creation idempotency checks (`find_release_by_tag` — returns `Ok(None)` on 404, `Ok(Some(ExistingRelease { is_draft, .. }))` on hit, error otherwise; every new impl must provide this method).
59
+
- `git/` - `Git` trait abstracting all git operations; includes `head_sha()` returning the full SHA of the current HEAD commit, and `path_exists_at_head(path)` returning whether a path is tracked at HEAD (used by the signed-commit decorators to classify staged paths as `create`/`update`/`delete`). `GitWorkdir` is the production impl that delegates to the `git` binary via `CommandRunner`. Two `Git` decorators route the prepare commit through a forge's web-commit API to produce Verified commits with no key custody: `GitHubSignedCommit` via the GitHub Git Data API (ADR-050) and `GitLabSignedCommit` via the GitLab commits API (ADR-058). Both override `commit()`, `push()`, and `force_push_branch()` and delegate all other methods to the inner `Git`. Selection happens at the binary boundary based on `[github].enabled` vs `[gitlab].enabled`. All alternative `Git` impls must implement every trait method including `head_sha()` and `path_exists_at_head()`. The `ref_format` submodule (`pub(crate)`) provides `validate_branch_name`, `validate_tag_name`, and `validate_revision`; every `GitWorkdir` method that accepts a caller-supplied branch, tag, or revision string calls the appropriate validator before invoking the `CommandRunner`. Any new git operation that takes such a string must do the same. `diff_names` does not validate its `extra_args` slice — that is a caller contract documented on the method.
60
+
- `forge/` - `CodeForgeClient` trait (in `forge/client.rs`, re-exported from `forge`) and per-forge implementations as sibling submodules: `forge::github::OctocrabGitHubClient` (octocrab) and `forge::gitlab::ReqwestGitLabClient` (Kitware `gitlab` crate's `AsyncGitlab`). Every impl provides: `forge_name() -> &'static str` (returns the forge's user-facing label, e.g. `"GitHub"`/`"GitLab"`, used by orchestration code to compose forge-aware log lines); `find_release_by_tag` (returns `Ok(None)` on 404, `Ok(Some(ExistingRelease { is_draft, .. }))` on hit, error otherwise — `is_draft` is always `false` on GitLab); `create_release`, `upload_asset`, `publish_release` (no-op on GitLab since releases are created in final state), `create_pull_request`, `find_open_pull_request`, `update_pull_request`. The trait, parameter names, and shared types stay forge-neutral; per-forge log lines and error messages use the active forge's native vocabulary at the API boundary (e.g. the GitLab impl translates trait `head`/`base` → `source_branch`/`target_branch`).
61
61
-`filesystem.rs` - `Filesystem` trait abstracting all file I/O; `LocalFilesystem` is the production impl using `tokio::fs`.
62
-
-`command/` - `CommandRunner` trait with `run` (read-only) and mutating variants (`run_mut`, `run_interactive`, `run_shell_interactive`, `run_streaming`). `run_streaming` executes user-configurable shell commands (`github.build_command`, `npm.lock_command`) with inherited stdout/stderr so output appears live; stdin is null. `DryRunCommandRunner` decorator implements the ADR-017 late-guard dry-run pattern (skips mutating ops, forwards read-only); `VerboseCommandRunner` logs invocations.
63
-
-`env.rs` - `Env` struct: dependency injection container holding `Arc<dyn CommandRunner>`, `Arc<dyn Filesystem>`, `Arc<dyn Git>`, `Option<Arc<dyn CodeForgeClient>>`, editor, locale, and environment flags. Builder methods compose runners (e.g. `with_dry_run_runner()`). All command execution and file I/O goes through `Env`.
62
+
-`command/` - `CommandRunner` trait with `run` (read-only) and mutating variants (`run_mut`, `run_interactive`, `run_shell_interactive`, `run_streaming`). `run_streaming` executes user-configurable shell commands (`github.build_command`, `gitlab.build_command`, `npm.lock_command`) with inherited stdout/stderr so output appears live; stdin is null. `DryRunCommandRunner` decorator implements the ADR-017 late-guard dry-run pattern (skips mutating ops, forwards read-only); `VerboseCommandRunner` logs invocations.
63
+
-`env.rs` - `Env` struct: dependency injection container holding `Arc<dyn CommandRunner>`, `Arc<dyn Filesystem>`, `Arc<dyn Git>`, `Result<Arc<dyn CodeForgeClient>, String>` (`Err` carries a human-readable reason why the client is unavailable, set by the binary boundary), editor, locale, and environment flags. Builder methods compose runners (e.g. `with_dry_run_runner()`). All command execution and file I/O goes through `Env`.
64
64
-`conventional_commit.rs` - Parser for Conventional Commits; maps `feat`→Minor, `fix`→Patch, breaking→Major via `ConventionalCommit::change_type()`
65
65
-`locale.rs` - i18n via `fluent-templates`; messages are embedded at compile time (ADR-034).
| 058 | 058-verified-release-commits-on-gitlab-via-web-commits-api.md | Produce Verified Release Commits on GitLab via the Web Commits API | Accepted (2026-05-22) |
Adds GitLab verified release commits. When running on GitLab CI ≥18.10 with a token, the prepare commit is routed through the GitLab commits API and appears as **Verified** in the GitLab UI — no signing key custody required. Reuses the existing `[git].signed_commits` config knob (`"auto"`, `"force"`, `"off"`); `"auto"` engages whenever `GITLAB_CI=true` and a token is present. See the [GitLab CI guide](https://zantarix.github.io/cursus/guides/ci-integration/gitlab/#verified-commits) for setup.
Harden GitLab forge support. Self-managed instances served over plain HTTP are now reachable end-to-end: the API client and the asset URLs surfaced in release notes both honour the scheme from `CI_API_V4_URL` or `[gitlab].host`. The release-asset host is also pinned to the same endpoint the API client used, so a stale or mirrored git remote can no longer cause asset links to point at the wrong instance. GitLab API errors run through credential redaction before being logged, matching the protection already in place for the signed-commit decorator.
Cursus now rejects configurations with more than one forge section enabled at load time. Setting both `[github].enabled = true` and `[gitlab].enabled = true` in `.cursus/config.toml` produces a hard error that names the offending flags and explains the fix. Configs with a single enabled forge — or no enabled forge — continue to work as before.
Add GitLab support to `cursus init`. The wizard now prompts you to pick GitHub, GitLab, or Neither as your forge, with a dedicated GitLab editor screen that auto-detects `group/project` from your git origin and surfaces a self-managed host field for non-gitlab.com instances. The generated `.cursus/config.toml` writes the chosen forge as `enabled = true` and emits the other forge as a commented-out template, so switching forges later is a hand-edit away. The config also reorders active sections to the top of the file so your live configuration is visible without scrolling as the schema grows.
Add first-class GitLab support: [gitlab] config section, ReqwestGitLabClient implementing CodeForgeClient via the Kitware gitlab crate, GitLab CI token detection at the binary boundary, and a forge-neutral crate::forge module layout (relocates crate::github to crate::forge::github)
0 commit comments