chore: remove the alpha quality warning, it is secure enough to be used in production #774
Labels
No labels
FreeBSD
Kind/Breaking
Kind/Bug
Kind/Chore
Kind/DependencyUpdate
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
Windows
linux-powerpc64le
linux-riscv64
linux-s390x
run-end-to-end-tests
run-forgejo-tests
No milestone
No project
No assignees
5 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
forgejo/runner!774
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "earl-warren/runner:wip-production"
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?
Refs https://codeberg.org/forgejo/discussions/issues/377
Please change also the repo description ❤️
Good catch, added a note.
chore: declare the Forgejo runner to be stable [skip ci] [skip cascade]to chore: declare the Forgejo runner to be stablechore: declare the Forgejo runner to be stableto chore: remove the alpha quality warning, it is secure enough to be used in productionFollowing discussions and concerns expressed in the past week, I changed the title to be "chore: remove the alpha quality warning, it is secure enough to be used in production " which is less ambitious than declaring it stable and also reflects the content of this pull request.
chore: remove the alpha quality warning, it is secure enough to be used in productionto chore: remove the alpha quality warning, it is secure enough to be used in production [skip ci] [skip cascade]f2a383269f1001343b2bchore: remove the alpha quality warning, it is secure enough to be used in production [skip ci] [skip cascade]to chore: remove the alpha quality warning, it is secure enough to be used in productionLet's wait for @Gusted input before merging. There is no urgency to do it right now, it is good to take time to think about the consequences.
Fine by me.
viceice-bot referenced this pull request2025-08-18 00:10:15 +00:00
viceice-bot referenced this pull request2025-08-18 00:31:54 +00:00
viceice-bot referenced this pull request2025-08-18 01:02:08 +00:00
viceice-bot referenced this pull request2025-08-18 01:31:08 +00:00
viceice-bot referenced this pull request2025-08-18 02:01:42 +00:00
viceice-bot referenced this pull request2025-08-18 02:31:02 +00:00
viceice-bot referenced this pull request2025-08-18 03:01:42 +00:00
viceice-bot referenced this pull request2025-08-18 03:31:00 +00:00
viceice-bot referenced this pull request2025-08-18 04:01:39 +00:00
viceice-bot referenced this pull request2025-08-18 04:31:00 +00:00
viceice-bot referenced this pull request2025-08-18 05:02:28 +00:00
viceice-bot referenced this pull request2025-08-18 05:31:15 +00:00