Skip to content

ci: add aireceipts pr-check (notice-only cost receipt) #105

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
anandgupta42 wants to merge 3 commits into
base: main
Choose a base branch
from
+12 −0
Open

ci: add aireceipts pr-check (notice-only cost receipt) #105

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
80d6849
ci: add aireceipts pr-check (notice-only cost receipt)
anandgupta42 Jul 8, 2026
f13c3a2
ci: pin aireceipts-cli@0.5.0 (supply-chain: no mutable @latest with w…
anandgupta42 Jul 8, 2026
ed1328e
ci: revert to aireceipts-cli@latest (internal repos stay on @latest)
anandgupta42 Jul 8, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions .github/workflows/aireceipts.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,12 @@
name: aireceipts
on: [pull_request]
permissions:
contents: read
pull-requests: write
jobs:
check:
runs-on: ubuntu-latest
steps:
- run: npx -y aireceipts-cli@latest pr-check

@kilo-code-bot kilo-code-bot Bot Jul 8, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

WARNING: @latest reintroduces an unpinned supply-chain risk with a write token

This commit reverts the @0.5.0 pin (added explicitly for "supply-chain: no mutable @latest with write token") back to @latest. Since the step exposes GH_TOKEN with pull-requests: write, every run resolves and executes whatever aireceipts-cli version is @latest at run time — so a compromised or broken newly published release runs with PR-write capability before this repo has reviewed it. If the floating version is intentional, consider isolating the install step from the write token (or otherwise limiting the token's blast radius) to reduce the risk.

Reply with @kilocode-bot fix it to have Kilo Code address this issue.

env:
GH_TOKEN: ${{ github.token }}
Loading