blockmine 1.24.0 → 1.27.0

package/.claude/skills/release-engineering/resources/progressive-delivery.md

@@ -1,83 +0,0 @@
-# Progressive Delivery
-
-Feature flags, traffic splitting, gradual rollout, LaunchDarkly, Unleash, and progressive deployment techniques.
-
-## Feature Flags
-
-**LaunchDarkly:**
-```typescript
-import * as ld from 'launchdarkly-node-server-sdk';
-
-const client = ld.init(process.env.LAUNCHDARKLY_SDK_KEY);
-
-await client.waitForInitialization();
-
-const user = {
-  key: 'user@example.com',
-  email: 'user@example.com',
-  custom: {
-    plan: 'premium'
-  }
-};
-
-const showNewFeature = await client.variation('new-feature', user, false);
-
-if (showNewFeature) {
-  // New feature code
-} else {
-  // Old feature code
-}
-```
-
-**Unleash:**
-```typescript
-import { startUnleash } from 'unleash-client';
-
-const unleash = await startUnleash({
-  url: 'https://unleash.example.com/api',
-  appName: 'my-app',
-  customHeaders: {
-    Authorization: process.env.UNLEASH_API_KEY
-  }
-});
-
-if (unleash.isEnabled('new-feature', { userId: 'user@example.com' })) {
-  // New feature
-}
-```
-
-## Traffic Splitting
-
-**Istio VirtualService:**
-```yaml
-apiVersion: networking.istio.io/v1beta1
-kind: VirtualService
-metadata:
-  name: myapp
-spec:
-  hosts:
-  - myapp
-  http:
-  - match:
-    - headers:
-        canary:
-          exact: "true"
-    route:
-    - destination:
-        host: myapp
-        subset: v2
-  - route:
-    - destination:
-        host: myapp
-        subset: v1
-      weight: 90
-    - destination:
-        host: myapp
-        subset: v2
-      weight: 10
-```
-
----
-
-**Related Resources:**
-- [deployment-strategies.md](deployment-strategies.md)

package/.claude/skills/release-engineering/resources/release-automation.md

@@ -1,68 +0,0 @@
-# Release Automation
-
-Automated releases, changelog generation, release notes, semantic release, and git tag automation.
-
-## Semantic Release
-
-**Configuration:**
-```json
-{
-  "branches": ["main"],
-  "plugins": [
-    "@semantic-release/commit-analyzer",
-    "@semantic-release/release-notes-generator",
-    "@semantic-release/changelog",
-    "@semantic-release/npm",
-    "@semantic-release/github",
-    "@semantic-release/git"
-  ]
-}
-```
-
-**Commit Conventions:**
-```
-feat: New feature (minor version bump)
-fix: Bug fix (patch version bump)
-BREAKING CHANGE: Breaking change (major version bump)
-docs: Documentation only
-chore: Maintenance tasks
-```
-
-## GitHub Release Action
-
-```yaml
-name: Release
-
-on:
-  push:
-    tags:
-      - 'v*'
-
-jobs:
-  release:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v3
-
-      - name: Generate Changelog
-        id: changelog
-        run: |
-          echo "## Changes" > CHANGELOG.md
-          git log $(git describe --tags --abbrev=0 HEAD^)..HEAD --pretty=format:"- %s (%an)" >> CHANGELOG.md
-
-      - name: Create Release
-        uses: softprops/action-gh-release@v1
-        with:
-          body_path: CHANGELOG.md
-          files: |
-            dist/*
-            *.tar.gz
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-```
-
----
-
-**Related Resources:**
-- [versioning-strategies.md](versioning-strategies.md)
-- [ci-cd-pipelines.md](ci-cd-pipelines.md)

package/.claude/skills/release-engineering/resources/release-orchestration.md

@@ -1,77 +0,0 @@
-# Release Orchestration
-
-Multi-service deployments, dependency management, coordinated releases, and release coordination strategies.
-
-## Multi-Service Deployment
-
-**Helm Umbrella Chart:**
-```yaml
-# umbrella-chart/Chart.yaml
-apiVersion: v2
-name: myapp
-version: 1.0.0
-dependencies:
-  - name: api-service
-    version: "1.2.0"
-    repository: "file://../api-service"
-  - name: worker-service
-    version: "1.1.0"
-    repository: "file://../worker-service"
-  - name: frontend
-    version: "2.0.0"
-    repository: "file://../frontend"
-```
-
-**Deploy Order:**
-```bash
-# 1. Deploy dependencies first
-helm upgrade database ./charts/database
-
-# 2. Deploy backend services
-helm upgrade api-service ./charts/api-service
-helm upgrade worker-service ./charts/worker-service
-
-# 3. Deploy frontend last
-helm upgrade frontend ./charts/frontend
-```
-
-## Dependency Management
-
-**Service Dependencies:**
-```yaml
-# api-service depends on database
-deployment:
-  init_containers:
-    - name: wait-for-db
-      image: busybox
-      command: ['sh', '-c', 'until nc -z postgres 5432; do sleep 1; done']
-```
-
-**ArgoCD Sync Waves:**
-```yaml
-metadata:
-  annotations:
-    argocd.argoproj.io/sync-wave: "1"  # Deploy first
----
-metadata:
-  annotations:
-    argocd.argoproj.io/sync-wave: "2"  # Deploy second
-```
-
-## Release Coordination
-
-**Feature Toggles for Coordination:**
-```typescript
-// Release both services, enable feature after both deployed
-if (featureFlags.isEnabled('new-api-integration')) {
-  // Use new API
-} else {
-  // Use old API
-}
-```
-
----
-
-**Related Resources:**
-- [deployment-strategies.md](deployment-strategies.md)
-- [progressive-delivery.md](progressive-delivery.md)

package/.claude/skills/release-engineering/resources/rollback-strategies.md

@@ -1,66 +0,0 @@
-# Rollback Strategies
-
-Automated rollback, manual rollback procedures, database rollback, and recovery strategies.
-
-## Automated Rollback
-
-**Kubernetes with Flagger:**
-```yaml
-apiVersion: flagger.app/v1beta1
-kind: Canary
-metadata:
-  name: myapp
-spec:
-  analysis:
-    threshold: 5  # Rollback after 5 failed checks
-    metrics:
-    - name: request-success-rate
-      thresholdRange:
-        min: 99  # Rollback if success rate < 99%
-    - name: request-duration
-      thresholdRange:
-        max: 500  # Rollback if p95 > 500ms
-```
-
-## Manual Rollback
-
-**Kubernetes:**
-```bash
-# Rollback to previous version
-kubectl rollout undo deployment/myapp
-
-# Rollback to specific revision
-kubectl rollout history deployment/myapp
-kubectl rollout undo deployment/myapp --to-revision=2
-
-# Check rollback status
-kubectl rollout status deployment/myapp
-```
-
-**Blue-Green Rollback:**
-```bash
-# Switch back to blue (old version)
-kubectl patch service myapp -p '{"spec":{"selector":{"version":"blue"}}}'
-```
-
-## Database Rollback
-
-**Backward Compatible Migrations:**
-```sql
--- Step 1: Add new column (nullable)
-ALTER TABLE users ADD COLUMN new_email VARCHAR(255);
-
--- Step 2: Backfill data
-UPDATE users SET new_email = old_email;
-
--- Step 3: Make non-nullable (in next release)
--- ALTER TABLE users ALTER COLUMN new_email SET NOT NULL;
-
--- Step 4: Drop old column (in future release)
--- ALTER TABLE users DROP COLUMN old_email;
-```
-
----
-
-**Related Resources:**
-- [deployment-strategies.md](deployment-strategies.md)

package/.claude/skills/release-engineering/resources/versioning-strategies.md

@@ -1,59 +0,0 @@
-# Versioning Strategies
-
-Semantic versioning (SemVer), calendar versioning (CalVer), Git-based versioning, and version management.
-
-## Semantic Versioning (SemVer)
-
-**Format:** MAJOR.MINOR.PATCH
-
-```
-v1.0.0 - Initial release
-v1.0.1 - Patch: Bug fix
-v1.1.0 - Minor: New feature (backward compatible)
-v2.0.0 - Major: Breaking change
-```
-
-**Implementation:**
-```bash
-# Tag release
-git tag -a v1.2.3 -m "Release version 1.2.3"
-git push origin v1.2.3
-
-# Auto-increment with npm
-npm version patch  # 1.0.0 → 1.0.1
-npm version minor  # 1.0.0 → 1.1.0
-npm version major  # 1.0.0 → 2.0.0
-```
-
-## Calendar Versioning (CalVer)
-
-**Format:** YYYY.MM.MICRO or YY.MM.MICRO
-
-```
-2024.01.0 - January 2024, first release
-2024.01.1 - January 2024, second release
-2024.02.0 - February 2024, first release
-```
-
-**Use Cases:**
-- Time-based releases
-- Marketing-driven versioning
-- Infrastructure tools (Ubuntu, Poetry)
-
-## Git-Based Versioning
-
-**Git Describe:**
-```bash
-# v1.2.3-14-g2414721
-# v1.2.3: Last tag
-# 14: Commits since tag
-# g2414721: Git commit hash
-
-git describe --tags --always
-```
-
----
-
-**Related Resources:**
-- [artifact-management.md](artifact-management.md)
-- [release-automation.md](release-automation.md)