1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
//! Release-provider abstractions and git operations for the
//! phpboyscout Rust toolkit.
//!
//! Formerly `rtb-vcs` in the
//! [rust-tool-base](https://gitlab.com/phpboyscout/rust-tool-base)
//! monorepo — renamed to `rtb-forge` at extraction for name
//! convergence with the GTB family. Only the crate identity changed:
//! types, modules, Cargo features, and the `RTB_VCS_GIT_TOKEN` auth
//! environment variable are exactly those of `rtb-vcs` 0.7.0.
//!
//! # What this crate is
//!
//! A narrow, read-only abstraction over release-source APIs. Tool
//! authors pick one of six backends — GitHub, GitLab, Bitbucket, Gitea,
//! Codeberg, or Direct (bare HTTPS URL) — and `rtb-update` consumes the
//! trait to list, fetch, and download release artefacts.
//!
//! # What this crate is not
//!
//! - **Not Git.** Repository operations (`Repo`, clone, fetch, commit
//! walk) land as `rtb-forge` v0.2 at the v0.5 roadmap milestone.
//! - **Not writeable.** `ReleaseProvider` has four methods, all of them
//! read-only. Creating releases, uploading assets, and editing tags
//! are deliberately out of scope.
//! - **Not a caching layer.** Every call hits the wire. Downstream
//! tools add HTTP caching via `reqwest::ClientBuilder::middleware`
//! if they need it.
//!
//! # Foundation
//!
//! The v0.1.1 release ships the foundation only — trait, value types,
//! error enum, config structs, and the `linkme`-backed factory
//! registry. Backend implementations land in follow-up releases,
//! feature-gated so downstream tools only compile what they use.
// `deny` rather than `forbid` — identical in strictness but allows the
// targeted `#[allow(unsafe_code)]` below for the built-in backends'
// `#[distributed_slice(RELEASE_PROVIDERS)]` registrations. `linkme`
// emits `#[link_section]` attributes at the registration sites, and
// Rust 1.95+ attributes that behaviour to the `unsafe_code` lint.
// Every other rtb-* crate keeps `forbid` because they register into
// slices declared in *other* crates (`rtb_app::BUILTIN_COMMANDS`),
// which puts the emission behind a cross-crate boundary and out of
// the `forbid`'s view. `rtb-forge` is the first crate that declares
// AND registers in the same library, so it needs the override.
// Consumers still get the guarantee via the `[lints.rust]`
// `unsafe_code = "deny"` in Cargo.toml — nothing in this crate
// writes hand-rolled `unsafe` blocks.
// v0.5 git-operations slice — entire module gated on the `git` feature.
// See `docs/development/specs/2026-05-11-v0.5-scope.md`.
// Shared HTTP helpers for the REST-API backends. `pub(crate)` —
// downstream custom backends roll their own.
pub
pub use ;
pub use ;