jmrp.io / cs-routeros-bouncer

0

[READ-ONLY] Mirror of https://github.com/jmrplens/cs-routeros-bouncer. CrowdSec bouncer for MikroTik RouterOS — manages address lists and firewall rules via the RouterOS API jmrp.io/docs/cs-routeros-bouncer

bouncer crowdsec firewall go mikrotik network-security routeros

0

cs-routeros-bouncer / docs /

at main 4 folders 11 files

José M. Requena Plens chore(deps): update Go and pnpm dependencies (#85) 12d ago

feat(docs): read the Person entity from its canonical source (#75) Part of a rollout across the six sites that publish the `https://jmrp.io/#person` entity. jmrp.io now serves it as a standalone document; this site consumes it instead of restating it. ## Problem This site restated the entity by **copying its values**. Across the five project sites doing the same, that convention failed twice: - `cs-routeros-bouncer` published *"Open-source developer; author and maintainer of cs-routeros-bouncer"* as the `description` of the shared entity — a project description on a person node. - `Cloudflare-DNS-Updater` advertised an avatar URL that **returned 404** — a fingerprinted Astro asset the portfolio had long since rebuilt. Both are fixed upstream. Values that must not diverge should not be copied at all. ## Change The node is fetched at build time from the canonical document and spliced verbatim, so this document and jmrp.io describe the same entity with the same values **by construction**. ``` raw.githubusercontent.com/jmrplens/jmrp.io/main/public/identity/person.jsonld ``` Fetched from GitHub rather than `https://jmrp.io` **on purpose**: this build runs on a CI runner, and jmrp.io sits behind Cloudflare, CrowdSec and a MikroTik bouncer — the one place a blocked runner IP would silently degrade this site to a stale snapshot. GitHub serves the same bytes and is already a hard dependency of the build (the checkout comes from it). If GitHub is down there is no build anyway, which makes the committed snapshot a belt-and-braces fallback rather than a real dependency. ## What it gains Beyond removing the drift risk, this site now asserts things it never did: | | Before | After | | --- | --- | --- | | `alternateName` | `"jmrplens"` | **8 observed variants**, including `José M. Requena-Plens` — the citation form in every published paper | | `sameAs` | 6–10 | **14**, including two forge accounts with signed OpenPGP proofs | | `owns` | absent | **11 projects** | ## Deliberate choices - **`knowsAbout` stays local and is merged, not replaced.** It is multi-valued, so the project's own topics reinforce the canonical list instead of conflicting with it. The full local set is kept — not just the entries the canonical lacks — so this site keeps asserting its own topics even if that list changes. - **`creator` + `maintainer` added alongside `author`** on the software nodes, matching the three agents `jmrp.io/projects/` emits for those `@id`s. They merge, so a partial set per document was untidy rather than wrong. - **Visible footer link to the project index**, localized where the site is bilingual. Deliberately **not** `rel="me"`: it is a page, not an identity profile. - **`pnpm run identity:sync`** refreshes the snapshot deliberately, in its own commit, so the identity this site would ship without a network is visible in review rather than frozen at whatever it was the day the file was added. ## Verification Built and re-parsed out of the built HTML: ``` props identical to canonical : YES extra props : none alternateName 8 · owns 11 · sameAs 14 knowsAbout: canonical 19 + this project's own, no duplicates ``` The full JSON-LD node inventory was compared before and after — not just the `Person` — after an earlier attempt in this rollout silently deleted two sibling nodes while still producing a green build. https://claude.ai/code/session_01Ecf6hESxYdc7f1UV1vHrQU  <a href="https://cubic.dev/pr/jmrplens/cs-routeros-bouncer/pull/75?utm_source=github" target="_blank" rel="noopener noreferrer" data-no-image-dialog="true"><picture><source media="(prefers-color-scheme: dark)" srcset="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"><source media="(prefers-color-scheme: light)" srcset="https://www.cubic.dev/buttons/review-in-cubic-light.svg"><img alt="Review in cubic" src="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"></picture></a>

4 weeks ago

docs: remove references to deleted Wikidata items (#67) ## Summary The project (Q140393352) and personal (Q140455276) Wikidata items were deleted by a Wikidata admin on 2026-07-07 ("Mass deletion of pages added by Jmrplens", notability policy). Links to nonexistent entities are a negative entity-verification signal, so this removes them from: - `docs/astro.config.mjs` (Person and SoftwareApplication `sameAs`) - `docs/public/llms.txt` (knowledge-graph bullet) - `docs/src/content/docs/about.mdx` + `es/about.mdx` (visible listings) CrowdSec Hub, pkg.go.dev, and GHCR listings are unaffected. Part of a cross-repo cleanup; companion PR jmrplens/gitlab-mcp-server#221. https://claude.ai/code/session_016KQnnNLPVouuFYJqLd6kzv  <a href="https://cubic.dev/pr/jmrplens/cs-routeros-bouncer/pull/67?utm_source=github" target="_blank" rel="noopener noreferrer" data-no-image-dialog="true"><picture><source media="(prefers-color-scheme: dark)" srcset="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"><source media="(prefers-color-scheme: light)" srcset="https://www.cubic.dev/buttons/review-in-cubic-light.svg"><img alt="Review in cubic" src="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"></picture></a>

1 month ago

feat(docs): read the Person entity from its canonical source (#75) Part of a rollout across the six sites that publish the `https://jmrp.io/#person` entity. jmrp.io now serves it as a standalone document; this site consumes it instead of restating it. ## Problem This site restated the entity by **copying its values**. Across the five project sites doing the same, that convention failed twice: - `cs-routeros-bouncer` published *"Open-source developer; author and maintainer of cs-routeros-bouncer"* as the `description` of the shared entity — a project description on a person node. - `Cloudflare-DNS-Updater` advertised an avatar URL that **returned 404** — a fingerprinted Astro asset the portfolio had long since rebuilt. Both are fixed upstream. Values that must not diverge should not be copied at all. ## Change The node is fetched at build time from the canonical document and spliced verbatim, so this document and jmrp.io describe the same entity with the same values **by construction**. ``` raw.githubusercontent.com/jmrplens/jmrp.io/main/public/identity/person.jsonld ``` Fetched from GitHub rather than `https://jmrp.io` **on purpose**: this build runs on a CI runner, and jmrp.io sits behind Cloudflare, CrowdSec and a MikroTik bouncer — the one place a blocked runner IP would silently degrade this site to a stale snapshot. GitHub serves the same bytes and is already a hard dependency of the build (the checkout comes from it). If GitHub is down there is no build anyway, which makes the committed snapshot a belt-and-braces fallback rather than a real dependency. ## What it gains Beyond removing the drift risk, this site now asserts things it never did: | | Before | After | | --- | --- | --- | | `alternateName` | `"jmrplens"` | **8 observed variants**, including `José M. Requena-Plens` — the citation form in every published paper | | `sameAs` | 6–10 | **14**, including two forge accounts with signed OpenPGP proofs | | `owns` | absent | **11 projects** | ## Deliberate choices - **`knowsAbout` stays local and is merged, not replaced.** It is multi-valued, so the project's own topics reinforce the canonical list instead of conflicting with it. The full local set is kept — not just the entries the canonical lacks — so this site keeps asserting its own topics even if that list changes. - **`creator` + `maintainer` added alongside `author`** on the software nodes, matching the three agents `jmrp.io/projects/` emits for those `@id`s. They merge, so a partial set per document was untidy rather than wrong. - **Visible footer link to the project index**, localized where the site is bilingual. Deliberately **not** `rel="me"`: it is a page, not an identity profile. - **`pnpm run identity:sync`** refreshes the snapshot deliberately, in its own commit, so the identity this site would ship without a network is visible in review rather than frozen at whatever it was the day the file was added. ## Verification Built and re-parsed out of the built HTML: ``` props identical to canonical : YES extra props : none alternateName 8 · owns 11 · sameAs 14 knowsAbout: canonical 19 + this project's own, no duplicates ``` The full JSON-LD node inventory was compared before and after — not just the `Person` — after an earlier attempt in this rollout silently deleted two sibling nodes while still producing a green build. https://claude.ai/code/session_01Ecf6hESxYdc7f1UV1vHrQU  <a href="https://cubic.dev/pr/jmrplens/cs-routeros-bouncer/pull/75?utm_source=github" target="_blank" rel="noopener noreferrer" data-no-image-dialog="true"><picture><source media="(prefers-color-scheme: dark)" srcset="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"><source media="(prefers-color-scheme: light)" srcset="https://www.cubic.dev/buttons/review-in-cubic-light.svg"><img alt="Review in cubic" src="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"></picture></a>

4 weeks ago

refactor(tooling): install analysis tools as pinned binaries, not go.mod tools (#81) Adopts the arrangement used by the sibling gitlab-mcp-server repository — linters as standalone binaries rather than a go.mod `tool` directive — but pins every version instead of installing @latest, so local runs and CI agree and a bump is a reviewable diff rather than silent drift. A `tool` directive forces the linters and the application through a single MVS graph, so any two tools with incompatible requirements deadlock the whole build. Both conflicts are live today: - securego/gosec 2.28.0 and rhysd/actionlint 1.7.12 require mutually exclusive go.yaml.in/yaml/v4 revisions (rc.6 vs rc.3). - golangci-lint 2.12.2 pins denis-tingaikin/go-header at v0.5.0, and v1.0.0 breaks the API it calls. As standalone binaries each tool resolves its own dependencies and the class of problem disappears. gosec goes to 2.28.0 with no `replace`, superseding #80 (closed). Versions live in the Makefile as the single source of truth, tracked by version-stamped markers so bumping a variable forces a reinstall: make tools install all seven into bin/tools/ make tools-versions print the pins CI installs from the same pins via the make targets, with bin/tools cached on a hash of the Makefile. Side effect: go.mod drops from 305 to 81 lines and go.sum from 757 to 178, leaving only what the shipped binary actually links. .golangci.yml is kept as-is — it already shares the sibling's lineage and structure. The remaining deltas (complexity guards, gofumpt/gci, stricter gosec audit) are a separate judgement call. Also corrects the CHANGELOG claim merged in #78 that gosec had to be held at 2.27.1 because 2.28.0 "requires the rc.6 YAML API". gosec never imports go.yaml.in/yaml/v4 at all. Docs updated: CONTRIBUTING.md and the EN/ES building and contributing pages no longer tell contributors to `go install golangci-lint@latest`, which also pointed at a stale v1 module path. Verified from a deleted bin/tools: `make analyze` reinstalls all seven tools and passes end to end, plus go build and the test suite.

3 weeks ago

chore(deps): update Go and pnpm dependencies (#85) ## Description Routine dependency refresh: Go module closure and the docs site's pnpm workspace, plus a bump of the pinned pnpm release itself. ## Type of change - [ ] 🐛 Bug fix (non-breaking change that fixes an issue) - [ ] ✨ New feature (non-breaking change that adds functionality) - [ ] 💥 Breaking change (fix or feature that would cause existing functionality to change) - [ ] 📖 Documentation update - [x] 🔒 Security / dependency update - [ ] 🧪 Tests / tooling / CI - [ ] 🧹 Refactoring / code cleanup - [ ] ⚡ Performance improvement ## Changes - Go dependency closure: `go-openapi/{analysis,validate}`, `golang.org/x/{net,text}`, `google.golang.org/protobuf`, `lufia/plan9stats`, `power-devops/perfstat` - pnpm pinned release: 11.18.0 → 11.21.0 - docs npm dependencies: Astro 7.1.6 → 7.2.1, `@astrojs/starlight` 0.41.6 → 0.41.7, ESLint 10.8.0 → 10.8.1, `eslint-plugin-astro` 3.0.1 → 3.1.0, `globals` 17.8.0 → 17.11.0, `html-validate` 11.6.0 → 11.6.2, `typescript-eslint` 8.65.0 → 8.67.0 - `typescript` intentionally held at `^6.0.3` — 7.x breaks `astro check`'s programmatic API (see `.github/dependabot.yml` ignore rule and [withastro/roadmap#1321](https://github.com/withastro/roadmap/discussions/1321)) - Supersedes dependabot #84 (npm-minor-patch group in `/docs`) — all 6 of its bumps are matched or exceeded here ## Testing - [x] Unit tests pass (`go test ./...`) - [x] Static analysis passes (`go build ./...`, `pnpm run lint`) - [x] Documentation checks pass (`pnpm run check`, `pnpm run build`, `pnpm run html:validate`, `pnpm run format:check`) - [ ] Tested against a real MikroTik router (if applicable) - [ ] Docker image builds (`make docker-build`) ## RouterOS compatibility Not applicable — dependency-only change, no RouterOS interaction touched. ## Checklist - [x] My code follows the project style guidelines - [ ] I have added tests for my changes (if applicable) - [ ] I have updated the documentation (if applicable) - [x] I have updated CHANGELOG.md (if applicable) - [ ] I have updated release/configuration files when behavior changed - [x] My changes do not introduce new warnings ## Summary by Sourcery Refresh Go and docs-site dependencies and update the pinned pnpm release. Enhancements: - Update indirect Go module dependencies including go-openapi, golang.org/x/{net,text}, google.golang.org/protobuf, lufia/plan9stats, and power-devops/perfstat. - Bump the docs site npm dependencies for Astro, @astrojs/starlight, ESLint and related tooling while keeping TypeScript pinned at 6.x for astro check compatibility. Build: - Increase the pinned pnpm package manager version from 11.18.0 to 11.21.0 in the docs workspace. Documentation: - Extend CHANGELOG with a new dependencies entry documenting the Go, pnpm, and docs-site npm updates.  ## Summary by CodeRabbit * **Chores** * Updated supporting tools and platform components to newer versions. * Improved compatibility and maintenance across the documentation site and Go-based components. * Updated package-management configuration and lockfile integrity settings. * **Documentation** * Added a dated changelog entry summarizing the latest tooling and platform updates. * TypeScript remains on the 6.x release line.

1 week ago

.htmlvalidate.json

Prepare 1.4.0 tooling and review follow-ups (#24) Prepare the 1.4.0 branch with dependency/tooling updates, docs validation, release metadata, and follow-up review fixes. Summary: - Add and document periodic reconciliation behavior, release references, and refreshed docs/tooling validation. - Modernize Go and docs tooling, including static analysis, pnpm checks, GoReleaser, and workflow gating. - Address review feedback across RouterOS error handling, metrics, config expansion, functional scripts, docs, templates, and CI.

3 months ago

.prettierignore

Prepare 1.4.0 tooling and review follow-ups (#24) Prepare the 1.4.0 branch with dependency/tooling updates, docs validation, release metadata, and follow-up review fixes. Summary: - Add and document periodic reconciliation behavior, release references, and refreshed docs/tooling validation. - Modernize Go and docs tooling, including static analysis, pnpm checks, GoReleaser, and workflow gating. - Address review feedback across RouterOS error handling, metrics, config expansion, functional scripts, docs, templates, and CI.

3 months ago

.prettierrc.json

Prepare 1.4.0 tooling and review follow-ups (#24) Prepare the 1.4.0 branch with dependency/tooling updates, docs validation, release metadata, and follow-up review fixes. Summary: - Add and document periodic reconciliation behavior, release references, and refreshed docs/tooling validation. - Modernize Go and docs tooling, including static analysis, pnpm checks, GoReleaser, and workflow gating. - Address review feedback across RouterOS error handling, metrics, config expansion, functional scripts, docs, templates, and CI.

3 months ago

Prepare 1.4.0 tooling and review follow-ups (#24) Prepare the 1.4.0 branch with dependency/tooling updates, docs validation, release metadata, and follow-up review fixes. Summary: - Add and document periodic reconciliation behavior, release references, and refreshed docs/tooling validation. - Modernize Go and docs tooling, including static analysis, pnpm checks, GoReleaser, and workflow gating. - Address review feedback across RouterOS error handling, metrics, config expansion, functional scripts, docs, templates, and CI.

3 months ago

astro.config.mjs

feat(docs): read the Person entity from its canonical source (#75) Part of a rollout across the six sites that publish the `https://jmrp.io/#person` entity. jmrp.io now serves it as a standalone document; this site consumes it instead of restating it. ## Problem This site restated the entity by **copying its values**. Across the five project sites doing the same, that convention failed twice: - `cs-routeros-bouncer` published *"Open-source developer; author and maintainer of cs-routeros-bouncer"* as the `description` of the shared entity — a project description on a person node. - `Cloudflare-DNS-Updater` advertised an avatar URL that **returned 404** — a fingerprinted Astro asset the portfolio had long since rebuilt. Both are fixed upstream. Values that must not diverge should not be copied at all. ## Change The node is fetched at build time from the canonical document and spliced verbatim, so this document and jmrp.io describe the same entity with the same values **by construction**. ``` raw.githubusercontent.com/jmrplens/jmrp.io/main/public/identity/person.jsonld ``` Fetched from GitHub rather than `https://jmrp.io` **on purpose**: this build runs on a CI runner, and jmrp.io sits behind Cloudflare, CrowdSec and a MikroTik bouncer — the one place a blocked runner IP would silently degrade this site to a stale snapshot. GitHub serves the same bytes and is already a hard dependency of the build (the checkout comes from it). If GitHub is down there is no build anyway, which makes the committed snapshot a belt-and-braces fallback rather than a real dependency. ## What it gains Beyond removing the drift risk, this site now asserts things it never did: | | Before | After | | --- | --- | --- | | `alternateName` | `"jmrplens"` | **8 observed variants**, including `José M. Requena-Plens` — the citation form in every published paper | | `sameAs` | 6–10 | **14**, including two forge accounts with signed OpenPGP proofs | | `owns` | absent | **11 projects** | ## Deliberate choices - **`knowsAbout` stays local and is merged, not replaced.** It is multi-valued, so the project's own topics reinforce the canonical list instead of conflicting with it. The full local set is kept — not just the entries the canonical lacks — so this site keeps asserting its own topics even if that list changes. - **`creator` + `maintainer` added alongside `author`** on the software nodes, matching the three agents `jmrp.io/projects/` emits for those `@id`s. They merge, so a partial set per document was untidy rather than wrong. - **Visible footer link to the project index**, localized where the site is bilingual. Deliberately **not** `rel="me"`: it is a page, not an identity profile. - **`pnpm run identity:sync`** refreshes the snapshot deliberately, in its own commit, so the identity this site would ship without a network is visible in review rather than frozen at whatever it was the day the file was added. ## Verification Built and re-parsed out of the built HTML: ``` props identical to canonical : YES extra props : none alternateName 8 · owns 11 · sameAs 14 knowsAbout: canonical 19 + this project's own, no duplicates ``` The full JSON-LD node inventory was compared before and after — not just the `Person` — after an earlier attempt in this rollout silently deleted two sibling nodes while still producing a green build. https://claude.ai/code/session_01Ecf6hESxYdc7f1UV1vHrQU  <a href="https://cubic.dev/pr/jmrplens/cs-routeros-bouncer/pull/75?utm_source=github" target="_blank" rel="noopener noreferrer" data-no-image-dialog="true"><picture><source media="(prefers-color-scheme: dark)" srcset="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"><source media="(prefers-color-scheme: light)" srcset="https://www.cubic.dev/buttons/review-in-cubic-light.svg"><img alt="Review in cubic" src="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"></picture></a>

4 weeks ago

eslint.config.js

Prepare 1.4.0 tooling and review follow-ups (#24) Prepare the 1.4.0 branch with dependency/tooling updates, docs validation, release metadata, and follow-up review fixes. Summary: - Add and document periodic reconciliation behavior, release references, and refreshed docs/tooling validation. - Modernize Go and docs tooling, including static analysis, pnpm checks, GoReleaser, and workflow gating. - Address review feedback across RouterOS error handling, metrics, config expansion, functional scripts, docs, templates, and CI.

3 months ago

chore(deps): update Go and pnpm dependencies (#85) ## Description Routine dependency refresh: Go module closure and the docs site's pnpm workspace, plus a bump of the pinned pnpm release itself. ## Type of change - [ ] 🐛 Bug fix (non-breaking change that fixes an issue) - [ ] ✨ New feature (non-breaking change that adds functionality) - [ ] 💥 Breaking change (fix or feature that would cause existing functionality to change) - [ ] 📖 Documentation update - [x] 🔒 Security / dependency update - [ ] 🧪 Tests / tooling / CI - [ ] 🧹 Refactoring / code cleanup - [ ] ⚡ Performance improvement ## Changes - Go dependency closure: `go-openapi/{analysis,validate}`, `golang.org/x/{net,text}`, `google.golang.org/protobuf`, `lufia/plan9stats`, `power-devops/perfstat` - pnpm pinned release: 11.18.0 → 11.21.0 - docs npm dependencies: Astro 7.1.6 → 7.2.1, `@astrojs/starlight` 0.41.6 → 0.41.7, ESLint 10.8.0 → 10.8.1, `eslint-plugin-astro` 3.0.1 → 3.1.0, `globals` 17.8.0 → 17.11.0, `html-validate` 11.6.0 → 11.6.2, `typescript-eslint` 8.65.0 → 8.67.0 - `typescript` intentionally held at `^6.0.3` — 7.x breaks `astro check`'s programmatic API (see `.github/dependabot.yml` ignore rule and [withastro/roadmap#1321](https://github.com/withastro/roadmap/discussions/1321)) - Supersedes dependabot #84 (npm-minor-patch group in `/docs`) — all 6 of its bumps are matched or exceeded here ## Testing - [x] Unit tests pass (`go test ./...`) - [x] Static analysis passes (`go build ./...`, `pnpm run lint`) - [x] Documentation checks pass (`pnpm run check`, `pnpm run build`, `pnpm run html:validate`, `pnpm run format:check`) - [ ] Tested against a real MikroTik router (if applicable) - [ ] Docker image builds (`make docker-build`) ## RouterOS compatibility Not applicable — dependency-only change, no RouterOS interaction touched. ## Checklist - [x] My code follows the project style guidelines - [ ] I have added tests for my changes (if applicable) - [ ] I have updated the documentation (if applicable) - [x] I have updated CHANGELOG.md (if applicable) - [ ] I have updated release/configuration files when behavior changed - [x] My changes do not introduce new warnings ## Summary by Sourcery Refresh Go and docs-site dependencies and update the pinned pnpm release. Enhancements: - Update indirect Go module dependencies including go-openapi, golang.org/x/{net,text}, google.golang.org/protobuf, lufia/plan9stats, and power-devops/perfstat. - Bump the docs site npm dependencies for Astro, @astrojs/starlight, ESLint and related tooling while keeping TypeScript pinned at 6.x for astro check compatibility. Build: - Increase the pinned pnpm package manager version from 11.18.0 to 11.21.0 in the docs workspace. Documentation: - Extend CHANGELOG with a new dependencies entry documenting the Go, pnpm, and docs-site npm updates.  ## Summary by CodeRabbit * **Chores** * Updated supporting tools and platform components to newer versions. * Improved compatibility and maintenance across the documentation site and Go-based components. * Updated package-management configuration and lockfile integrity settings. * **Documentation** * Added a dated changelog entry summarizing the latest tooling and platform updates. * TypeScript remains on the 6.x release line.

1 week ago

chore(deps): update Go and pnpm dependencies (#85) ## Description Routine dependency refresh: Go module closure and the docs site's pnpm workspace, plus a bump of the pinned pnpm release itself. ## Type of change - [ ] 🐛 Bug fix (non-breaking change that fixes an issue) - [ ] ✨ New feature (non-breaking change that adds functionality) - [ ] 💥 Breaking change (fix or feature that would cause existing functionality to change) - [ ] 📖 Documentation update - [x] 🔒 Security / dependency update - [ ] 🧪 Tests / tooling / CI - [ ] 🧹 Refactoring / code cleanup - [ ] ⚡ Performance improvement ## Changes - Go dependency closure: `go-openapi/{analysis,validate}`, `golang.org/x/{net,text}`, `google.golang.org/protobuf`, `lufia/plan9stats`, `power-devops/perfstat` - pnpm pinned release: 11.18.0 → 11.21.0 - docs npm dependencies: Astro 7.1.6 → 7.2.1, `@astrojs/starlight` 0.41.6 → 0.41.7, ESLint 10.8.0 → 10.8.1, `eslint-plugin-astro` 3.0.1 → 3.1.0, `globals` 17.8.0 → 17.11.0, `html-validate` 11.6.0 → 11.6.2, `typescript-eslint` 8.65.0 → 8.67.0 - `typescript` intentionally held at `^6.0.3` — 7.x breaks `astro check`'s programmatic API (see `.github/dependabot.yml` ignore rule and [withastro/roadmap#1321](https://github.com/withastro/roadmap/discussions/1321)) - Supersedes dependabot #84 (npm-minor-patch group in `/docs`) — all 6 of its bumps are matched or exceeded here ## Testing - [x] Unit tests pass (`go test ./...`) - [x] Static analysis passes (`go build ./...`, `pnpm run lint`) - [x] Documentation checks pass (`pnpm run check`, `pnpm run build`, `pnpm run html:validate`, `pnpm run format:check`) - [ ] Tested against a real MikroTik router (if applicable) - [ ] Docker image builds (`make docker-build`) ## RouterOS compatibility Not applicable — dependency-only change, no RouterOS interaction touched. ## Checklist - [x] My code follows the project style guidelines - [ ] I have added tests for my changes (if applicable) - [ ] I have updated the documentation (if applicable) - [x] I have updated CHANGELOG.md (if applicable) - [ ] I have updated release/configuration files when behavior changed - [x] My changes do not introduce new warnings ## Summary by Sourcery Refresh Go and docs-site dependencies and update the pinned pnpm release. Enhancements: - Update indirect Go module dependencies including go-openapi, golang.org/x/{net,text}, google.golang.org/protobuf, lufia/plan9stats, and power-devops/perfstat. - Bump the docs site npm dependencies for Astro, @astrojs/starlight, ESLint and related tooling while keeping TypeScript pinned at 6.x for astro check compatibility. Build: - Increase the pinned pnpm package manager version from 11.18.0 to 11.21.0 in the docs workspace. Documentation: - Extend CHANGELOG with a new dependencies entry documenting the Go, pnpm, and docs-site npm updates.  ## Summary by CodeRabbit * **Chores** * Updated supporting tools and platform components to newer versions. * Improved compatibility and maintenance across the documentation site and Go-based components. * Updated package-management configuration and lockfile integrity settings. * **Documentation** * Added a dated changelog entry summarizing the latest tooling and platform updates. * TypeScript remains on the 6.x release line.

1 week ago

pnpm-workspace.yaml

chore(deps): update GitHub Actions, Go and pnpm/Astro dependencies (#57) ## Description Consolidated dependency refresh across the three ecosystems: GitHub Actions, Go modules and the docs pnpm/Astro workspace. ## Type of change - [ ] 🐛 Bug fix (non-breaking change that fixes an issue) - [ ] ✨ New feature (non-breaking change that adds functionality) - [ ] 💥 Breaking change (fix or feature that would cause existing functionality to change) - [ ] 📖 Documentation update - [x] 🔒 Security / dependency update - [ ] 🧪 Tests / tooling / CI - [ ] 🧹 Refactoring / code cleanup - [ ] ⚡ Performance improvement ## Changes - **GitHub Actions**: bump `actions/checkout` v6 → v7 across `ci.yml`, `docs.yml`, `release.yml` (all other pinned actions were already at their latest release). - **Go**: `go get -u ./...` + `go mod tidy` — refreshes indirect deps (mostly transitive to `crowdsecurity/crowdsec`) and tool deps (`gosec`, `x/tools`, `x/vuln`) to latest minor/patch. No direct dependency needed a major bump. - **docs (pnpm/Astro)**: `astro` 6.4.8 → 7.0.4, `@astrojs/starlight` 0.40.0 → 0.41.1, `eslint-plugin-astro` 1.7.0 → 2.1.1 (majors), plus minor/patch bumps for `eslint`, `globals`, `playwright`, `prettier`, `typescript-eslint`. Also cleaned up a stray unfilled `allowBuilds` placeholder that pnpm 11 had appended to `docs/pnpm-workspace.yaml`. Supersedes dependabot PRs #52 (actions/checkout) and #54 (astro major); those can be closed once this merges. ## Testing - [x] Unit tests pass (`make test-short` or `make test`) - [x] Static analysis passes (`make analyze` or equivalent CI jobs) — `make lint`, `make gosec`, `make govulncheck` all clean. Note: `make actionlint` fails on `.github/workflows/auto-assign.yml` (pre-existing shellcheck warning from #56, unrelated to this branch). - [x] Documentation checks pass (`make docs-analyze` if docs changed) — `check`, `lint`, `format:check`, `build`, `html-validate` all pass on Astro 7. - [ ] Tested against a real MikroTik router (if applicable) - [ ] Docker image builds (`make docker-build`) ## Checklist - [x] My code follows the project style guidelines - [ ] I have added tests for my changes (if applicable) - [ ] I have updated the documentation (if applicable) - [ ] I have updated CHANGELOG.md (if applicable) - [ ] I have updated release/configuration files when behavior changed - [x] My changes do not introduce new warnings ## Summary by Sourcery Update dependencies across Go modules, GitHub Actions workflows, and the docs pnpm/Astro workspace. Build: - Bump actions/checkout from v6 to v7 in CI, docs, and release GitHub Actions workflows. Documentation: - Upgrade Astro docs dependencies, including Astro, @astrojs/starlight, eslint-plugin-astro, and related tooling, and adjust pnpm workspace config for built dependencies. Chores: - Refresh indirect Go module dependencies (including go-openapi, TOML, Prometheus, gopsutil, and others) to newer minor/patch versions.  ## Summary by CodeRabbit * **Chores** * Updated CI and release workflows to use the latest repository checkout action, helping keep build and test automation current. * Refreshed several project dependencies and tooling versions, including docs and linting packages, to improve maintenance and compatibility. * Enabled builds for additional workspace components used by the docs site, supporting smoother documentation builds and deployment.

1 month ago

Prepare 1.4.0 tooling and review follow-ups (#24) Prepare the 1.4.0 branch with dependency/tooling updates, docs validation, release metadata, and follow-up review fixes. Summary: - Add and document periodic reconciliation behavior, release references, and refreshed docs/tooling validation. - Modernize Go and docs tooling, including static analysis, pnpm checks, GoReleaser, and workflow gating. - Address review feedback across RouterOS error handling, metrics, config expansion, functional scripts, docs, templates, and CI.

3 months ago

README.md

cs-routeros-bouncer — Documentation#

Documentation site for cs-routeros-bouncer, the CrowdSec bouncer for MikroTik RouterOS. Live at: https://jmrplens.github.io/cs-routeros-bouncer

Project Structure#

docs/
├── public/              # Static assets (og-image, favicon)
├── src/
│   ├── assets/          # Logo, images
│   ├── components/
│   │   └── overrides/   # Starlight component overrides (Header, Footer)
│   ├── content/docs/    # MDX documentation pages
│   └── styles/          # Custom CSS theme system
├── astro.config.mjs     # Starlight + Astro configuration
└── package.json

Key customizations#

Theme system — Full design system in src/styles/custom.css (color palette, typography, dark/high-contrast modes, responsive tables, print styles)
Mermaid diagrams — Server-side rendering via rehype-mermaid (requires Playwright)
Component overrides — Custom Header (announcement bar) and Footer
SEO — Open Graph/Twitter meta tags, JSON-LD structured data, sitemap
Accessibility — WCAG focus indicators, reduced-motion support, proper ARIA landmarks

Commands#

Command	Action
`pnpm install`	Install dependencies
`pnpm dev`	Start dev server at `localhost:4321`
`pnpm analyze`	Run all docs checks
`pnpm lint`	Run ESLint
`pnpm format`	Format docs sources
`pnpm build`	Build production site to `./dist/`
`pnpm preview`	Preview build locally before deploying

Note: First install requires pnpm approve-builds to approve esbuild/sharp post-install scripts, and Playwright's Chromium browser (npx playwright install chromium).