Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Tags: armbian/community

Tags

26.2.0-trunk.464

Toggle 26.2.0-trunk.464's commit message
fix: use published_at instead of created_at for release sorting

When multiple releases are created in bulk, they have identical created_at
timestamps, causing unstable sort order that may delete newer releases
instead of older ones. Use published_at which reflects the actual release
publication order.

26.2.0-trunk.458

Toggle 26.2.0-trunk.458's commit message
fix: use published_at instead of created_at for release sorting

When multiple releases are created in bulk, they have identical created_at
timestamps, causing unstable sort order that may delete newer releases
instead of older ones. Use published_at which reflects the actual release
publication order.

26.2.0-trunk.449

Toggle 26.2.0-trunk.449's commit message
fix: use published_at instead of created_at for release sorting

When multiple releases are created in bulk, they have identical created_at
timestamps, causing unstable sort order that may delete newer releases
instead of older ones. Use published_at which reflects the actual release
publication order.

26.2.0-trunk.448

Toggle 26.2.0-trunk.448's commit message
fix: use published_at instead of created_at for release sorting

When multiple releases are created in bulk, they have identical created_at
timestamps, causing unstable sort order that may delete newer releases
instead of older ones. Use published_at which reflects the actual release
publication order.

26.2.0-trunk.447

Toggle 26.2.0-trunk.447's commit message
fix: use published_at instead of created_at for release sorting

When multiple releases are created in bulk, they have identical created_at
timestamps, causing unstable sort order that may delete newer releases
instead of older ones. Use published_at which reflects the actual release
publication order.

26.2.0-trunk.321

Toggle 26.2.0-trunk.321's commit message
fix: use published_at instead of created_at for release sorting

When multiple releases are created in bulk, they have identical created_at
timestamps, causing unstable sort order that may delete newer releases
instead of older ones. Use published_at which reflects the actual release
publication order.

26.2.0-trunk.319

Toggle 26.2.0-trunk.319's commit message
fix: use published_at instead of created_at for release sorting

When multiple releases are created in bulk, they have identical created_at
timestamps, causing unstable sort order that may delete newer releases
instead of older ones. Use published_at which reflects the actual release
publication order.

25.11.0-trunk.544

Toggle 25.11.0-trunk.544's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Update logo in README with a smaller version

25.11.0-trunk.540

Toggle 25.11.0-trunk.540's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Update logo in README with a smaller version

25.11.0-trunk.523

Toggle 25.11.0-trunk.523's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Update logo in README with a smaller version