Skip to content

tutanota@345.260424.1: Fix hash#17704

Closed
z-Fng wants to merge 1 commit intomasterfrom
tutanota-hash-fix-139205256
Closed

tutanota@345.260424.1: Fix hash#17704
z-Fng wants to merge 1 commit intomasterfrom
tutanota-hash-fix-139205256

Conversation

@z-Fng
Copy link
Copy Markdown
Member

@z-Fng z-Fng commented Apr 29, 2026

Closes #17703

  • Use conventional PR title: <manifest-name[@version]|chore>: <general summary of the pull request>
  • I have read the Contributing Guide

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Apr 29, 2026

📝 Walkthrough

Walkthrough

This change updates a single SHA-256 hash value in the bucket/tutanota.json manifest file. The Windows 64-bit installer integrity check hash for tutanota version 345.260424.1 is updated from bba9d381e6d66889cb4b62fbf5b7f4c8b78e99b56a6d78375e29380b07efb9ec to d639beaead7196fadf0bee4ec25540496d9b8b0216adcde1fed2a2636568daa7. The installer URL and all other manifest fields remain unchanged.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

  • telegram@6.7.1: Fix hash #17522: Updates the architecture["64bit"].hash field in a bucket manifest JSON file following the same SHA-256 hash correction pattern.
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately describes the main change: updating the hash value for tutanota version 345.260424.1.
Description check ✅ Passed The description includes the required linked issue reference (#17703) and confirms completion of the repository's PR checklist items.
Linked Issues check ✅ Passed The PR successfully addresses issue #17703 by correcting the SHA-256 hash in the tutanota manifest to match the actual downloaded file.
Out of Scope Changes check ✅ Passed All changes are scoped to fixing the hash mismatch in the tutanota manifest; no unrelated modifications are present.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
Review rate limit: 6/8 reviews remaining, refill in 9 minutes and 41 seconds.

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions
Copy link
Copy Markdown
Contributor

Your changes did not pass all checks.

Please address the issues in the manifest and comment starting with /verify to rerun the checks.

tutanota

  • Lint
  • Description
  • License
  • Hashes
  • Checkver
  • Autoupdate
  • Autoupdate Hash Extraction

Check the full log for details.

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (3)
bucket/tutanota.json (3)

1-35: Looks good—hash update is isolated to the intended field.

The change updates only architecture.64bit.hash for version 345.260424.1, leaving the installer URL, extraction, and autoupdate config untouched—this matches the PR objective (fix hash mismatch so the update succeeds).

Please still run a local integrity check for this manifest before merge (or rely on CI if already enforced): use checkhashes.ps1 against bucket/ (or install the manifest for the 64-bit arch) to confirm the new SHA-256 matches the downloaded installer artifact.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@bucket/tutanota.json` around lines 1 - 35, The manifest change only updates
architecture.64bit.hash for version 345.260424.1; before merging, run a local
integrity check to confirm the new SHA-256 by running the repository's
checkhashes.ps1 against the bucket/ directory or by installing the manifest for
the 64-bit arch and verifying the downloaded installer matches
architecture.64bit.hash (also confirm checkver and autoupdate URLs remain
valid).

5-5: Optional: consider updating deprecated SPDX license identifier form.

license is currently set to GPL-3.0 (Line 5). Per project guidance/learned best practices for Scoop manifests, prefer the non-deprecated SPDX suffixed forms (e.g. GPL-3.0-only or GPL-3.0-or-later) if you’re updating/maintaining this field.

If you want to change it, confirm which exact GPL variant Tuta applies and ensure the bucket’s manifest tests accept the chosen SPDX string.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@bucket/tutanota.json` at line 5, The manifest's SPDX license identifier
currently uses the deprecated bare form "GPL-3.0"; update the "license" field in
the manifest to the correct suffixed SPDX form (e.g., "GPL-3.0-only" or
"GPL-3.0-or-later") that matches Tutanota's licensing; confirm which variant
applies and run the bucket/manifest tests to ensure the chosen SPDX string is
accepted and adjust if tests require the alternate suffix.

1-1: Scoop manifest should be CRLF.

Scoop bucket manifests are expected to use CRLF line endings. Please ensure bucket/tutanota.json is checked in with CRLF (not LF), to avoid CI/lint issues on some environments.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@bucket/tutanota.json` at line 1, The manifest file tutanota.json currently
uses LF line endings but Scoop requires CRLF; convert the file to CRLF, stage
the normalized file, and commit the change. You can convert using your editor's
EOL setting or a tool (e.g., unix2dos/dos2unix in reverse) then ensure git will
persist CRLF by setting core.autocrlf or updating .gitattributes, run git add
--renormalize tutanota.json (or re-add the file after conversion), and commit so
the repository stores the file with CRLF endings.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@bucket/tutanota.json`:
- Around line 1-35: The manifest change only updates architecture.64bit.hash for
version 345.260424.1; before merging, run a local integrity check to confirm the
new SHA-256 by running the repository's checkhashes.ps1 against the bucket/
directory or by installing the manifest for the 64-bit arch and verifying the
downloaded installer matches architecture.64bit.hash (also confirm checkver and
autoupdate URLs remain valid).
- Line 5: The manifest's SPDX license identifier currently uses the deprecated
bare form "GPL-3.0"; update the "license" field in the manifest to the correct
suffixed SPDX form (e.g., "GPL-3.0-only" or "GPL-3.0-or-later") that matches
Tutanota's licensing; confirm which variant applies and run the bucket/manifest
tests to ensure the chosen SPDX string is accepted and adjust if tests require
the alternate suffix.
- Line 1: The manifest file tutanota.json currently uses LF line endings but
Scoop requires CRLF; convert the file to CRLF, stage the normalized file, and
commit the change. You can convert using your editor's EOL setting or a tool
(e.g., unix2dos/dos2unix in reverse) then ensure git will persist CRLF by
setting core.autocrlf or updating .gitattributes, run git add --renormalize
tutanota.json (or re-add the file after conversion), and commit so the
repository stores the file with CRLF endings.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: bf16f0fc-5c2c-4d82-9826-aa80a23330a7

📥 Commits

Reviewing files that changed from the base of the PR and between c0afdd1 and 9faadfe.

📒 Files selected for processing (1)
  • bucket/tutanota.json

@z-Fng z-Fng closed this Apr 29, 2026
@z-Fng z-Fng deleted the tutanota-hash-fix-139205256 branch April 29, 2026 08:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

tutanota@345.260424.1: hash check failed

1 participant