At least the output from `npins update nixpkgs`

No reason to

This script fuly automates releases. In a future commit this will be run by CI

I ran the script once to generate the initial version 0.1.0: https://github.com/NixOS/nixpkgs-check-by-name/releases/tag/0.1.0

This calls the release script whenever a commit is pushed to the main branch, such that merging a PR
that increases the version number immediately causes a new release

This also turns off the other CI for pushes to the main branch, doesn't seem necessary

Improves upon the automated update PRs introduced in NixOS#12 to resolve issues brought up in the first automated PR NixOS#14.

* Give more information about the updates, not much, but at least the output of npins update
* Update all npins sources, not just Nixpkgs.
* Run `cargo update`
* Make it trigger CI by using an unprivileged separate machine account (welcome, @infinixbot!)
* Set committer and author of the commits to the machine account

This sets up automated releases, mainly so that we can distribute a pre-built version of the tool, allowing Nixpkgs' CI to fetch it without building.

Hopefully..

See https://github.com/NixOS/nixpkgs-check-by-name/actions/runs/8381658441/job/22953710054#step:4:575 for the failure

Set `GH_TOKEN` to fix automated releases

Don't commit PR body for automated updates

Fix automated updates (another try)

And make it also build the autoPrUpdate derivation

See NixOS#20 (comment)

We fix this by telling the update scripts explicitly which files they should update and passing that
information in from CI

Fix updates (another try)

Need to set the correct path to create the PR from..

It can be derived from the package_name

to avoid confusing it with a valid package_name where relative_package_dir could
be derived.

Fix clippy warning about same postfix "Problem" in struct names on
NixpkgsProblem enum

Automated update

It's @infinisil and @philiptaron

Switch automated updates to weekly

To remove duplicate `.into()` calls

Include clippy lints for tests

This pull request does not change the single-line vs multi-line style or any of the error messages. The goal here is to reduce code duplication.

A lot of the NixpkgsProblem enum variants had common fields more or less due to the context of where the error originated.

I grouped these similar problems into structs which contains the common fields and a kind enum to differentiate between the different types of problems.

Work related to: NixOS#2

- Updating autocfg v1.1.0 -> v1.2.0
- Updating clap v4.5.3 -> v4.5.4
- Updating clap_derive v4.5.3 -> v4.5.4
- Updating itoa v1.0.10 -> v1.0.11
- Updating memchr v2.7.1 -> v2.7.2
- Updating memoffset v0.9.0 -> v0.9.1
- Updating regex-syntax v0.8.2 -> v0.8.3
- Updating serde_json v1.0.114 -> v1.0.115
- Updating syn v2.0.55 -> v2.0.57

No way currently to see inside `npins` for those updates.

…-paths

Consistent relative paths to expression file

Automated update

For future extra allowances in tests

The command isn't very reproducible anyways, since it depends on certain files existing.
Printing a reproducible command is up to callers like Nixpkgs:
https://github.com/NixOS/nixpkgs/blob/4cba8b53da471aea2ab2b0c1f30a81e7c451f4b6/.github/workflows/check-by-name.yml#L115

By turning Nix eval errors into a NixpkgsProblem.

With the convention of NixpkgsProblem representing problems caused by Nixpkgs, and
I/O-Result errors caused by bugs in the program, it should've really been of the first variant all
along.

Some workarounds are required to make the testing of this feasible

Second release out of this repository. I'm excited!

…ixOS#37)

Now using `nix-build -A <tab>` is much smaller

Makes the diff smaller for a future non-trivial update script

Using the dependabot CLI

Many different script updates along the way as well.

lazyDerivation limits which attributes are exposed, and version is not currently one of them,
so we need to explicitly expose it.

This fixes this CD failure:

https://github.com/NixOS/nixpkgs-check-by-name/actions/runs/8637321506/job/23679230914

With the advice from dependabot/cli#301 (comment)

dependabot/cli#301 (comment)

Automated update

Previously the closing </details> tag was not printed if there was nothing to update, which leads to
wrong nesting

Fix output markdown of update-github-actions

Automated release