gitea/blog
44
20
Fork 31
Code Issues 10 Pull Requests 1 Actions Activity

Blog post 1.18.0 #222

Merged
6543 merged 3 commits from jolheiser/blog:1.18.0 into main 2022-12-30 02:51:10 +00:00
Conversation 0 Commits 3 Files Changed 5 +372
jolheiser commented 2022-12-29 20:13:58 +00:00
Owner
Copy Link

Collaborative editing over at https://cryptpad.cz/code/#/2/code/edit/zq4phJiJg00ydHpdiZ2I1UO8/

Collaborative editing over at https://cryptpad.cz/code/#/2/code/edit/zq4phJiJg00ydHpdiZ2I1UO8/
jolheiser added 1 commit 2022-12-29 20:13:59 +00:00
initial draft of 1.18.0 
Signed-off-by: jolheiser <john.olheiser@gmail.com>
All checks were successful
continuous-integration/drone/pr Build is passing
Details
a039d1392e
lafriks reviewed 2022-12-29 21:16:06 +00:00
content/post/release-of-1.18.0.md Outdated
@ -0,0 +65,4 @@
<!-- Changelog Details -->
* SECURITY
* Remove ReverseProxy authentication from the API ([#22219](https://github.com/go-gitea/gitea/pull/22219)) ([#22251](https://github.com/go-gitea/gitea/pull/22251))
* Support Go Vulnerability Management ([#21139](https://github.com/go-gitea/gitea/pull/21139))
lafriks commented 2022-12-29 21:16:06 +00:00
Member
Copy Link

I know this is in changelog but it's very misleading as it's not really related to gitea itself but is just internal process for development.

I know this is in changelog but it's very misleading as it's not really related to gitea itself but is just internal process for development.
jolheiser commented 2022-12-29 23:10:44 +00:00
Author
Owner
Copy Link

I am largely ambivalent on whether this goes here or down in the build section. Does anyone else have an opinion on it?

I think this, while not being a security fix, is still a security PR.
That being said, as lafriks pointed out, this is just something we run in CI to check against the Go vuln db.

I am largely ambivalent on whether this goes here or down in the build section. Does anyone else have an opinion on it? I think this, while not being a security *fix*, is still a security PR. That being said, as lafriks pointed out, this is just something we run in CI to check against the Go vuln db.
6543 marked this conversation as resolved
jolheiser added 1 commit 2022-12-29 22:19:41 +00:00
chore: updates from pad 
Signed-off-by: jolheiser <john.olheiser@gmail.com>
All checks were successful
continuous-integration/drone/pr Build is passing
Details
df4d396850
KN4CK3R reviewed 2022-12-29 22:36:01 +00:00
content/post/release-of-1.18.0.md Outdated
@ -0,0 +14,4 @@
We have merged [535](https://github.com/go-gitea/gitea/pulls?q=is%3Apr+milestone%3A1.18.0+is%3Amerged) pull requests to release this version.
<!-- Security Thanks! -->e
KN4CK3R commented 2022-12-29 22:29:42 +00:00
Member
Copy Link
- e
```diff - e ```
jolheiser marked this conversation as resolved
content/post/release-of-1.18.0.md Outdated
@ -0,0 +48,4 @@
This means that at the moment, the following languages/types can be stored as a package:
- C++
KN4CK3R commented 2022-12-29 22:33:42 +00:00
Member
Copy Link
+ Composer (PHP)
+ Conan (C++)
+ Container Images
+ Generic (raw binaries)
+ Helm Charts
+ Maven (Java)
+ npm (JavaScript)
+ NuGet (.NET, C#/VB)
+ Pub (Dart)
+ PyPI (Python)
+ RubyGems (Ruby)
+ Vagrant Boxes

I would list them like this.

```diff + Composer (PHP) + Conan (C++) + Container Images + Generic (raw binaries) + Helm Charts + Maven (Java) + npm (JavaScript) + NuGet (.NET, C#/VB) + Pub (Dart) + PyPI (Python) + RubyGems (Ruby) + Vagrant Boxes ``` I would list them like this.
jolheiser marked this conversation as resolved
content/post/release-of-1.18.0.md
@ -0,0 +81,4 @@
![issue forms screenshot 1](/demos/20987/1.png)
As you can see above, you can require with these forms that certain standards are being met, while being (hopefully) idiot-proof and intuitive at the same time. <!--Can I write it like that?-->
KN4CK3R commented 2022-12-29 22:34:57 +00:00
Member
Copy Link

I would remove the "idiot-proof".

I would remove the "idiot-proof".
jolheiser commented 2022-12-29 22:38:43 +00:00
Author
Owner
Copy Link

"user-friendly"

"user-friendly"
jolheiser marked this conversation as resolved
jolheiser added 1 commit 2022-12-29 22:40:41 +00:00
review: KN4CK3R 
Signed-off-by: jolheiser <john.olheiser@gmail.com>
All checks were successful
continuous-integration/drone/pr Build is passing
Details
6408e0eb53
jolheiser changed title from WIP: Blog post 1.18.0 to Blog post 1.18.0 2022-12-29 22:49:15 +00:00
KN4CK3R approved these changes 2022-12-29 22:52:58 +00:00
KN4CK3R left a comment
Member
Copy Link

I did not check the Changelog Details but the upper part lgtm.

I did not check the `Changelog Details` but the upper part lgtm.
6543 approved these changes 2022-12-30 02:50:54 +00:00
6543 merged commit 4d79b4ea62 into main 2022-12-30 02:51:10 +00:00
6543 referenced this issue from a commit 2022-12-30 02:51:11 +00:00
Blog post 1.18.0 (#222)
Sign in to join this conversation.
Reviewers
No reviewers
KN4CK3R
6543
Labels
Clear labels   
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 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
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
4 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: gitea/blog#222
No description provided.
Delete Branch "jolheiser/blog:1.18.0"

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?