ci: pin Swatinem/rust-cache to v2.9.1 for release workflow compliance - #84
Merged
Vladyslav Nikonov (vnikonov-devolutions) merged 6 commits intoJul 27, 2026
Conversation
Add Apt, Bun, Cargo, Chocolatey, Dnf, Dotnet, Flatpak, Homebrew, Npm, Pacman, Pip, Scoop, Snap, and Vcpkg to the policy and broker API manager enums (Rust and .NET), bump the broker API version to 1.1, and regenerate the OpenAPI document and policy JSON schema. Managers introduced in 1.1 are version-gated: ManagerName exposes its minimum API version, CapabilitiesResponse gains manager support check methods distinguishing a protocol-version gap from a missing capability, and the .NET client refuses to send a too-new manager to an older broker with a distinct UnsupportedApiVersion error kind. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
- Revert crate versions to 0.1.0 (managed by cargo-release) and fixture ServerVersion back to 0.1.0 - Add IncompatibleApiVersion to ManagerSupport (Rust + .NET) so a broker with a different major API version or malformed version is no longer misclassified as RequiresNewerApiVersion; client raises a distinct message for it - Version the policy schema: bump canonical URI to now-policy.schema.1.1.json, keep accepting the 1.0 URI on read (Rust marker + .NET consts), default PolicyVersion to 1.1.0, regenerate schema JSON - Strengthen version-gating test: old broker now advertises Chocolatey and the version gate still wins; add incompatible-major tests in both languages - Reword 'broker speaks version' to 'broker advertises version' Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
A broker with a different major API version fails much earlier, when parsing the response envelope, so classifying it per-manager is not meaningful. Keep ManagerSupport focused on Supported / RequiresNewerApiVersion / NotAdvertised in both Rust and .NET. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
We are not in a release state, so breaking version compatibility is acceptable: the expanded manager set ships as part of the existing 1.0 contract. Removes the redundant versioning machinery: - API_VERSION_STR / BrokerApi.Version back to 1.0 (fixtures included) - Drop ManagerName::minimum_api_version / GetMinimumApiVersion, ApiVersion::supports / ApiVersionSupports and ManagerSupport - Drop the BrokerClient protocol-version gate and BrokerClientErrorKind.UnsupportedApiVersion - Policy schema URI and PolicyVersion defaults back to 1.0 / 1.0.0; regenerate schema and OpenAPI Capability checking stays via CapabilitiesResponse::supports_manager / manager_capability (SupportsManager / GetManagerCapability in .NET). Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot started work on behalf of
Vladyslav Nikonov (vnikonov-devolutions)
July 27, 2026 19:45
View session
Copilot started work on behalf of
Vladyslav Nikonov (vnikonov-devolutions)
July 27, 2026 19:51
View session
Vladyslav Nikonov (vnikonov-devolutions)
changed the base branch from
feat/add-more-package-managers
to
master
July 27, 2026 19:52
Vladyslav Nikonov (vnikonov-devolutions)
marked this pull request as ready for review
July 27, 2026 19:53
Vladyslav Nikonov (vnikonov-devolutions)
requested review from
a team
as code owners
July 27, 2026 19:53
Marc-André Moreau (mamoreau-devolutions)
approved these changes
Jul 27, 2026
Vladyslav Nikonov (vnikonov-devolutions)
enabled auto-merge (squash)
July 27, 2026 19:55
Vladyslav Nikonov (vnikonov-devolutions)
merged commit Jul 27, 2026
7157ff6
into
master
10 checks passed
Vladyslav Nikonov (vnikonov-devolutions)
deleted the
copilot/featpolicies-add-package-managers-to-api
branch
July 27, 2026 19:56
Contributor
|
IMPORTANT: This branch accidentially had merged changes from #83 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Create New Releasewas failing because the workflow policy blocksSwatinem/rust-cache@v2.8.2. This updates the cache action pin to the allowlistedv2.9.1and aligns all repository references accordingly.What changed
.github/actions/setup-rust-cache/action.yml:Swatinem/rust-cache@v2.8.2→Swatinem/rust-cache@v2.9.1Repository consistency
Swatinem/rust-cachereferences and aligned all occurrences tov2.9.1(no additional versioned references remained).Snippet
(Same issue as in devolutions-gateway, PR: ci: pin Swatinem/rust-cache to v2.9.1 for release workflow compliance devolutions-gateway#1868)