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

gitea: 1.9.6 -> 1.10.0 #73416

Merged
merged 1 commit into from Nov 19, 2019
Merged

gitea: 1.9.6 -> 1.10.0 #73416

merged 1 commit into from Nov 19, 2019

Conversation

kolaente
Copy link
Member

Motivation for this change

Gitea Major release https://blog.gitea.io/2019/11/gitea-1.10.0-is-released/

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Ensured that relevant documentation is up to date
  • Fits CONTRIBUTING.md.
Notify maintainers

cc @

@etu
Copy link
Contributor

etu commented Nov 15, 2019

@GrahamcOfBorg test gitea

@flokli
Copy link
Contributor

flokli commented Nov 17, 2019

Can this be rebased on top of master, now that #73415 is merged?

@kolaente kolaente changed the title gitea: 1.9.5 -> 1.10.0 gitea: 1.9. 6-> 1.10.0 Nov 18, 2019
@kolaente kolaente changed the title gitea: 1.9. 6-> 1.10.0 gitea: 1.9.6 -> 1.10.0 Nov 18, 2019
@kolaente
Copy link
Member Author

@flokli Done.

@etu etu merged commit 84d582f into NixOS:master Nov 19, 2019
@etu etu mentioned this pull request Nov 19, 2019
10 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants