Is this normal binary logging behaviour - maintaining one ever growing file despite expire_logs_days?
If the file hasn't exceeded max_binlog_size or if a log flushing event hasn't occurred then it won't start a new file. expire_logs_days only removes non-active binary logs (i.e. files other than the one that shows up under a "show master status;").