Trouble with --sheet-columns in batch mode

I have 236 .png of 128x128 size each. I’d like to put them into a spritesheet with 10 columns sprites in each. Sounds simple enough, but… (Steam version, Linux)

% aseprite -b *.png --sheet-columns 10 --sheet-type columns --sheet ../spritesheet.png
 "meta": {
  "app": "http://www.aseprite.org/",
  "version": "1.3.17.2-x64",
  "image": "spritesheet.png",
  "format": "RGBA8888",
  "size": { "w": 30208, "h": 128 },
  "scale": "1"
 }

From width and height you can clearly see that it is a single row with 236 columns, which is not what I wanted. Thinking that maybe I understood something wrong from the documentation, I tried a few more commands:

% aseprite -b *.png --sheet-columns 10 --sheet-type rows --sheet ../spritesheet.png
"size": { "w": 128, "h": 30208 },

% aseprite -b *.png --sheet-columns 10 --sheet-type horizontal --sheet ../spritesheet.png
"size": { "w": 30208, "h": 128 },

% aseprite -b *.png --sheet-columns 10 --sheet-type vertical --sheet ../spritesheet.png
"size": { "w": 128, "h": 30208 },

% aseprite -b *.png --sheet-columns 10 --sheet-type packed --sheet ../spritesheet.png
"size": { "w": 2048, "h": 1920 },

The packed sheet type produced 16 columns as expected from its packing algorithm - which is neat, but not what I wanted. All other types produced a single line of sprites as evidenced by the dimensions.

It seems that every possible sheet type ignored the --sheet-columns argument. Am I doing something wrong, or is it a bug as I suspect?

PS I managed to solve my use case with --sheet-width, which actually worked! So I’m not actually looking for a solution to my problem, just reporting a possible bug. The final command ended up being

% aseprite -b *.png --inner-padding 1 --sheet-width 1300 --sheet-type rows --sheet ../spritesheet.png

I skipped the padding in my previous examples for simplification.