Downloads of v 1.16.6:


Last Update:

21 Apr 2022

Package Maintainer(s):

Software Author(s):

  • Gitea


gitea git


This is not the latest version of Gitea available.

  • 1
  • 2
  • 3

1.16.6 | Updated: 21 Apr 2022



Downloads of v 1.16.6:



Software Author(s):

  • Gitea


gitea git

  • 1
  • 2
  • 3
Gitea 1.16.6

This is not the latest version of Gitea available.

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests

Validation Testing Passed

Verification Testing Passed


Scan Testing Successful:

No detections found in any package files

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install Gitea, run the following command from the command line or from PowerShell:


To upgrade Gitea, run the following command from the command line or from PowerShell:


To uninstall Gitea, run the following command from the command line or from PowerShell:


Deployment Method:

📝 NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Enter Your Internal Repository Url

(this should look similar to

2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Copy Your Script

choco upgrade gitea -y --source="'INTERNAL REPO URL'" --version="'1.16.6'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade gitea -y --source="'INTERNAL REPO URL'" --version="'1.16.6'" 

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Install gitea
    name: gitea
    version: '1.16.6'
    state: present

See docs at

chocolatey_package 'gitea' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '1.16.6'

See docs at

cChocoPackageInstaller gitea
    Name     = "gitea"
    Version  = "1.16.6"
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { 'gitea':
  ensure   => '1.16.6',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',

Requires Puppet Chocolatey Provider module. See docs at

4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package was approved as a trusted package on 22 Apr 2022.


Gitea is a lightweight code hosting solution written in Go and published under the MIT license.


$ErrorActionPreference = 'Stop';

$packageName= 'gitea'
$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$url        = ''
$url64      = ''
$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"

$packageArgs = @{
  packageName   = $packageName

  url           = $url
  url64bit      = $url64

  softwareName  = 'Gitea'

  checksum      = 'de095a63d6d7a10458a23e430c2bf228ed2f0af59ebe08997196a0b890efef35'
  checksumType  = 'sha256'
  checksum64    = 'a57a2c077eea9fdb09978f3e7771eaaa45708b9be6dbefa580840140920f4261'
  checksumType64= 'sha256'

  fileFullPath  = "$toolsDir\gitea.exe"

  validExitCodes= @(0)

Get-ChocolateyWebFile @packageArgs

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Add to Builder Version Downloads Last Updated Status
Gitea 1.16.7 130 Monday, May 2, 2022 Approved
Gitea 1.16.6 92 Thursday, April 21, 2022 Approved
Gitea 1.16.5 198 Thursday, March 24, 2022 Approved
Gitea 1.16.4 79 Monday, March 14, 2022 Approved
Gitea 1.16.3 84 Thursday, March 3, 2022 Approved
Gitea 1.16.2 68 Thursday, February 24, 2022 Approved
Gitea 1.16.0 215 Monday, January 31, 2022 Approved
Gitea 1.15.10 158 Friday, January 14, 2022 Approved
Gitea 1.15.9 168 Thursday, December 30, 2021 Approved

    • Only request write when necessary (#18657) (#19422)
    • Disable service worker by default (#18914) (#19342)
    • When dumping trim the standard suffices instead of a random suffix (#19440) (#19447)
    • Fix DELETE request for non-existent public key (#19443) (#19444)
    • Don't panic on ErrEmailInvalid (#19441) (#19442)
    • Add uploadpack.allowAnySHA1InWant to allow --filter=blob:none with older git clients (#19430) (#19438)
    • Warn on SSH connection for incorrect configuration (#19317) (#19437)
    • Search Issues via API, dont show 500 if filter result in empty list (#19244) (#19436)
    • When updating mirror repo intervals by API reschedule next update too (#19429) (#19433)
    • Fix nil error when some pages are rendered outside request context (#19427) (#19428)
    • Fix double blob-hunk on diff page (#19404) (#19405)
    • Don't allow merging PR's which are being conflict checked (#19357) (#19358)
    • Fix middleware function's placements (#19377) (#19378)
    • Fix invalid CSRF token bug, make sure CSRF tokens can be up-to-date (#19338)
    • Restore user autoregistration with email addresses (#19261) (#19312)
    • Move checks for pulls before merge into own function (#19271) (#19277)
    • Granular webhook events in editHook (#19251) (#19257)
    • Only send webhook events to active system webhooks and only deliver to active hooks (#19234) (#19248)
    • Use full output of git show-ref --tags to get tags for PushUpdateAddTag (#19235) (#19236)
    • Touch mirrors on even on fail to update (#19217) (#19233)
    • Hide sensitive content on admin panel progress monitor (#19218 & #19226) (#19231)
    • Fix clone url JS error for the empty repo page (#19209)
    • Bump goldmark to v1.4.11 (#19201) (#19203)
    • Prevent intermittent failures in RepoIndexerTest (#19225 #19229) (#19228)
    • Revert the minimal golang version requirement from 1.17 to 1.16 and add a warning in Makefile (#19319)
  • MISC
    • Performance improvement for add team user when org has more than 1000 repositories (#19227) (#19289)
    • Check go and nodejs version by go.mod and package.json (#19197) (#19254)

This package has no dependencies.

Discussion for the Gitea Package

Ground Rules:

  • This discussion is only about Gitea and the Gitea package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Gitea, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus