Skip to content

Commit d8f8c43

Browse files
authored
Merge pull request #10 from ManuelGil/dependabot/npm_and_yarn/main/biomejs/biome-2.3.13
chore(deps-dev): bump @biomejs/biome from 2.3.12 to 2.3.13
2 parents 36139dd + 075cb10 commit d8f8c43

File tree

4 files changed

+116
-135
lines changed

4 files changed

+116
-135
lines changed

.github/workflows/ci.yml

Lines changed: 22 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -1,59 +1,56 @@
11
# CI for VS Code Extension
22
# -----------------------
3-
# This workflow validates Pull Requests before merging into main.
3+
# This workflow runs on Pull Requests targeting the main branch.
4+
# It ensures that the extension installs dependencies correctly
5+
# and that the TypeScript sources compile without errors.
46
#
5-
# Design goals:
6-
# - Low maintenance and low noise
7-
# - Deterministic Node version via .nvmrc
8-
# - pnpm-based dependency management
9-
# - Compile-only check (no tests yet)
10-
#
11-
# This is the recommended baseline CI for a VS Code extension.
7+
# Scope:
8+
# - Node.js version is defined by .nvmrc
9+
# - Dependencies are managed with pnpm
10+
# - Only compilation is verified (no tests are executed)
1211

1312
name: CI
1413

15-
# Run CI only on Pull Requests targeting main
1614
on:
1715
pull_request:
1816
branches:
1917
- main
2018

2119
jobs:
2220
compile:
23-
# Ubuntu is the standard and most stable runner for VS Code extensions
21+
# Ubuntu provides a stable and widely supported environment
22+
# for building and compiling VS Code extensions.
2423
runs-on: ubuntu-latest
2524

2625
steps:
27-
# Checkout repository source code
26+
# Fetch the repository contents for the workflow run
2827
- name: Checkout repository
2928
uses: actions/checkout@v4
3029

31-
# Setup pnpm
32-
# - Installs a pinned pnpm version
33-
# - Enables native pnpm store caching
34-
# - More reliable on modern Ubuntu runners than setup-node caching
30+
# Install pnpm and make it available in the environment.
31+
# pnpm also manages its own dependency store cache.
3532
- name: Setup pnpm
3633
uses: pnpm/action-setup@v4
3734
with:
3835
version: 10
39-
cache: true
4036

41-
# Setup Node.js runtime
42-
# - Uses .nvmrc as the single source of truth
43-
# - No dependency caching here (handled by pnpm)
37+
# Configure the Node.js runtime using the version
38+
# specified in the .nvmrc file.
4439
- name: Setup Node.js
4540
uses: actions/setup-node@v4
4641
with:
4742
node-version-file: ".nvmrc"
43+
cache: "pnpm"
44+
cache-dependency-path: "pnpm-lock.yaml"
4845

49-
# Install dependencies
50-
# - Ensures pnpm-lock.yaml is respected
51-
# - Fails fast if the lockfile is out of sync
46+
# Install dependencies exactly as defined in pnpm-lock.yaml.
47+
# The workflow will fail if the lockfile and package.json
48+
# are not in sync.
5249
- name: Install dependencies
5350
run: pnpm install --frozen-lockfile
5451

55-
# Compile VS Code extension
56-
# - Typically runs TypeScript compilation (tsc)
57-
# - Core validation step for this project
52+
# Compile the VS Code extension.
53+
# This step typically runs the TypeScript compiler and
54+
# validates the project configuration.
5855
- name: Compile extension
5956
run: pnpm compile

package.json

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -941,12 +941,10 @@
941941
"prepare": "husky"
942942
},
943943
"devDependencies": {
944-
"@biomejs/biome": "2.3.12",
944+
"@biomejs/biome": "2.3.13",
945945
"@commitlint/cli": "^20.3.1",
946946
"@commitlint/config-conventional": "^20.3.1",
947947
"@compodoc/compodoc": "^1.2.1",
948-
"@types/glob": "^9.0.0",
949-
"@types/minimatch": "^6.0.0",
950948
"@types/mocha": "^10.0.10",
951949
"@types/node": "^24.10.9",
952950
"@types/vscode": "^1.90.0",
@@ -957,6 +955,7 @@
957955
"glob": "^13.0.0",
958956
"husky": "^9.1.7",
959957
"lint-staged": "^16.2.7",
958+
"minimatch": "^10.1.1",
960959
"rimraf": "^6.1.2",
961960
"typescript": "^5.9.3"
962961
},

pnpm-lock.yaml

Lines changed: 41 additions & 60 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

0 commit comments

Comments
 (0)