chore(deps): bump typescript to 6.0.3

[idanlodzki]

Replaces #113.

Why not TypeScript 7

#113 looks green, but only because the Docusaurus build never invokes tsc. Running this repo's own npm run typecheck on it:

tsconfig.json(5,5): error TS5102: Option 'baseUrl' has been removed.
  Use '"paths": {"*": ["./*"]}' instead.

TS 7 removes baseUrl outright. TypeScript 6 is the supported intermediate step, so this takes that instead.

The baseUrl situation

TS 6 deprecates baseUrl rather than removing it — and the deprecation can't actually be resolved in this repo. @docusaurus/tsconfig sets baseUrl upstream:

// node_modules/@docusaurus/tsconfig/tsconfig.json
"baseUrl": ".",
"paths": { "@site/*": ["./*"] }

So the warning fires on the inherited option even after removing ours — I tried, and TS5101 just moves to pointing at the compilerOptions block. Our local baseUrl: "." exists to re-anchor that alias to the project directory rather than the package's own location inside node_modules, so dropping it would be a silent behaviour change, not a cleanup.

Added ignoreDeprecations: "6.0" with the reasoning inline. TS 7 here is blocked on Docusaurus shipping a baseUrl-free tsconfig, not on anything in this repo — worth knowing before someone retries the TS 7 bump and hits the same wall.

Incidentally, the @site/* alias this all exists to support isn't used anywhere in the project (zero matches across .ts, .tsx, .md, .mdx). It's inherited config we carry, not something we depend on.

Verification

npm run typecheck and npm run build both pass. The new CI job from #115 exercises both.

Close #113 in favour of this.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Updated the documentation site’s TypeScript tooling.
  • Improved editor configuration for path aliases and compatibility with newer TypeScript versions.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
documentation-opsimate-docs2	Ready	Preview	Aug 2, 2026 4:15pm

[coderabbitai]

📝 Walkthrough

Walkthrough

The documentation project updates its TypeScript development dependency to 6.0.3 and adjusts the editor-only compiler configuration to retain the Docusaurus path alias while suppressing TypeScript 6.0 deprecation warnings.

Changes

TypeScript upgrade

Layer / File(s)	Summary
TypeScript dependency and compiler configuration opsimate-docs/package.json, opsimate-docs/tsconfig.json	The development dependency changes from ~5.6.2 to ^6.0.3. The editor configuration retains baseUrl and adds ignoreDeprecations: "6.0".

Assessment against linked issues

Objective	Addressed	Explanation
Bump TypeScript from 5.6.3 to 7.0.2 [#113]	❌	The dependency is updated to ^6.0.3, not 7.0.2.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@opsimate-docs/package.json`:
- Line 34: Regenerate opsimate-docs/package-lock.json from the updated
TypeScript dependency in package.json so the root dependency range is ^6.0.3 and
the node_modules/typescript entry resolves to 6.0.3, including corresponding
metadata and integrity values.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: a3a39830-159f-4fdf-981f-784542fe48c5

📥 Commits

Reviewing files that changed from the base of the PR and between e250953 and 5861ee6.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (2)

• opsimate-docs/package.json
• opsimate-docs/tsconfig.json

[coderabbitai]

🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

python - <<'PY'
import json
from pathlib import Path

manifest = json.loads(Path("opsimate-docs/package.json").read_text())
lockfile = json.loads(Path("opsimate-docs/package-lock.json").read_text())

assert (
    lockfile["packages"][""]["devDependencies"]["typescript"]
    == manifest["devDependencies"]["typescript"]
)
assert lockfile["packages"]["node_modules/typescript"]["version"] == "6.0.3"
PY

Repository: OpsiMate/documentation

Length of output: 248

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== package.json relevant deps =="
python3 - <<'PY'
import json
from pathlib import Path
p=Path("opsimate-docs/package.json")
m=json.loads(p.read_text())
print(m.get("devDependencies", {}).get("typescript"), m.get("dependencies", {}).get("typescript"))
PY

echo "== package-lock files mentioning typescript =="
rg -n '"typescript"|"node_modules/typescript"' opsimate-docs/package-lock.json || true
echo "== lockfile package entry =="
python3 - <<'PY'
import json
from pathlib import Path
lock=json.loads(Path("opsimate-docs/package-lock.json").read_text())
print("root ts range:", lock.get("packages", {}).get("", {}).get("devDependencies", {}).get("typescript"))
for k,v in lock.get("packages", {}).items():
    if k.endswith("node_modules/typescript"):
        print(k, v.get("version"), v.get("resolved"), v.get("dev", False), v.get("devDependencies"))
PY

Repository: OpsiMate/documentation

Length of output: 544

---

Update the lockfile with TypeScript 6.0.3.

opsimate-docs/package-lock.json still lists typescript as ~5.6.2 and resolves 5.6.3, but opsimate-docs/package.json requests ^6.0.3. Regenerate the lockfile so the root dependency range and node_modules/typescript resolved version match 6.0.3.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@opsimate-docs/package.json` at line 34, Regenerate
opsimate-docs/package-lock.json from the updated TypeScript dependency in
package.json so the root dependency range is ^6.0.3 and the
node_modules/typescript entry resolves to 6.0.3, including corresponding
metadata and integrity values.