acli: 1.3.20-stable -> 1.3.21-stable

[r-ryantm]

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.

meta.description for acli is: Atlassian Command Line Interface

meta.homepage for acli is: https://developer.atlassian.com/cloud/acli/guides/introduction

Updates performed

• Ran passthru.UpdateScript

To inspect upstream changes

Impact

Checks done

---

• built on NixOS
• The tests defined in passthru.tests, if any, passed
• found 1.3.21-stable in filename of file in /nix/store/day4sqgqldnv1nbx051iznm0159jsy12-acli-1.3.21-stable

---

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

acli

Instructions to test this update (click to expand)

---

Either download from the cache:

nix-store -r /nix/store/day4sqgqldnv1nbx051iznm0159jsy12-acli-1.3.21-stable \
  --option binary-caches 'https://cache.nixos.org/ https://nixpkgs-update-cache.nix-community.org/' \
  --option trusted-public-keys '
  nixpkgs-update-cache.nix-community.org-1:U8d6wiQecHUPJFSqHN9GSSmNkmdiFW7GW7WNAnHW0SM=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The nixpkgs-update cache is only trusted for this store-path realization.)
For the cached download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.

Or, build yourself:

nix-build -A acli https://github.com/r-ryantm/nixpkgs/archive/38a040264ef1833811576b104485c42175b69dd3.tar.gz

Or:

nix build github:r-ryantm/nixpkgs/38a040264ef1833811576b104485c42175b69dd3#acli

After you've downloaded or built it, look at the files and if there are any, run the binaries:

ls -la /nix/store/day4sqgqldnv1nbx051iznm0159jsy12-acli-1.3.21-stable
ls -la /nix/store/day4sqgqldnv1nbx051iznm0159jsy12-acli-1.3.21-stable/bin

---

Pre-merge build results

We have automatically built all packages that will get rebuilt due to
this change.

This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review --extra-nixpkgs-config '{ allowBroken = false; }'
Commit: 38a040264ef1833811576b104485c42175b69dd3

---

x86_64-linux

✅ 1 package built:

• acli

---

Maintainer pings

cc @Moraxyc for testing.

Tip

As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

[Moraxyc]

LGTM

[Moraxyc]

@NixOS/nixpkgs-merge-bot merge

[nixpkgs-ci]

@Moraxyc wants to merge this PR.

Requirements to merge this PR with @NixOS/nixpkgs-merge-bot merge:

• ✅ PR targets a development branch.
• ✅ PR touches only files of packages in pkgs/by-name/.
• ✅ PR is at least one of:
  • ⬜ Approved by a committer.
  • ⬜ Backported via label.
  • ⬜ Opened by a committer.
  • ✅ Opened by @r-ryantm.
• ✅ PR is not a draft
• ✅ PR is not blocked by a "changes requested" review from a committer.
• ✅ Moraxyc is a member of @NixOS/nixpkgs-maintainers.
• ✅ Moraxyc is a maintainer of all touched packages on the master branch.

✔️ Queued for merge (#306934)

[nixpkgs-ci]

Backport failed for release-26.05, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin release-26.05
git worktree add -d .worktree/backport-537079-to-release-26.05 origin/release-26.05
cd .worktree/backport-537079-to-release-26.05
git switch --create backport-537079-to-release-26.05
git cherry-pick -x 38a040264ef1833811576b104485c42175b69dd3