SeliseBlocks.ReleaseDriver.OS 4.0.4

.NET 10.0

dotnet add package SeliseBlocks.ReleaseDriver.OS --version 4.0.4

NuGet\Install-Package SeliseBlocks.ReleaseDriver.OS -Version 4.0.4

This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.

<PackageReference Include="SeliseBlocks.ReleaseDriver.OS" Version="4.0.4" />

For projects that support PackageReference, copy this XML node into the project file to reference the package.

<PackageVersion Include="SeliseBlocks.ReleaseDriver.OS" Version="4.0.4" />
                    

                            Directory.Packages.props

<PackageReference Include="SeliseBlocks.ReleaseDriver.OS" />
                    

                            Project file

For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.

paket add SeliseBlocks.ReleaseDriver.OS --version 4.0.4

The NuGet Team does not provide support for this client. Please contact its maintainers for support.

#r "nuget: SeliseBlocks.ReleaseDriver.OS, 4.0.4"

#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.

#:package SeliseBlocks.ReleaseDriver.OS@4.0.4

#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package.

#addin nuget:?package=SeliseBlocks.ReleaseDriver.OS&version=4.0.4
                    

                            Install as a Cake Addin

#tool nuget:?package=SeliseBlocks.ReleaseDriver.OS&version=4.0.4
                    

                            Install as a Cake Tool

The NuGet Team does not provide support for this client. Please contact its maintainers for support.

SeliseBlocks.ReleaseDriver.OS

A NuGet package that exposes release and repository management operations for Blocks-based applications.

Installation

dotnet add package SeliseBlocks.ReleaseDriver.OS

Registration

Secrets are loaded from the vault, then the domain services and the driver are registered:

await builder.Services.RegisterBlocksReleaseServicesAsync();

// or, to read from a non-Azure vault (defaults to VaultType.Azure)
await builder.Services.RegisterBlocksReleaseServicesAsync(VaultType.OnPrem);

Usage

Inject IReleaseDriverService and call any of the available methods:

public class MyService
{
    private readonly IReleaseDriverService _release;

    public MyService(IReleaseDriverService release)
    {
        _release = release;
    }
}

Available Operations

Method	Description
`IsAuthorizeAsync()`	Checks whether the current user has a valid access token
`GetAccessTokenAsync(code)`	Exchanges an OAuth authorization code for an access token
`RemoveAuthorizationAsync()`	Revokes the current user's OAuth access from the provider
`DeleteAuthorizationAsync()`	Deletes the stored access token for the current user
`GetReposListAsync()`	Retrieves the repository list; archived repositories are excluded
`GetRepoDetailsAsync(repoId, branch, pageNumber, pageSize)`	Retrieves a repository with its paged build history
`GetReportsAsync(buildId, type)`	Retrieves test and analysis reports produced by a build
`GetUserAsync()`	Retrieves the authenticated GitHub user
`SearchRepositoriesAsync(search, pageNumber, pageSize)`	Searches the authenticated user's GitHub repositories
`GetBranchesAsync(repo)`	Retrieves the branches for the specified GitHub repository
`GithubBranchExistsAsync(repoId)`	Checks whether the configured branch exists for the given repository
`UpdateRepoDomainAsync(request)`	Updates the custom deployment domains for the given repositories

Migrating from 4.x

4.x shipped these types under the DeploymentDriver name. 5.0.0 renames them to match the package id. The rename is the only change — every method behaves exactly as it did in 4.x.

4.x	5.0.0
`namespace DeploymentDriver`	`namespace ReleaseDriver`
`IDeploymentDriverService`	`IReleaseDriverService`
`DeploymentDriverService`	`ReleaseDriverService`
`RegisterBlocksDeploymentServicesAsync()`	`RegisterBlocksReleaseServicesAsync()`

Product	Compatible and additional computed target framework versions.
.NET	net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed.

Compatible target framework(s)

Included target framework(s) (in package)

Learn more about Target Frameworks and .NET Standard.

net10.0
- FluentValidation (>= 12.0.0)
- KubernetesClient (>= 17.0.14)
- Microsoft.Extensions.Hosting (>= 9.0.2)
- MongoDB.Driver (>= 3.8.0)
- Newtonsoft.Json (>= 13.0.3)
- SeliseBlocks.Genesis.OS (>= 4.2.3)
- SeliseBlocks.Secrets.OS (>= 4.0.3)

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version	Downloads	Last Updated
4.0.4	61	10/13/2026
4.0.3	242	9/29/2026
4.0.2	409	9/27/2026
4.0.1	1,521	8/13/2026
4.0.0	1,417	7/29/2026

GitHub access tokens are stored in Azure Key Vault through the Blocks.Secrets value store; the RepositoryTokens row keeps only TokenSecretId. Rows with a plaintext AccessToken stay readable and move to the vault on the user's next connect, so no data migration is needed. The host must resolve ISecretValueStore to the Key Vault store (KeyVault__KeyVaultUrl set, Secrets__ValueStore unset or KeyVault): with the database store, connecting, revoking and building webhooks fail with a token-store error, while legacy plaintext tokens keep working. RegisterBlocksReleaseServicesAsync calls AddBlocksSecrets(), whose registrations are TryAdd, so a host's own call made first is kept. The package now declares its SeliseBlocks.Secrets.OS dependency, which 4.0.3 bundled an assembly reference to without declaring. No API removals.