| Commit message (Collapse) | Author | Age |
|\
| |
| | |
CODEOWNERS: add myself to nixos/no-x-libs module
|
| | |
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bumps [peter-evans/create-or-update-comment](https://github.com/peter-evans/create-or-update-comment) from 3.1.0 to 4.0.0.
- [Release notes](https://github.com/peter-evans/create-or-update-comment/releases)
- [Commits](https://github.com/peter-evans/create-or-update-comment/compare/23ff15729ef2fc348714a3bb66d2f655ca9066f2...71345be0265236311c031f5c7866368bd1eff043)
---
updated-dependencies:
- dependency-name: peter-evans/create-or-update-comment
dependency-type: direct:production
update-type: version-update:semver-major
...
Signed-off-by: dependabot[bot] <support@github.com>
|
|\
| |
| | |
workflows/check-by-name: Trigger on base branch changes
|
| |
| |
| |
| |
| | |
Not doing this can cause CI to report a misleading result when it wasn't
retriggered after a base branch change.
|
| |
| |
| |
| |
| | |
I enjoyed doing major overhaul work on these parts of the codebase,
but I can't continue maintaining them.
|
|\ \
| | |
| | | |
Revert "CODEOWNERS: Watch the maintainers lists"
|
| |/ |
|
|/ |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bumps [cachix/cachix-action](https://github.com/cachix/cachix-action) from 13 to 14.
- [Release notes](https://github.com/cachix/cachix-action/releases)
- [Commits](https://github.com/cachix/cachix-action/compare/6a2e08b5ebf7a9f285ff57b1870a4262b06e0bee...18cf96c7c98e048e10a83abd92116114cd8504be)
---
updated-dependencies:
- dependency-name: cachix/cachix-action
dependency-type: direct:production
update-type: version-update:semver-major
...
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bumps [cachix/install-nix-action](https://github.com/cachix/install-nix-action) from 24 to 25.
- [Release notes](https://github.com/cachix/install-nix-action/releases)
- [Commits](https://github.com/cachix/install-nix-action/compare/7ac1ec25491415c381d9b62f0657c7a028df52a7...6004951b182f8860210c8d6f0d808ec5b1a33d28)
---
updated-dependencies:
- dependency-name: cachix/install-nix-action
dependency-type: direct:production
update-type: version-update:semver-major
...
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
|
|
|
|
|
| |
Now that the tooling is pinned instead of being fetched indirectly from
the channel, the docs need some updating
|
|
|
|
| |
Wasn't detected in https://github.com/NixOS/nixpkgs/pull/281407
|
|\
| |
| | |
check-by-name/run-local.sh: Make it usable for non-CI platforms
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Since https://github.com/NixOS/nixpkgs/pull/281374, the
nixpkgs-check-by-name tooling is pinned to a specific /nix/store path to
avoid having to evaluate Nixpkgs in CI.
The same path is used for local runs, but that doesn't actually work
when you're trying to run it on a platform different from CI.
This commit makes it work by being clearer about platforms and making
local runs check out the correct Nixpkgs to evaluate the tool from.
|
|/ |
|
|\
| |
| | |
workflows/check-by-name: Pin nixpkgs-check-by-name tool
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Before this, the tool for CI would update when nixos-unstable updated,
which is kind of terrible because you don't know when it happens, and it
might break master.
In fact, the tooling _right now_ has a serious bug and shouldn't be used!
This PR addresses this by _pinning_ the tooling in Nixpkgs itself.
Updating the tooling now requires two PRs:
- The first PR to update the tooling source
- (wait for Hydra to build and publish it in nixos-unstable)
- The second PR to update the pinned tooling
In turn you know exactly when the changes are going to take effect.
This change however has additional benefits:
- It makes CI more reproducible, because it doesn't depend on the state
of nixos-unstable anymore
- Updates to the tooling can be tested with the workflow itself,
because PRs that update the pinned tool will be tested on the updated
version
- CI gets a sizable speed boost, because there's no need to download and
evaluate a channel anymore
- It makes it more realistic to move the source of the tool into a
separate repository
- It removes the brittle branch-specific logic that was previously
needed to ensure that release branches use their own version of the
tooling.
|
| |
| |
| |
| | |
The nix_path definition was missing :/
|
|\ \
| |/
|/| |
ci: Check if all nix files are parseable
|
| | |
|
| | |
|
|/
|
|
|
|
|
|
|
| |
Given the prior attempts to encourage Nix package bumps to be more stable, we failed, failed and failed again.
Today again, we shipped a broken Nix (2.19.2) without sufficient testing to unstable-small and it broke some users.
As announced in the past, I am taking ownership of the package manager bumps and modifications
as seemingly no one is interested to do it inside of Nixpkgs.
|
|\
| |
| | |
chromium: drop inactive maintainers, CODEOWNERS: init chromium
|
| | |
|
| | |
|
| | |
|
|\ \
| | |
| | | |
`pkgs/by-name`: Enable gradual migration checks and add `run-local.sh`
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
This enables the ratchet checks for pkgs/by-name, allowing gradual
migrations!
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Now that we have a script to run the check locally,
there's no real need to output the information to reproduce anymore,
which allows cleaning up the CI workflow.
Furthermore, this prepares the CI workflow to be passed `--base`, as
introduced recently.
|
| | | |
|
| | |
| | |
| | |
| | | |
This part of the CI can also be reproduced locally
|
|\ \ \
| | | |
| | | | |
maintainers: Add new script to check URLs in `doc/manpage-urls.json`
|
| | | | |
|
| |_|/
|/| | |
|
| |/
|/| |
|
|/ |
|
|
|
|
|
|
| |
terraform
terraform is unfree and can't be built on ofborg
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bumps [cachix/cachix-action](https://github.com/cachix/cachix-action) from 12 to 13.
- [Release notes](https://github.com/cachix/cachix-action/releases)
- [Commits](https://github.com/cachix/cachix-action/compare/6a9a34cdd93d0ae4b4b59fd678660efb08109f2f...6a2e08b5ebf7a9f285ff57b1870a4262b06e0bee)
---
updated-dependencies:
- dependency-name: cachix/cachix-action
dependency-type: direct:production
update-type: version-update:semver-major
...
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bumps [cachix/install-nix-action](https://github.com/cachix/install-nix-action) from 23 to 24.
- [Release notes](https://github.com/cachix/install-nix-action/releases)
- [Commits](https://github.com/cachix/install-nix-action/compare/6a9a9e84a173d90b3ffb42c5ddaf9ea033fad011...7ac1ec25491415c381d9b62f0657c7a028df52a7)
---
updated-dependencies:
- dependency-name: cachix/install-nix-action
dependency-type: direct:production
update-type: version-update:semver-major
...
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
|
| |
|
|\
| |
| | |
.github: fix "Priorities" heading level
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Where this was a markdown heading, it sometimes had the wrong weight
so it appeared as if it was a subheading of the previous section, and
some people feel the word "Priorities" creates misleading
expectations.
Link: https://github.com/NixOS/nixpkgs/pull/203969/files#r1037761779
|
| |
| |
| |
| |
| | |
Currently there is an eval fix on master and waiting five hours for it
to propagate into staging-next and staging is annoyingly long.
|
|\ \
| | |
| | | |
workflows/check-by-name: Limited and exponential retries
|
| | |
| | |
| | |
| | | |
Co-Authored-By: Cole Helbling <cole.e.helbling@outlook.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We've had a recent PR CI mass failure event, ultimately caused by the
mergeability check GitHub API not returning a result.
But due to the `pkgs/by-name` check workflow not backing off
appropriately between retries, it pummeled the API, resulting in
exceeding the API rate limit:
https://github.com/NixOS/nixpkgs/actions/runs/7010089143/job/19069845070
This commit fixes that for the future by implementing a retry strategy limited to three
retries, with exponential backoff
|