ci: pin actions and harden release packaging #633
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
thwap/thwap-pagesd!633
Loading…
Reference in a new issue
No description provided.
Delete branch "chore/issue-cicd"
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?
What
Lumped CI/CD issues branch (#522+ cleanup).
thwap-actions/golang-releaseandthwap-actions/docker-buildare now referenced at immutable commit SHAs (880ed2d…,bfedfe4…) instead of the mutable@mainref, so a force-push to those action branches no longer changes this repo's CI/release behavior without review. (No release tags exist on either action repo yet, so a commit SHA is the immutable pin.)cmd/tpagectl/distandcmd/thwap-pagesd/distexist and contain binaries, and errors if the number of packaged archives doesn't match the binary count — no more silently shipping a release without.tar.gz/.ziparchives if thegolang-releaseoutput convention changes.tpagectlsnap app declaresplugs: [network, home, dbus]so a strict-confined snap can reach the daemon, write the config file, and use Secret Service keychain storage.Triage — already resolved (closed without code change, after verification):
.exe: bothci.ymlandrelease.ymlbuild viathwap-actions/golang-release, which names Windows binariestpagectl_<ver>_windows_<arch>.exe(and the finalize step zips those). No manualtpagectl-windows-amd64naming remains.Why
Second lump of the #522+ issue cleanup (CI/CD & packaging).
Testing
snapcraft.yamlparse; pre-commit "Validate Forgejo Actions files" and "check yaml" passSystemExit(failing the step)go test+ pre-commit hooks passBreaking Changes
None. Pinning to SHAs and failing loudly are additive/behavior-hardening.
Closes #615
Closes #619
Closes #621