fix: grant pull-requests:write permission to reusable CI workflow changelog.yml (currently broken)

[zerosnacks]

Fixes the invalid workflow error in https://github.com/tempoxyz/mpp-rs/actions/workflows/changelog.yml

The nested job 'lint' is requesting 'pull-requests: write', but is only allowed 'pull-requests: none'.

The changelog.yml workflow calls ci.yml via workflow_call, but the lint job in ci.yml requests pull-requests: write (needed by tempoxyz/lints to post comments). Without explicit permissions on the caller's job, the reusable workflow inherits none for undeclared permissions.

Security: Safe — the trigger is pull_request (not pull_request_target), so fork PRs get a read-only GITHUB_TOKEN regardless. Same-repo PRs come from trusted collaborators.

[github-actions]

Tempo Lint Results

Summary

Found 687 issue(s) across 41 file(s)

Severity	Count
Errors	0
Warnings	687
Hints	0

---

Issues by Rule Type

no-unwrap-in-lib (673 occurrences)

• /home/runner/work/mpp-rs/mpp-rs/src/body_digest.rs:1 - Avoid .unwrap() in library code. Use proper error handling with ? or .expect() with context.
• /home/runner/work/mpp-rs/mpp-rs/src/client/fetch.rs:1 - Avoid .unwrap() in library code. Use proper error handling with ? or .expect() with context.
• /home/runner/work/mpp-rs/mpp-rs/src/client/fetch.rs:1 - Avoid .unwrap() in library code. Use proper error handling with ? or .expect() with context.
• /home/runner/work/mpp-rs/mpp-rs/src/client/fetch.rs:1 - Avoid .unwrap() in library code. Use proper error handling with ? or .expect() with context.
• /home/runner/work/mpp-rs/mpp-rs/src/client/fetch.rs:1 - Avoid .unwrap() in library code. Use proper error handling with ? or .expect() with context.
• /home/runner/work/mpp-rs/mpp-rs/src/client/fetch.rs:1 - Avoid .unwrap() in library code. Use proper error handling with ? or .expect() with context.
• /home/runner/work/mpp-rs/mpp-rs/src/client/fetch.rs:1 - Avoid .unwrap() in library code. Use proper error handling with ? or .expect() with context.
• /home/runner/work/mpp-rs/mpp-rs/src/client/fetch.rs:1 - Avoid .unwrap() in library code. Use proper error handling with ? or .expect() with context.
• /home/runner/work/mpp-rs/mpp-rs/src/mcp.rs:1 - Avoid .unwrap() in library code. Use proper error handling with ? or .expect() with context.
• /home/runner/work/mpp-rs/mpp-rs/src/mcp.rs:1 - Avoid .unwrap() in library code. Use proper error handling with ? or .expect() with context.

... and 663 more

no-leading-whitespace-strings (10 occurrences)

• /home/runner/work/mpp-rs/mpp-rs/src/error.rs:1 - String literals should not start with leading whitespace. Found: ' for '
• /home/runner/work/mpp-rs/mpp-rs/src/error.rs:1 - String literals should not start with leading whitespace. Found: ' ({})'
• /home/runner/work/mpp-rs/mpp-rs/src/error.rs:1 - String literals should not start with leading whitespace. Found: ' is invalid.'
• /home/runner/work/mpp-rs/mpp-rs/src/error.rs:1 - String literals should not start with leading whitespace. Found: ' is invalid: already used.'
• /home/runner/work/mpp-rs/mpp-rs/src/error.rs:1 - String literals should not start with leading whitespace. Found: ' (Premium access).'
• /home/runner/work/mpp-rs/mpp-rs/src/protocol/core/types.rs:1 - String literals should not start with leading whitespace. Found: ' and backslashes '
• /home/runner/work/mpp-rs/mpp-rs/src/proxy/service.rs:1 - String literals should not start with leading whitespace. Found: ' — '
• /home/runner/work/mpp-rs/mpp-rs/src/protocol/core/headers.rs:1 - String literals should not start with leading whitespace. Found: ' now'
• /home/runner/work/mpp-rs/mpp-rs/src/protocol/core/headers.rs:1 - String literals should not start with leading whitespace. Found: ' now'
• /home/runner/work/mpp-rs/mpp-rs/src/protocol/core/headers.rs:1 - String literals should not start with leading whitespace. Found: ' now'

unsafe-needs-safety-comment (4 occurrences)

• /home/runner/work/mpp-rs/mpp-rs/src/server/mpp.rs:1 - Unsafe block requires a SAFETY comment explaining why this is safe.
• /home/runner/work/mpp-rs/mpp-rs/src/server/mpp.rs:1 - Unsafe block requires a SAFETY comment explaining why this is safe.
• /home/runner/work/mpp-rs/mpp-rs/src/server/mpp.rs:1 - Unsafe block requires a SAFETY comment explaining why this is safe.
• /home/runner/work/mpp-rs/mpp-rs/src/server/mpp.rs:1 - Unsafe block requires a SAFETY comment explaining why this is safe.

Issues by File

View grouped by file

/home/runner/work/mpp-rs/mpp-rs/src/protocol/core/challenge.rs (85 issues)

• Line 1: [warning] no-unwrap-in-lib
• Line 1: [warning] no-unwrap-in-lib
• Line 1: [warning] no-unwrap-in-lib
• Line 1: [warning] no-unwrap-in-lib
• Line 1: [warning] no-unwrap-in-lib
• ... and 80 more

/home/runner/work/mpp-rs/mpp-rs/src/client/tempo/session/mod.rs (58 issues)

• Line 1: [warning] no-unwrap-in-lib
• Line 1: [warning] no-unwrap-in-lib
• Line 1: [warning] no-unwrap-in-lib
• Line 1: [warning] no-unwrap-in-lib
• Line 1: [warning] no-unwrap-in-lib
• ... and 53 more

/home/runner/work/mpp-rs/mpp-rs/src/client/tempo/signing/mod.rs (54 issues)

• Line 1: [warning] no-unwrap-in-lib
• Line 1: [warning] no-unwrap-in-lib
• Line 1: [warning] no-unwrap-in-lib
• Line 1: [warning] no-unwrap-in-lib
• Line 1: [warning] no-unwrap-in-lib
• ... and 49 more

/home/runner/work/mpp-rs/mpp-rs/src/server/mpp.rs (47 issues)

• Line 1: [warning] no-unwrap-in-lib
• Line 1: [warning] no-unwrap-in-lib
• Line 1: [warning] no-unwrap-in-lib
• Line 1: [warning] no-unwrap-in-lib
• Line 1: [warning] no-unwrap-in-lib
• ... and 42 more

/home/runner/work/mpp-rs/mpp-rs/src/protocol/methods/tempo/session_method.rs (39 issues)

• Line 1: [warning] no-unwrap-in-lib
• Line 1: [warning] no-unwrap-in-lib
• Line 1: [warning] no-unwrap-in-lib
• Line 1: [warning] no-unwrap-in-lib
• Line 1: [warning] no-unwrap-in-lib
• ... and 34 more

/home/runner/work/mpp-rs/mpp-rs/src/client/tempo/session/channel_ops.rs (38 issues)

• Line 1: [warning] no-unwrap-in-lib
• Line 1: [warning] no-unwrap-in-lib
• Line 1: [warning] no-unwrap-in-lib
• Line 1: [warning] no-unwrap-in-lib
• Line 1: [warning] no-unwrap-in-lib
• ... and 33 more

/home/runner/work/mpp-rs/mpp-rs/src/protocol/methods/tempo/method.rs (35 issues)

• Line 1: [warning] no-unwrap-in-lib
• Line 1: [warning] no-unwrap-in-lib
• Line 1: [warning] no-unwrap-in-lib
• Line 1: [warning] no-unwrap-in-lib
• Line 1: [warning] no-unwrap-in-lib
• ... and 30 more

/home/runner/work/mpp-rs/mpp-rs/src/protocol/core/headers.rs (32 issues)

• Line 1: [warning] no-unwrap-in-lib
• Line 1: [warning] no-unwrap-in-lib
• Line 1: [warning] no-unwrap-in-lib
• Line 1: [warning] no-unwrap-in-lib
• Line 1: [warning] no-unwrap-in-lib
• ... and 27 more

/home/runner/work/mpp-rs/mpp-rs/src/client/tempo/charge/tx_builder.rs (30 issues)

• Line 1: [warning] no-unwrap-in-lib
• Line 1: [warning] no-unwrap-in-lib
• Line 1: [warning] no-unwrap-in-lib
• Line 1: [warning] no-unwrap-in-lib
• Line 1: [warning] no-unwrap-in-lib
• ... and 25 more

/home/runner/work/mpp-rs/mpp-rs/src/server/middleware.rs (27 issues)

• Line 1: [warning] no-unwrap-in-lib
• Line 1: [warning] no-unwrap-in-lib
• Line 1: [warning] no-unwrap-in-lib
• Line 1: [warning] no-unwrap-in-lib
• Line 1: [warning] no-unwrap-in-lib
• ... and 22 more

Showing 10 of 41 files

---

Posted by https://github.com/tempoxyz/lints