The last release before JSONPrism moves to maintenance mode.
- Dependencies at their latest releases, superseding Dependabot
#183-#191. i18next 27.1.3, react-i18next 18.0.2 and jsdom 31.0.1 are
majors; cargo update within semver (wry 0.57.2, tauri-plugin-opener
2.7.3); sonarqube-scan-action 8.5.0 and setup-java 6.3.0.
THIRD-PARTY.md is re-synced with both lockfiles.
- Qodana: a new workflow runs Qodana for JS (native mode) and Qodana for
Rust (EAP, Docker, as root with a bootstrap for the C toolchain and
GTK/WebKit headers). Both report to Qodana Cloud.
- Qodana findings, all fixed or documented:
- React types are imported instead of read from the UMD global.
- XMLBuilder comes from fast-xml-builder; XMLValidator stays, with a
documented suppression.
- act() calls in tests are synchronous.
- The Range geometry test stub is shared.
- Small regex and boolean cleanups.
- Two false positives are excluded with their reasons: a secret
reference, and serde_json, which tauri::generate_context!() needs.
- Maintenance mode:
- status badge and section in both READMEs;
- the policy in CONTRIBUTING;
- converter and translation issue templates;
- a Scope checklist in the PR template;
- ROADMAP Phase 11;
- maintenance-triage.yml closes out-of-scope feature requests with a
bilingual comment;
- a Dependabot group for the two fast-xml packages.
- Release 2.2.1: versionCode 20201, CHANGELOG.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
3.0 KiB
3.0 KiB
Maintainers
| Name | GitHub | Contact | Scope |
|---|---|---|---|
| Kokone | @poli0981 | code@poli0981.dev | Solo maintainer — code review, releases, translations review, community |
JSONPrism is co-authored with AI tooling — see DISCLAIMER.md for details. The maintainer is the single point of human review for every merged PR.
Since 2.2.1 the project is in maintenance mode: no new features, only the changes listed in CONTRIBUTING.md → Maintenance mode.
Responsibilities
- Code review — reviews and merges every PR, including AI-assisted changes and the weekly grouped Dependabot updates, and doesn't merge on red CI.
- Releases — tags
v*releases;release.ymlbuilds the Windows, macOS, Linux and Android packages into a draft GitHub Release withSHA256SUMS.txtand build-provenance attestations, which the maintainer reviews and publishes. The website deploys itself frommainthrough Cloudflare Workers Builds. - Translations review — the AI-generated Japanese and Simplified Chinese strings and the partly AI-generated Vietnamese ones.
- Accessibility — triages reports labelled
accessibility, runs the manual checks before a release and keeps ACCESSIBILITY.md current. - Community — issues, Discussions and the Discord server, and enforcement of the Code of Conduct. Vulnerability reports are triaged as described in SECURITY.md.
- Triage — keeps issues and pull requests within the maintenance
scope, closing the rest with the
out-of-scopelabel (the triage workflow posts the explanation).
Contact
- Bug reports, translation fixes and converter requests: GitHub Issues
- Feature ideas (no commitment while in maintenance mode): Discussions → Ideas
- Accessibility barriers: the Accessibility issue template, or code@poli0981.dev — see ACCESSIBILITY.md
- Discussion / Q&A: GitHub Discussions
- Community chat: Discord
- Project, maintainer & Code of Conduct: code@poli0981.dev
- Security: Private Security Advisory or security@poli0981.dev — never a public issue
Becoming a maintainer
JSONPrism is small-by-design. Additional maintainers may be added when a contributor has demonstrated:
- Multiple high-quality merged PRs.
- Familiarity with the conventions in CLAUDE.md and CONTRIBUTING.md.
- Willingness to review others' PRs and respond to issues.
Until then, the project runs as a single-maintainer indie project.