treewide: remove refs/tags/ from github release meta.changelog

[pbsds]

I saw #346488 was a thing, so i figured a redo of #338301 was warranted. Part of #346453

diff of jq <packages.json 'to_entries[]|"\(.key) \(.value.meta.changelog)"' -r:

https://gist.github.com/pbsds/02ee3d771ab31e15c3c67db9c79c4e57

Made using the script in #338301 without modifications

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

---

Add a 👍 reaction to pull requests you find important.

[SuperSandro2000]

This change is kinda backwards. We should take version and optionally add the v prefix.

[adamcstephens]

I agree with Sandro that we should use version if these links are broken.

[pbsds]

semantically the github release urls are derived from the git tag, which don't necessarily map cleanly from the version. In #338301 the idea of a tag input and output for fetchFromGitHub was brought up which I fully support, but in the meanwhile I believe this is the easiest treewide to consistently enforce.

[adamcstephens]

I don't really understand. How is what you propose any simpler, clearer, or more reliable than using the version like so:

changelog = "https://codeberg.org/forgejo/forgejo/releases/tag/v${version}";

In my opinion your version is more complex, and needlessly spends compute cycles modifying strings when we already have said string in version. This is all so you don't have to put the v in front of version in the URL?

If an upstream is so far off from our versioning that you can't just re-use version, then treat that as the odd-ball that it is. There's no reason to apply premature optimization and complexity everywhere else because of edge cases.

[pbsds]

Okay, have it your way. Note now that the review requires you to view the whole file. I assume someone will in the future come along and revert the change back to src.rev not knowing better.

I left forgejo with lib.removePrefix since rev is provided as an input to callPackage

[emilylange]

I left forgejo with lib.removePrefix since rev is provided as an input to callPackage

version is used and required in multiple places in this internal abstraction (generic.nix) of Forgejo.
Please change it to v${version}, just like you did with all the other packages.

Thanks :)

[pbsds]

Thanks for pointing that out 👍

addressed