Skip to content

Release v0.1.0-beta.2: End-to-End Process Validation #459

@josecelano

Description

@josecelano

Overview

Execute the second pre-release of the Torrust Tracker Deployer, validating the
full release workflow after the fixes and improvements made during and after the
beta.1 cycle. Version 0.1.0-beta.2 serves as a second validation gate before
cutting the final v0.1.0 release.

Specification

See detailed specification: docs/issues/459-release-v0-1-0-beta-2-end-to-end-validation.md

Implementation Plan

Phase 1: Pre-Flight and Setup

  • Task 1.1: Verify local workspace is clean and on torrust/main up-to-date with origin/main
  • Task 1.2: Confirm GitHub environments dockerhub-torrust and crates-io are still configured
  • Task 1.3: Confirm releaser has push access to main, tags, and release branches
  • Task 1.4: Document any pre-flight issues found

Phase 2: Execute the Release

  • Task 2.1: Update version to 0.1.0-beta.2 in all four Cargo.toml files and in every internal path dependency constraint
  • Task 2.2: Run cargo build && cargo test and verify they pass
  • Task 2.3: Run ./scripts/pre-commit.sh and verify all checks pass
  • Task 2.4: Create and push the signed release commit to main
  • Task 2.5: Create and push annotated signed tag v0.1.0-beta.2
  • Task 2.6: Create and push release branch releases/v0.1.0-beta.2
  • Task 2.7: Monitor Container and Publish Crate workflows to completion

Phase 3: Artifact Verification

  • Task 3.1: Pull and inspect Docker image torrust/tracker-deployer:0.1.0-beta.2
  • Task 3.2: Verify all four crates at 0.1.0-beta.2 are visible on crates.io
  • Task 3.3: Verify docs.rs build for the published crate versions
  • Task 3.4: Create GitHub release from tag v0.1.0-beta.2

Phase 4: Process Review and Fixes

  • Task 4.1: Collect every friction point, error, or unexpected step encountered during the release
  • Task 4.2: Fix the root cause in the relevant artifact (docs/release-process.md, .github/skills/dev/git-workflow/release-new-version/skill.md, scripts/, .github/workflows/, etc.)
  • Task 4.3: File follow-up issues for any non-trivial problems
  • Task 4.4: Re-run ./scripts/pre-commit.sh after any fixes
  • Task 4.5: Confirm all finalization gates are met

Acceptance Criteria

Quality Checks:

  • Pre-commit checks pass: ./scripts/pre-commit.sh

Release Execution:

  • Version 0.1.0-beta.2 is committed and present in all four Cargo.toml files on main
  • Tag v0.1.0-beta.2 exists and is signed
  • Branch releases/v0.1.0-beta.2 exists
  • Container workflow completed successfully
  • Publish Crate workflow completed successfully
  • GitHub release v0.1.0-beta.2 is published (not draft)

Artifact Verification:

  • Docker image torrust/tracker-deployer:0.1.0-beta.2 can be pulled and run
  • All four crates at 0.1.0-beta.2 are visible on crates.io:
    • torrust-tracker-deployer-types@0.1.0-beta.2
    • torrust-tracker-deployer-dependency-installer@0.1.0-beta.2
    • torrust-tracker@0.1.0-beta.2
    • torrust-tracker-deployer-sdk@0.1.0-beta.2
  • docs.rs build page loads for the published versions

Process Quality:

  • Every friction point or error encountered is documented (inline comment or filed follow-up issue)
  • Every fixable problem is fixed in the relevant artifact — documentation, skill, script, or workflow — not just noted
  • No step was silently skipped or improvised without documentation
  • docs/release-process.md and the release skill accurately reflect how the release was actually executed

Related

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions