Skip to content

fix: update Dockerfile label to 'runtime authority server'#54

Merged
amavashev merged 1 commit into
mainfrom
claude/audit-docs-blogs-L2gsm
Mar 21, 2026
Merged

fix: update Dockerfile label to 'runtime authority server'#54
amavashev merged 1 commit into
mainfrom
claude/audit-docs-blogs-L2gsm

Conversation

@amavashev
Copy link
Copy Markdown
Collaborator

Budget authority is a subset of runtime authority — the Docker image description should use the umbrella positioning term.

https://claude.ai/code/session_01NEcAqmfZHsZV9WEZXNofWY

Budget authority is a subset of runtime authority — the Docker image
description should use the umbrella positioning term.

https://claude.ai/code/session_01NEcAqmfZHsZV9WEZXNofWY
@amavashev amavashev merged commit 7bc286e into main Mar 21, 2026
1 check passed
amavashev added a commit that referenced this pull request May 3, 2026
…lerts (#148)

Trivy alerts on the main-branch alert track only auto-close when a SARIF
scan publishes against refs/heads/main with the same (workflow, job,
category) tuple. Currently pr-container-scan.yml only triggers on
pull_request, so scans always upload against PR refs — main-track alerts
go stale after every fix merge.

Concrete impact: cycles-server-events had 13 stale gnutls alerts after
PR #54 (the gnutls fix) merged. Required a no-op Dockerfile-comment PR
(#57) to retrigger the scan and finally clear them.

Fix: add 'push: branches: [main]' trigger with the same paths filter.
Now every fix-merge to main re-scans and updates the alert track.

Side effect: image tag template changed from 'pr-N' to 'scan-{N or sha}'
so it's defined for both event types. Image is local-only (load:true,
push:false) so the tag value doesn't matter to anything downstream.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants