Add comprehensive version configuration with metadata to deployment workflow

[Copilot]

This PR implements dynamic version switching by publishing comprehensive version info to S3 after each frontend deployment, enabling instant version switching without infrastructure changes.

Changes Made

GitHub Actions Workflow (publish.yml)

Added two new steps to the deployment workflow that run after successful S3 upload:

1. Create version info: Generates a comprehensive config/version.json file with:
   • Current deployed version
   • Description and timestamp
   • Rollback version field
   • Deployment metadata (deployed by, environment)
2. Upload version info: Uploads the file to s3://bucket/config/version.json at the S3 bucket root

The version file format is:

{
  "version": "0.4.0",
  "description": "Current frontend version configuration",
  "lastUpdated": "2024-01-01T00:00:00Z",
  "rollbackVersion": "0.3.0",
  "metadata": {
    "deployedBy": "github-actions",
    "environment": "production"
  }
}

Documentation (README.md)

Added comprehensive documentation covering:

• How the version management system works with the new format
• Step-by-step deployment instructions
• Rollback procedures without redeployment
• Benefits and future capabilities

Benefits

Immediate:

• ✅ Instant version switching by updating a single JSON file
• ✅ Simple rollback mechanism without redeploying infrastructure
• ✅ Version info accessible to CloudFront for dynamic routing
• ✅ Rich metadata for deployment tracking

Future enablement:

• 🚀 A/B testing capabilities
• 🚀 Canary deployments
• 🚀 Advanced deployment strategies

Example Usage

Deploy new version:
Run the "Publish to s3" workflow with version v1.2.4 → automatically updates config/version.json

Rollback to previous version:
Manually update S3 file: change "version": "1.2.4" to "version": "1.2.3" → instant rollback

The implementation is minimal and surgical, adding only the necessary functionality without modifying existing deployment logic.

Fixes #99.

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.

[saebyn]

This is the format expected for the config/version.json:

{
  "version": "0.4.0",
  "description": "Current frontend version configuration",
  "lastUpdated": "2024-01-01T00:00:00Z",
  "rollbackVersion": "0.3.0",
  "metadata": {
    "deployedBy": "system",
    "environment": "production"
  }
}

[saebyn]

@copilot can you update this PR to match?

[Copilot]

@copilot can you update this PR to match?

Updated the version configuration format to match the expected structure. The workflow now generates a comprehensive JSON file with version, description, timestamp, rollback version, and deployment metadata. Commit: 92517cf

done

[Copilot]

Pull Request Overview

This PR implements a dynamic version management system for frontend deployments by adding comprehensive version configuration metadata. The changes enable instant version switching and rollback capabilities without requiring infrastructure redeployment.

Key changes:

• Added automated version configuration file generation to the deployment workflow
• Created comprehensive documentation for the new version management system
• Implemented S3-based version tracking with deployment metadata

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
.github/workflows/publish.yml	Added two new steps to generate and upload version configuration JSON with deployment metadata
README.md	Added comprehensive documentation covering version management workflow, deployment procedures, and rollback instructions