:robot: I have created a release *beep* *boop*
---
<details><summary>1.1.0</summary>
## [1.1.0](https://github.com/CV_Website/CV_Site_Nuxt/compare/v1.0.0...v1.1.0) (2026-10-18)
### Features
* add nuxt application shell ([5caa345](https://github.com/CV_Website/CV_Site_Nuxt/commit/5caa3457aa8f97dfca94059b15f8330e97bfb041))
* added dockerignore, a development docker image and a qa/prod docker image ([1a78935](https://github.com/CV_Website/CV_Site_Nuxt/commit/1a78935c23ef2c756912d9f561a69569c2f45d2f))
* extend ESLint config with default rule set ([e4ea5c3](https://github.com/CV_Website/CV_Site_Nuxt/commit/e4ea5c3e7c74c4d2c700ced71372da13e031eb6c))
* merged main into this branch ([cefdb34](https://github.com/CV_Website/CV_Site_Nuxt/commit/cefdb34d7ec33a176714388a4a0805177e8c4216))
* set up ESLint and typecheck with @nuxt/eslint ([4e2a03e](https://github.com/CV_Website/CV_Site_Nuxt/commit/4e2a03eab88495cbfa9db861919189da0c4b2889))
### Bug Fixes
* **ci:** address AI review findings (credentials, supply chain) ([85f488a](https://github.com/CV_Website/CV_Site_Nuxt/commit/85f488a94dd8796ea5f11c292edddd32e21398cd))
* **ci:** apply review findings round two ([a3e6aef](https://github.com/CV_Website/CV_Site_Nuxt/commit/a3e6aef901086f5f8b416e2aa7d29596517f9550))
* **ci:** close the fail-open gate, enforce read-only sandbox ([3e68e63](https://github.com/CV_Website/CV_Site_Nuxt/commit/3e68e630dff92a7abd791b7a8808eb682f37a060))
* **ci:** deny write tools, never swallow review errors ([f8d1287](https://github.com/CV_Website/CV_Site_Nuxt/commit/f8d128705faa9493202cf724ae0a451d4dc6d1e5))
* **ci:** give release-please git credentials for the release-branch push ([a27bbbb](https://github.com/CV_Website/CV_Site_Nuxt/commit/a27bbbb2abf0fa8ddedd20c05bba2128e88faa3a))
* **ci:** hand review diff to agent as file, not argv ([16b9291](https://github.com/CV_Website/CV_Site_Nuxt/commit/16b9291a5111b93d6e7da244f821589fa3432d87))
* **ci:** install opencode v2 for the review job ([783c9cc](https://github.com/CV_Website/CV_Site_Nuxt/commit/783c9ccda369fe5ec05ea5085488998de125045c))
* **ci:** JSON-encode review with node instead of jq ([a061fad](https://github.com/CV_Website/CV_Site_Nuxt/commit/a061fad9b1933414faa7e6a26bd3182c0ce6c9d7))
* **ci:** make droast job actually run ([cf6f209](https://github.com/CV_Website/CV_Site_Nuxt/commit/cf6f209ebf03c3a4faf4e32971ba036d60ddb36b))
* **ci:** pass --all-projects to snyk test ([7197f75](https://github.com/CV_Website/CV_Site_Nuxt/commit/7197f757a6447cf29a11f60914d89939bd647040))
* **ci:** pick gitleaks binary by CPU architecture ([88dadd5](https://github.com/CV_Website/CV_Site_Nuxt/commit/88dadd584627e963b4dee719768644626e343488))
* **ci:** point release-please at PR_GITEA_TOKEN (write scopes) ([e1192a2](https://github.com/CV_Website/CV_Site_Nuxt/commit/e1192a2014da8acfea37c5319f0b612f9f5a392e))
* **ci:** pull gitleaks from GHCR and pin version ([ce9c090](https://github.com/CV_Website/CV_Site_Nuxt/commit/ce9c090a150e448919205f9386ff61bfe77dfdb9))
* **ci:** run app jobs from repo root ([bb13f1a](https://github.com/CV_Website/CV_Site_Nuxt/commit/bb13f1a187d482b9bb55dafa303356114ece42ae))
* **ci:** run gitleaks as binary in node image ([779cf20](https://github.com/CV_Website/CV_Site_Nuxt/commit/779cf20f45ec8db009065197140067a531649401))
* **ci:** run Snyk CLI via npm on arm64 runner ([8d2a000](https://github.com/CV_Website/CV_Site_Nuxt/commit/8d2a00062e6381cbba9bdb703b210c8eb2201d92))
* **ci:** use opencode-go plan model for AI review ([8b6bcb6](https://github.com/CV_Website/CV_Site_Nuxt/commit/8b6bcb6d70d123dda551f08ef2c05dc3d50733f2))
* **ci:** use pnpm 11 in runner ([ecd0192](https://github.com/CV_Website/CV_Site_Nuxt/commit/ecd0192466f8d72b9f8532e32b1aea63ff9dd640))
* pass staged filenames to the eslint pre-commit hook ([81d658a](https://github.com/CV_Website/CV_Site_Nuxt/commit/81d658a87105434835016ae20b24ef3cb7617d86))
* remove leftover merge conflict marker from pr-checker.yml ([8f36f14](https://github.com/CV_Website/CV_Site_Nuxt/commit/8f36f14720a4826fe4b4cebdf591994fa0961ae3))
</details>
---
This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
build · deepseek-v4-pro
[0m→ [0mRead .pr-review-diff.patch
build · deepseek-v4-pro
[0m→ [0mRead .pr-review-diff.patch [90m[offset=67][0m
build · deepseek-v4-pro
[0m⚙ [0mexecute {"code":"\nconst fs = await import('fs');\n"}
build · deepseek-v4-pro
[0m✱ [0mGrep "^diff --git" [90min .pr-review-diff.patch · 3 matches[0m
[0m✱ [0mGrep "." [90min .pr-review-diff.patch · 67 matches[0m
build · deepseek-v4-pro
The patch file appears truncated (ends mid-hunk at line 67). Let me verify the repo state to determine if there's more to the PR diff.
[0m→ [0mRead package.json
[0m→ [0mRead .release-please-manifest.json
[0m✱ [0mGlob ".patch" [90m0 matches[0m
build · deepseek-v4-pro
[0m✱ [0mGlob ".pr-review" [90m1 match[0m
[0m✱ [0mGlob "lock" [90m1 match[0m
[0m→ [0mRead CHANGELOG.md [90m[limit=50][0m
build · deepseek-v4-pro
[0m→ [0mRead pnpm-lock.yaml [90m[limit=40][0m
build · deepseek-v4-pro
Reviewed the diff in .pr-review-diff.patch (verified complete against the repo; the @@ -1,6 +1,6 @@ package.json hunk accounts for all lines, including the trailing "scripts": { context line). The PR contains only release metadata: a version bump in .release-please-manifest.json and package.json (both consistent at 1.1.0) and the generated CHANGELOG.md entry. The version bump does not require a pnpm-lock.yaml update (pnpm does not record the root package version), so nothing is stale.
The diff contains no reviewable code (release metadata/docs only).
VERDICT: APPROVE
[0m
> build · deepseek-v4-pro
[0m→ [0mRead .pr-review-diff.patch
> build · deepseek-v4-pro
[0m→ [0mRead .pr-review-diff.patch [90m[offset=67][0m
> build · deepseek-v4-pro
[0m⚙ [0mexecute {"code":"\nconst fs = await import('fs');\n"}
> build · deepseek-v4-pro
[0m✱ [0mGrep "^diff --git" [90min .pr-review-diff.patch · 3 matches[0m
[0m✱ [0mGrep "." [90min .pr-review-diff.patch · 67 matches[0m
> build · deepseek-v4-pro
The patch file appears truncated (ends mid-hunk at line 67). Let me verify the repo state to determine if there's more to the PR diff.
[0m→ [0mRead package.json
[0m→ [0mRead .release-please-manifest.json
[0m✱ [0mGlob "*.patch" [90m0 matches[0m
> build · deepseek-v4-pro
[0m✱ [0mGlob ".pr-review*" [90m1 match[0m
[0m✱ [0mGlob "*lock*" [90m1 match[0m
[0m→ [0mRead CHANGELOG.md [90m[limit=50][0m
> build · deepseek-v4-pro
[0m→ [0mRead pnpm-lock.yaml [90m[limit=40][0m
> build · deepseek-v4-pro
Reviewed the diff in `.pr-review-diff.patch` (verified complete against the repo; the `@@ -1,6 +1,6 @@` package.json hunk accounts for all lines, including the trailing `"scripts": {` context line). The PR contains only release metadata: a version bump in `.release-please-manifest.json` and `package.json` (both consistent at 1.1.0) and the generated `CHANGELOG.md` entry. The version bump does not require a `pnpm-lock.yaml` update (pnpm does not record the root package version), so nothing is stale.
The diff contains no reviewable code (release metadata/docs only).
VERDICT: APPROVE
build · deepseek-v4-pro
[0m→ [0mRead .pr-review-diff.patch
build · deepseek-v4-pro
This PR is a release-please version bump (1.0.0 → 1.1.0): it changes only .release-please-manifest.json, CHANGELOG.md, and package.json — no reviewable code, logic, or configuration beyond the version field.
VERDICT: APPROVE
[0m
> build · deepseek-v4-pro
[0m→ [0mRead .pr-review-diff.patch
> build · deepseek-v4-pro
This PR is a release-please version bump (1.0.0 → 1.1.0): it changes only `.release-please-manifest.json`, `CHANGELOG.md`, and `package.json` — no reviewable code, logic, or configuration beyond the version field.
VERDICT: APPROVE
build · deepseek-v4.1-flash
I'll start by reading the PR diff.
[0m→ [0mRead .pr-review-diff.patch
build · deepseek-v4.1-flash
[0m→ [0mRead .pr-review-diff.patch [90m[offset=61, limit=500][0m
build · deepseek-v4.1-flash
No reviewable code: the diff is a release-please version bump only (package.json, .release-please-manifest.json → 1.1.0) plus generated CHANGELOG.md entries; all three agree on 1.1.0.
VERDICT: APPROVE
[0m
> build · deepseek-v4.1-flash
I'll start by reading the PR diff.
[0m→ [0mRead .pr-review-diff.patch
> build · deepseek-v4.1-flash
[0m→ [0mRead .pr-review-diff.patch [90m[offset=61, limit=500][0m
> build · deepseek-v4.1-flash
No reviewable code: the diff is a release-please version bump only (`package.json`, `.release-please-manifest.json` → 1.1.0) plus generated `CHANGELOG.md` entries; all three agree on 1.1.0.
VERDICT: APPROVE
build · claude-haiku-5-5
[0m→ [0mRead .pr-review-diff.patch
build · claude-haiku-5-5
No reviewable code: the diff only bumps the version to 1.1.0 in .release-please-manifest.json and package.json, and adds a generated CHANGELOG entry.
VERDICT: APPROVE
[0m
> build · claude-haiku-5-5
[0m→ [0mRead .pr-review-diff.patch
> build · claude-haiku-5-5
No reviewable code: the diff only bumps the version to 1.1.0 in `.release-please-manifest.json` and `package.json`, and adds a generated CHANGELOG entry.
VERDICT: APPROVE
build · claude-haiku-5-5
[0m→ [0mRead .pr-review-diff.patch
build · claude-haiku-5-5
The diff contains no reviewable code. It only bumps the version to 1.1.0 in .release-please-manifest.json and package.json and adds the matching CHANGELOG.md entry.
VERDICT: APPROVE
[0m
> build · claude-haiku-5-5
[0m→ [0mRead .pr-review-diff.patch
> build · claude-haiku-5-5
The diff contains no reviewable code. It only bumps the version to 1.1.0 in `.release-please-manifest.json` and `package.json` and adds the matching `CHANGELOG.md` entry.
VERDICT: APPROVE
build · claude-haiku-5-5
[0m→ [0mRead .pr-review-diff.patch
build · claude-haiku-5-5
The diff contains no reviewable code: it only bumps the version to 1.1.0 in .release-please-manifest.json and package.json and adds a generated CHANGELOG.md entry.
VERDICT: APPROVE
[0m
> build · claude-haiku-5-5
[0m→ [0mRead .pr-review-diff.patch
> build · claude-haiku-5-5
The diff contains no reviewable code: it only bumps the version to 1.1.0 in `.release-please-manifest.json` and `package.json` and adds a generated `CHANGELOG.md` entry.
VERDICT: APPROVE
build · claude-haiku-5-5
[0m→ [0mRead .pr-review-diff.patch
build · claude-haiku-5-5
The diff contains no reviewable code: it only bumps the version in .release-please-manifest.json and package.json and adds the generated CHANGELOG.md entry.
VERDICT: APPROVE
[0m
> build · claude-haiku-5-5
[0m→ [0mRead .pr-review-diff.patch
> build · claude-haiku-5-5
The diff contains no reviewable code: it only bumps the version in `.release-please-manifest.json` and `package.json` and adds the generated `CHANGELOG.md` entry.
VERDICT: APPROVE
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
🤖 I have created a release beep boop
1.1.0
1.1.0 (2026-10-18)
Features
Bug Fixes
This PR was generated with Release Please. See documentation.
9e3e9925c4to6978447e3e[0m
The diff contains no reviewable code (release metadata/docs only).
VERDICT: APPROVE
6978447e3eto36bddd6f4b[0m
VERDICT: APPROVE
36bddd6f4btoaabb56e983[0m
VERDICT: APPROVE
aabb56e983tof7a092584f[0m
VERDICT: APPROVE
f7a092584ftodd7e6c281f[0m
VERDICT: APPROVE
dd7e6c281ftod7387a01cf[0m
VERDICT: APPROVE
d7387a01cfto395d0ad0f7[0m
VERDICT: APPROVE
395d0ad0f7toced3d8dab4