Add blog for v1.21.1 #325
No reviewers
Labels
No Label
in progress
kind/bug
kind/deployment
kind/docs
kind/enhancement
kind/feature
kind/lint
kind/proposal
kind/question
kind/security
kind/testing
kind/translation
kind/ui
lgtm/done
lgtm/need 1
lgtm/need 2
priority/critical
priority/low
priority/maybe
priority/medium
reviewed/duplicate
reviewed/invalid
reviewed/wontfix
status/blocked
status/needs-feedback
status/wip
No Milestone
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitea/blog#325
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "lunny/gitea-blog:lunny/v1.21.1"
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?
@ -0,0 +12,4 @@
Gitea 1.21.1 is now released including [24](https://github.com/go-gitea/gitea/pulls?q=is%3Apr+milestone%3A1.21.1+is%3Amerged) merged PRs and a high impact security vulnerability. You are highly recommanded to upgrade to this version ASAP.
The problem was that previously only the ID of comments, among other types, was used to find the comment.
However, as you request the comment on a specific repo, it must also be checked that the ID of the given comment belongs to the given repo as you can otherwise retrieve content you are not supposed to see.
Remove
the ID of
Minor nits, no need to add me as co-author (unless you want to give me internet bonus points™️)
@ -0,0 +9,4 @@
coverImageRelease: 1.21.1
---
Gitea 1.21.1 is now released including [24](https://github.com/go-gitea/gitea/pulls?q=is%3Apr+milestone%3A1.21.1+is%3Amerged) merged PRs and a high impact security vulnerability. You are highly recommanded to upgrade to this version ASAP.
@ -0,0 +15,4 @@
However, as you request the comment on a specific repo, it must also be checked that the ID of the given comment belongs to the given repo as you can otherwise retrieve content you are not supposed to see.
<!-- Security Thanks! -->
We would like to give a special thanks to Forgejo team for reporting a security issue that was patched in this release.