pxpm
commented
1 month ago Hello @vernar
usually 402 means payment required. So it's possible that your license expired in backpack/pro:2.2.4, so you have access to that version and all prior versions to that one but not newer versions.
You can check what versions and until when you have package updates by login into your account at https://backpackforlaravel.com/user/tokens .
Let me know if I can help you with something else 👍
Cheers
jcastroa87
Bug report
What I did
composer upgradecommandWhat I expected to happen
Downloading backpack/pro (2.2.8)
and installed successfully
What happened
composer ask for token credentials to access private repos
What I've already tried to fix it
if I set version "backpack/pro": "2.2.4" clear(or not) composer cache, remove (or not) vendor folder, or run composer upgrade on other device, all installed correct without git access
Is it a bug in the latest version of Backpack?
It were reproduced on 2.2.5, 2.2.6, 2.2.7, 2.2.8 versions
Backpack, Laravel, PHP, DB version
PHP VERSION:
8.2.21
PHP EXTENSIONS:
Core, date, libxml, openssl, pcre, zlib, filter, hash, json, pcntl, random, Reflection, SPL, session, standard, sodium, mysqlnd, PDO, xml, bcmath, calendar, ctype, curl, dom, mbstring, FFI, fileinfo, ftp, gd, gettext, iconv, imagick, intl, exif, mysqli, pdo_mysql, Phar, posix, readline, shmop, SimpleXML, soap, sockets, sysvmsg, sysvsem, sysvshm, tokenizer, xmlreader, xmlwriter, xsl, zip, Zend OPcache, xdebug
LARAVEL VERSION:
10.48.16.0
BACKPACK PACKAGE VERSIONS:
backpack/basset: 1.3.5 backpack/crud: 6.7.18 backpack/generators: v4.0.5 backpack/logmanager: v5.0.2 backpack/permissionmanager: 7.2.1 backpack/pro: 2.2.4 backpack/settings: 3.1.1 backpack/theme-coreuiv2: 1.2.5 backpack/theme-coreuiv4: 1.1.2