From 1.3.0 Hash Tool is in maintenance mode. What it accepts is written down once, in CONTRIBUTING.md ("Project
status"): security fixes (high/critical vulnerabilities in .NET or a dependency get a prompt release), dependency and
.NET updates, bug and UI/UX fixes, accessibility, translation fixes, and hash algorithms on real demand; no new
features unless truly necessary.
- README: maintenance, Qodana and .NET 10 LTS badges and a "Project status" section.
- CONTRIBUTING: the policy, the issue forms, and the hash algorithm candidates (BLAKE2b-512, SHA3-256/512, CRC-32C)
with what each would take; ARCHITECTURE: a checklist for adding an algorithm.
- Issue forms: the feature request form is replaced by "Hash algorithm request" and "Translation problem"; feature
ideas go to Discussions (Ideas). The accessibility form gives the email address for people who cannot use GitHub.
- Pull request template: the kinds of change that are accepted.
- SECURITY: 1.3.x supported, the security commitment during maintenance, Qodana among the checks.
- CLAUDE.md: the project status for agents.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1.2 KiB
1.2 KiB
What and why
Type of change
- Bug fix, including UI/UX problems
- Accessibility fix
- Translation fix
- Hash algorithm added or removed (link the request)
- Security fix or dependency/.NET update
- Documentation, tests or CI
How it was tested
Checklist
dotnet build HashTool.slnx -warnaserroranddotnet test --solution HashTool.slnxpassdotnet format HashTool.slnx --verify-no-changespasses- New or changed UI text is added to every language (
python -I eng/loc.py checkpasses) - UI changes work with the keyboard alone, have translated names for screen readers and don't rely on colour alone (ACCESSIBILITY.md)
- User-visible changes are listed under
[Unreleased]in CHANGELOG.md