@eduardbar/drift 0.9.0 → 1.0.0

package/.github/workflows/publish-vscode.yml

@@ -0,0 +1,76 @@
+name: Publish VS Code Extension
+
+on:
+  release:
+    types: [published]
+  workflow_dispatch:
+    inputs:
+      version:
+        description: 'Version to publish (e.g. 0.1.1)'
+        required: true
+        type: string
+
+permissions:
+  contents: read
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    defaults:
+      run:
+        working-directory: packages/vscode-drift
+
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+        with:
+          ref: ${{ github.event_name == 'release' && github.ref || github.event.repository.default_branch }}
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: '20'
+          cache: 'npm'
+          cache-dependency-path: packages/vscode-drift/package-lock.json
+
+      - name: Verify version matches tag
+        if: github.event_name == 'release'
+        run: |
+          if [ "${{ github.event_name }}" = "workflow_dispatch" ]; then
+            TAG_VERSION="${{ inputs.version }}"
+          else
+            TAG_VERSION="${GITHUB_REF#refs/tags/v}"
+          fi
+          PKG_VERSION=$(node -p "require('./package.json').version")
+          if [ "$TAG_VERSION" != "$PKG_VERSION" ]; then
+            echo "Error: Tag version ($TAG_VERSION) does not match package.json version ($PKG_VERSION)"
+            exit 1
+          fi
+          echo "Version check passed: $PKG_VERSION"
+
+      - name: Check if version already published
+        run: |
+          PKG_VERSION=$(node -p "require('./package.json').version")
+          PUBLISHED=$(npx @vscode/vsce show eduardbar.vscode-drift 2>&1 | grep "Version:" | awk '{print $2}' || echo "none")
+          if [ "$PUBLISHED" = "$PKG_VERSION" ]; then
+            echo "Version $PKG_VERSION already published on Marketplace. Skipping."
+            echo "skip_publish=true" >> $GITHUB_ENV
+          fi
+
+      - name: Install dependencies
+        if: env.skip_publish != 'true'
+        run: npm ci
+
+      - name: Build extension
+        if: env.skip_publish != 'true'
+        run: npm run build
+
+      - name: Package extension
+        if: env.skip_publish != 'true'
+        run: npx @vscode/vsce package --no-dependencies
+
+      - name: Publish to VS Code Marketplace
+        if: env.skip_publish != 'true'
+        run: npx @vscode/vsce publish --no-dependencies
+        env:
+          VSCE_PAT: ${{ secrets.VSCE_PAT }}

package/AGENTS.md

@@ -88,18 +88,35 @@ npx @eduardbar/drift scan ./src -o report.md    # exportar Markdown
 
 ## Reglas del analyzer
 
-| Regla | Severidad | Peso | Qué detecta |
-|-------|-----------|------|-------------|
-| `large-file` | error | 20 | Archivos > 300 líneas |
-| `large-function` | error | 15 | Funciones > 50 líneas |
-| `duplicate-function-name` | error | 18 | Nombres de función duplicados (case-insensitive) |
-| `debug-leftover` | warning | 10 | `console.log/warn/error` + `TODO/FIXME/HACK/XXX/TEMP` |
-| `catch-swallow` | warning | 10 | Bloques `catch {}` vacíos |
-| `dead-code` | warning | 8 | Imports nombrados sin usar |
-| `any-abuse` | warning | 8 | Uso explícito de `any` como tipo |
-| `comment-contradiction` | warning | 12 | (reservado — definido en RULE_WEIGHTS) |
-| `no-return-type` | info | 5 | Funciones sin tipo de retorno explícito |
-| `magic-number` | info | 3 | (reservado — definido en RULE_WEIGHTS) |
+| Regla | Severidad | Peso |
+|-------|-----------|------|
+| `large-file` | error | 20 |
+| `large-function` | error | 15 |
+| `duplicate-function-name` | error | 18 |
+| `high-complexity` | error | 15 |
+| `circular-dependency` | error | 14 |
+| `layer-violation` | error | 16 |
+| `comment-contradiction` | warning | 12 |
+| `deep-nesting` | warning | 12 |
+| `semantic-duplication` | warning | 12 |
+| `debug-leftover` | warning | 10 |
+| `catch-swallow` | warning | 10 |
+| `high-coupling` | warning | 10 |
+| `dead-file` | warning | 10 |
+| `hardcoded-config` | warning | 10 |
+| `cross-boundary-import` | warning | 10 |
+| `dead-code` | warning | 8 |
+| `any-abuse` | warning | 8 |
+| `too-many-params` | warning | 8 |
+| `unused-export` | warning | 8 |
+| `inconsistent-error-handling` | warning | 8 |
+| `promise-style-mix` | warning | 7 |
+| `unnecessary-abstraction` | warning | 7 |
+| `naming-inconsistency` | warning | 6 |
+| `unused-dependency` | warning | 6 |
+| `no-return-type` | info | 5 |
+| `over-commented` | info | 4 |
+| `magic-number` | info | 3 |
 
 **Score = suma de pesos capped a 100. Score del proyecto = promedio de archivos.**
 
@@ -199,6 +216,7 @@ Sin esto, Windows no ejecuta el shebang correctamente con ES modules.
 
 | Versión | Cambios principales |
 |---------|---------------------|
+| **1.0.0** | 26 reglas, 131 tests, modular rules, JS/JSX, drift fix/report/diff/ci/badge/trend/blame, VS Code extension |
 | **0.3.0** | `--ai` (LLM-optimized JSON output) + `--fix` (inline suggestions) |
 | **0.2.3** | Fix: bin wrapper para compatibilidad Windows npx |
 | **0.2.2** | Refactor: `formatMarkdown` dividido en helpers + fix CI doble publish |

package/CHANGELOG.md

@@ -7,6 +7,15 @@ This project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.htm
 
 ---
 
+## [0.9.1] — 2026-02-25
+
+### Fixed
+- `drift trend`: `analyzeSingleCommit` now analyses the full project snapshot at each commit instead of only the files changed in the diff. Uses `git ls-tree -r <hash> --name-only` to enumerate all tracked `.ts/.tsx` files, writes them to a temp directory via `git show <hash>:<file>`, runs `analyzeProject` on the snapshot, then cleans up. Score in each `TrendDataPoint` now reflects the total project health, not just the files touched in that commit.
+- `drift trend`: added sampling to `analyzeHistoricalCommits` — selects at most 10 commits distributed evenly across the period (configurable via `maxSamples`). Prevents timeouts on repos with 100+ commits.
+- `drift trend` / `drift blame`: propagate `DriftConfig` through the full call chain (`analyzeTrend` → `analyzeHistoricalCommits` → `analyzeSingleCommit` → `analyzeProject`) so custom rule configs are respected in historical analysis.
+
+---
+
 ## [Unreleased]
 
 ---