Skip to content

negirau changelog

io.github.sincekmori/negirau

3 changes recorded. MCP Harbor re-reads this listing from the official registry every six hours and asks the live server what it exposes, and keeps what changed between one look and the next.

  • AGENTS.md +1 −1

    https://raw.githubusercontent.com/sincekmori/negirau/HEAD/AGENTS.md

    − - Dependency updates are Dependabot's (`.github/dependabot.yml`): one grouped PR per ecosystem per week (the bun root, the two pnpm packages, uv, GitHub Actions) behind a 7-day cooldown that mirrors the `minimumReleaseAge` in `bunfig.toml` and both `pnpm-workspace.yaml` files — change one, change all three.+ - Dependency updates are Dependabot's (`.github/dependabot.yml`): one grouped PR per ecosystem per week (the bun root, the two pnpm packages, uv, GitHub Actions) behind a 1-day cooldown that mirrors the `minimumReleaseAge` in `bunfig.toml` — change one, change both.

  • server.json 1 field changed
    version
    0.3.2 0.3.3

  • AGENTS.md +7 −2

    https://raw.githubusercontent.com/sincekmori/negirau/HEAD/AGENTS.md

    − - vitest runs in the workers pool (`@cloudflare/vitest-pool-workers`, vitest 4 plugin API `cloudflareTest()`); the old `fetchMock` from `cloudflare:test` is gone — stub `fetch` with `vi.stubGlobal`.−   Any conventional commit merged to main advances the version (docs/chore → patch, feat → minor, breaking → minor while pre-1.0 via `bump-minor-pre-major`); 1.0.0 is only ever taken deliberately, with a `Release-As: 1.0.0` commit.+ - vitest runs in the workers pool (`@cloudflare/vitest-plugin`, the renamed successor of `@cloudflare/vitest-pool-workers`, plugin API `cloudflareTest()`); the old `fetchMock` from `cloudflare:test` is gone — stub `fetch` with `vi.stubGlobal`.+   Only a commit whose type renders in the changelog releases: fix/perf/revert → patch, feat → minor, breaking → minor while pre-1.0 via `bump-minor-pre-major`; hidden types (docs, chore, build, ci, refactor, test, style) and messages that are not conventional leave the version alone, so a dependency bump ships with the next feat/fix rather than on its own.+   1.0.0 is only ever taken deliberately, with a `Release-As: 1.0.0` commit.+ - Dependency updates are Dependabot's (`.github/dependabot.yml`): one grouped PR per ecosystem per week (the bun root, the two pnpm packages, uv, GitHub Actions) behind a 7-day cooldown that mirrors the `minimumReleaseAge` in `bunfig.toml` and both `pnpm-workspace.yaml` files — change one, change all three.+   The PRs land as `build(deps)` / `ci` commits, which release-please hides, so a bump never releases on its own.+   oxfmt and zod stay outside the group on purpose: oxfmt formats the generated SKILL.md and zod emits the spec's JSON Schema, so either bump can move the committed `skills/negirau/` snapshot, which Dependabot cannot regenerate — run `bun run generate:skill` on those PRs and commit the result (Dependabot stops rebasing a PR once someone else pushes to it, which is fine).+   client-py is a published library, so its entry pins `versioning-strategy: lockfile-only` (GitHub rejects `widen` for uv) and pyproject's lower bounds stay where they are.