Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add changelog for v1.11.3 #10700

Merged
merged 3 commits into from
Mar 10, 2020
Merged

Conversation

lunny
Copy link
Member

@lunny lunny commented Mar 10, 2020

To avoid docker image gitea/gitea:1 become v1.10.6, this version have to be tagged after minutes when v1.10.6 tagged .

@lunny lunny added type/docs This PR mainly updates/creates documentation skip-changelog This PR is irrelevant for the (next) changelog, for example bug fixes for unreleased features. labels Mar 10, 2020
@lunny lunny added this to the 1.11.3 milestone Mar 10, 2020
@GiteaBot GiteaBot added the lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. label Mar 10, 2020
@GiteaBot GiteaBot added lgtm/need 1 This PR needs approval from one additional maintainer to be merged. and removed lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. labels Mar 10, 2020
@sapk
Copy link
Member

sapk commented Mar 10, 2020

For the docker tag bug maybe we should remove the autotag from n-2 version branch ?

@lunny
Copy link
Member Author

lunny commented Mar 10, 2020

@sapk I think make the max semantic version as gitea/gitea:1 everytime when we release that docker tag.

Co-Authored-By: John Olheiser <john.olheiser@gmail.com>
@GiteaBot GiteaBot added lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. and removed lgtm/need 1 This PR needs approval from one additional maintainer to be merged. labels Mar 10, 2020
CHANGELOG.md Outdated Show resolved Hide resolved
Co-Authored-By: Antoine GIRARD <sapk@users.noreply.github.com>
@sapk sapk added the status/blocked This PR cannot be merged yet, i.e. because it depends on another unmerged PR label Mar 10, 2020
@sapk
Copy link
Member

sapk commented Mar 10, 2020

I added the label blocked just to make it explicit that it need to be merged (or at least tagged) after #10699

@zeripath zeripath removed the status/blocked This PR cannot be merged yet, i.e. because it depends on another unmerged PR label Mar 10, 2020
@zeripath zeripath merged commit f3cacf1 into go-gitea:release/v1.11 Mar 10, 2020
@zeripath
Copy link
Contributor

Please send forward ports.

@lunny lunny deleted the lunny/changelog_1.11.3 branch March 11, 2020 01:21
lunny added a commit to lunny/gitea that referenced this pull request Mar 11, 2020
* Add changelog for v1.11.3

* Apply suggestions from code review

Co-Authored-By: John Olheiser <john.olheiser@gmail.com>

* Update CHANGELOG.md

Co-Authored-By: Antoine GIRARD <sapk@users.noreply.github.com>

Co-authored-by: John Olheiser <john.olheiser@gmail.com>
Co-authored-by: Antoine GIRARD <sapk@users.noreply.github.com>
lunny added a commit that referenced this pull request Mar 11, 2020
* Add changelog for v1.11.3

* Apply suggestions from code review

* Update CHANGELOG.md

Co-authored-by: John Olheiser <john.olheiser@gmail.com>
Co-authored-by: Antoine GIRARD <sapk@users.noreply.github.com>
Co-authored-by: Lauris BH <lauris@nix.lv>
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. skip-changelog This PR is irrelevant for the (next) changelog, for example bug fixes for unreleased features. type/docs This PR mainly updates/creates documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants