Unsigned causes Postgres error when used with Integer or BigInteger

[faytekin]

Laravel Version: 8.48.1
PHP Version: 8.0.1

Migrations that mix integer() (or bigInteger()) with unsigned() no longer migrate, but throw an error with Postgres error.

Schema::create('broken_primary', function (Blueprint $table) {
    $table->integer('broken_id')->unsigned()->primary();
    $table->timestamps();
});

[studnitz]

This was fixed with laravel/framework#37826, so no need for this anymore.