github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 02:24:21 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Release: Publish Gitea 1.23.4 #14146

New Issue
Closed
opened 2025-11-02 11:04:19 -06:00 by GiteaMirror · 5 comments
GiteaMirror commented 2025-11-02 11:04:19 -06:00
Owner
Copy Link

Originally created by @lunny on GitHub (Feb 17, 2025).

1.23.4

Originally created by @lunny on GitHub (Feb 17, 2025). ## 1.23.4 * [ ] Check cowdin sync * [x] Prepare a new changelog (there are a lot of new changes) and update CHANGELOG.md * [x] Close milestone of 1.23.4 * [x] Release 1.23.4 from release/v1.23 branch * [x] Generate changelog_1.23.4.md from merged CHANGELOG.md * [x] Frontend changelog to main branch #33649 * [x] Tag 1.23.4 with `git tag -s -f changelog_1.23.4.md v1.23.4` and Push to Github * [x] Wait for the release created and check whether the release artifacts generated * [x] Check whether Github release attachments are generated and normal * [x] Check whether the binaries generated under https://dl.gitea.com/gitea/1.23.4/ and normal * [x] Check whether docker images are generated https://hub.docker.com/r/gitea/gitea/tags?page=&page_size=&ordering=&name=1.23.4 * [x] If the release does work then make it out of draft so that it's public for everyone. * [x] Official packages updated * [x] Homebrew https://github.com/Homebrew/homebrew-core/pull/208233 * [x] Snap https://snapcraft.io/gitea * [x] Helm Chart https://gitea.com/gitea/helm-chart/pulls/797 * [x] Terraform https://gitea.com/gitea/terraform-provider-gitea/pulls/97 * [x] Update "version.json" to 1.23.4 * [x] Update documentation's latest stable version to 1.23.4 * [x] Confirm blog is ready and merge * [x] Announce the 1.23.4 release.
GiteaMirror commented 2025-11-02 11:04:20 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Feb 19, 2025):

The CHANGELOG.md on main branch is out-dated for long time again.

No idea why there are always things forgotten again and again.

@wxiaoguang commented on GitHub (Feb 19, 2025): The `CHANGELOG.md` on main branch is out-dated for long time again. No idea why there are always things forgotten again and again.
GiteaMirror commented 2025-11-02 11:04:20 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Feb 20, 2025):

The frontport of changelog task item added and #33649 is sent.

@lunny commented on GitHub (Feb 20, 2025): The frontport of changelog task item added and #33649 is sent.
GiteaMirror commented 2025-11-02 11:04:20 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Feb 20, 2025):

I still think it should either:

  • Add more todo/check list items
  • Simplify the CHANGELOG.md (just link to somewhere else) and only use one mechanism to maintain and display

And reiterate my previous comment: https://github.com/go-gitea/gitea/pull/32924#issuecomment-2556150881

I think there should be a document recording all tasks need to be checked/done regularly and when they were done last time, I could only guess some:

1. dependency update
    * language (golang, nodejs)
    * go, js, and other packages
    * docker images
2. crowdin sync
3. gitea.com / demo update
4. release packages: snap, homebrew, etc
@wxiaoguang commented on GitHub (Feb 20, 2025): I still think it should either: * Add more todo/check list items * Simplify the CHANGELOG.md (just link to somewhere else) and only use one mechanism to maintain and display And reiterate my previous comment: https://github.com/go-gitea/gitea/pull/32924#issuecomment-2556150881 ``` I think there should be a document recording all tasks need to be checked/done regularly and when they were done last time, I could only guess some: 1. dependency update * language (golang, nodejs) * go, js, and other packages * docker images 2. crowdin sync 3. gitea.com / demo update 4. release packages: snap, homebrew, etc ```
GiteaMirror commented 2025-11-02 11:04:21 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Feb 20, 2025):

  1. dependency update
    language (golang, nodejs)
    go, js, and other packages
    docker images

What did you mean

  1. crowdin sync

Did you mean backport languages changes from main branch? The crowdin data currently will only be sync to main branch.

  1. gitea.com / demo update

Since both these two instances never follow a fixed release, should we still need to check them?

  1. release packages: snap, homebrew, etc

Added.

@lunny commented on GitHub (Feb 20, 2025): > 1. dependency update language (golang, nodejs) go, js, and other packages docker images What did you mean > 2. crowdin sync Did you mean backport languages changes from main branch? The crowdin data currently will only be sync to main branch. > 3. gitea.com / demo update Since both these two instances never follow a fixed release, should we still need to check them? > 4. release packages: snap, homebrew, etc Added.
GiteaMirror commented 2025-11-02 11:04:21 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Feb 20, 2025):

  1. dependency update
    language (golang, nodejs)
    go, js, and other packages
    docker images

What did you mean

I mean update dependency

I mean

I think there should be a document recording all tasks need to be checked/done REGULARY

Image

@wxiaoguang commented on GitHub (Feb 20, 2025): > > 1. dependency update > > language (golang, nodejs) > > go, js, and other packages > > docker images > > What did you mean I mean update dependency I mean > > I think there should be a document recording all tasks need to be checked/done **REGULARY** ![Image](https://github.com/user-attachments/assets/bdb94826-3660-49bd-b048-2714326fd70a)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#14146
Delete Branch "%!s()"

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?