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

[Backport release-24.11] forgejo: 9.0.3 -> 10.0.0 #374849

Merged
merged 2 commits into from
Jan 19, 2025

Conversation

nixpkgs-ci[bot]
Copy link
Contributor

@nixpkgs-ci nixpkgs-ci bot commented Jan 18, 2025

Bot-based backport to release-24.11, triggered by a label in #374668.

  • Before merging, ensure that this backport is acceptable for the release.
    • Even as a non-commiter, if you find that it is not acceptable, leave a comment.

@emilylange
Copy link
Member

To elaborate on why this major version bump is acceptable to backport for those that may just randomly stumble upon this and are wondering:

We provide pkgs.forgejo and pkgs.forgejo-lts.
The nixos/forgejo module defaults to pkgs.forgejo-lts and users have to explicitly opt-into the non-LTS version.

So we build on that fact and make pkgs.forgejo an unstable moving target on stable releases instead of marking it as EOL whenever the time comes as that would leave users in the dust.

This is very similar to pkgs.incus and pkgs.incus-lts as far as I can tell.

@wolfgangwalther
Copy link
Contributor

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review pr 374849


x86_64-linux

✅ 2 packages built:
  • forgejo
  • forgejo.data

aarch64-linux

✅ 2 packages built:
  • forgejo
  • forgejo.data

x86_64-darwin

⏩ 2 packages marked as broken and skipped:
  • forgejo
  • forgejo.data

aarch64-darwin

⏩ 2 packages marked as broken and skipped:
  • forgejo
  • forgejo.data

@wolfgangwalther wolfgangwalther merged commit 8dab93a into release-24.11 Jan 19, 2025
34 of 36 checks passed
@wolfgangwalther wolfgangwalther deleted the backport-374668-to-release-24.11 branch January 19, 2025 18:42
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.

3 participants