New Issue

[RELEASE] Forgejo 1.18.3-1 #335

Closed

opened by dachary · 8 comments

dachary commented

Owner

Following the instructions

cherry-pick all commits from Gitea release/v1.18 on v1.18/forgejo except:
- #334 AKA https://github.com/go-gitea/gitea/pull/22805
- https://github.com/go-gitea/gitea/pull/22764
v1.18/forgejo CI https://forgejo-ci.codeberg.org/forgejo/forgejo/pipeline/491
publish for testing at https://codeberg.org/forgejo-experimental/ under 1.18.3-1
publish the release https://ci.dachary.org/forgejo/release/pipeline/7
publish release notes #319
- Gitea changes
- Alpine changes for git, gnupg, sqlite, openssh
merge forgejo-development in forgejo
~~publish blog post~~
rebuild main on https://codeberg.org/Forgejo/website

publish toot

#Forgejo v1.18.3-1 was just released! This is a minor patch. Check out the release notes and download it at https://forgejo.org/releases/. If you experience any issues with this release, please report to https://codeberg.org/forgejo/forgejo/issues.

release 1.18.3-1
DNS update

Following [the instructions](https://codeberg.org/forgejo/forgejo/src/branch/forgejo/CONTRIBUTING/RELEASE.md) - [x] cherry-pick all commits from Gitea release/v1.18 on [v1.18/forgejo](https://codeberg.org/forgejo/forgejo/src/branch/v1.18/forgejo) except: * https://codeberg.org/forgejo/forgejo/issues/334 AKA https://github.com/go-gitea/gitea/pull/22805 * https://github.com/go-gitea/gitea/pull/22764 - [x] [v1.18/forgejo](https://codeberg.org/forgejo/forgejo/src/branch/v1.18/forgejo) CI https://forgejo-ci.codeberg.org/forgejo/forgejo/pipeline/491 - [x] publish for testing at https://codeberg.org/forgejo-experimental/ under 1.18.3-1 - [x] https://codeberg.org/forgejo-integration https://ci.dachary.org/forgejo-integration/forgejo/pipeline/87 - [x] https://codeberg.org/forgejo-experimental/ https://ci.dachary.org/forgejo/experimental/pipeline/20 - [x] end-to-end testing https://ci.dachary.org/dachary/scripted-configuration/pipeline/127/3 - [x] publish the release https://ci.dachary.org/forgejo/release/pipeline/7 - [x] publish release notes https://codeberg.org/forgejo/forgejo/pulls/319 - Gitea changes - Alpine changes for [git](https://pkgs.alpinelinux.org/packages?name=git&branch=v3.16), [gnupg](https://pkgs.alpinelinux.org/packages?name=gnupg&branch=v3.16), [sqlite](https://pkgs.alpinelinux.org/packages?name=sqlite&branch=v3.16), [openssh](https://pkgs.alpinelinux.org/packages?name=openssh&branch=v3.16) - [x] merge forgejo-development in forgejo - [ ] ~~publish blog post~~ - [x] rebuild main on https://codeberg.org/Forgejo/website - [x] publish toot ``` #Forgejo v1.18.3-1 was just released! This is a minor patch. Check out the release notes and download it at https://forgejo.org/releases/. If you experience any issues with this release, please report to https://codeberg.org/forgejo/forgejo/issues. ``` - [x] release 1.18.3-1 - [x] DNS update

dachary added this to the Forgejo v1.18.3-1 milestone

dachary added the

forgejo/release

label

crystal was assigned by dachary

dachary self-assigned this

dachary commented

Poster

Owner

@crystal I have concerns that some backports are being merged without testing. See this one which fails because Gitea has not yet fixed the broken CI for the v1.18 branch.

When proceeding with the release we will have to be extra careful about the commits that are cherry-picked and verify which of those were merged with no CI pass.

@crystal I have concerns that some backports are being merged without testing. See [this one](https://github.com/go-gitea/gitea/pull/22757) which fails because Gitea has not yet fixed the broken CI for the v1.18 branch. When proceeding with the release we will have to be extra careful about the commits that are cherry-picked and verify which of those were merged with no CI pass.

dachary added the due date 2023-02-09

crystal commented

Owner

At this point I'm starting to wonder if I shouldn't send a contribution to fix their CI

dachary commented

Poster

Owner

I'm quite sure they will do it real soon. I just commented to make sure we don't forget to check when creating the release.

👍 1

crystal commented

Owner

I did get this passing CI pipeline with the pull request you mentioned before included. It looks like the CI fix was also backported to Gitea 1.18 about fifteen minutes ago.

[I did get this passing CI pipeline](https://ci.cryxtal.org/crystal/forgejo/build/45) with the pull request you mentioned before included. [It looks like the CI fix was also backported to Gitea 1.18 about fifteen minutes ago.](https://ci.cryxtal.org/crystal/forgejo/build/45)

👍 1

dachary commented

Poster

Owner

Manually check the footer for the translation of software.

crystal commented

Owner

Looks like aria.footer.software exists here

Looks like `aria.footer.software` exists [here](https://codeberg.org/forgejo/forgejo/src/branch/v1.18/forgejo/options/locales/gitea_en-US.ini#L112)

👍 1

dachary commented

Poster

Owner

Manually check the footer for the translation of software.

> Manually check the footer for the translation of software. ![image](/attachments/c41de242-d58b-478d-a666-a0f0ca9f8209)

image.png

36 KiB

dachary commented

Poster

Owner

@crystal here is the recording of our session

https://cloud.dachary.org/s/4JwmMaZC6HGaAA2

If you listen, you will catch a few things I said while your internet connection was playing tricks on you 😄 But nothing substantial.

@crystal here is the recording of our session https://cloud.dachary.org/s/4JwmMaZC6HGaAA2 If you listen, you will catch a few things I said while your internet connection was playing tricks on you 😄 But nothing substantial.

dachary closed this issue