Revert "ci: log in to the container registry as fmartingr" (FMG-5) #11
No reviewers
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
fmartingr/smtp2shoutrrr!11
Loading…
Reference in a new issue
No description provided.
Delete branch "agent/full-stack-developer/fmg-5-revert"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Reverts #10 (commit
d1d3f4d) at your request on FMG-5..github/workflows/release.ymlgoes back to-u ${{ github.actor }}, and the comment that explained the fixed username is removed. The file is byte-identical to its state at7565618, before #10 landed.This restores the failure described in FMG-5: a tag pushed by
butterrobotlogs in asbutterrobot, and the image push is expected to fail with401 Unauthorized: reqPackageAccess— while the login step still reportsLogin Succeeded, since Forgejo's/v2/tokenissues an anonymous token either way.No closing keyword here on purpose: merging a revert should not mark FMG-5 done.
Revert of a CI-config change, no Go code touched. I checked the workflow YAML still parses; there is no Go toolchain in this environment, so the repo's
format/lint/test/build/goreleaser-linttargets were not run locally.FMG-5