Just upgraded from 4.7.6 to 4.8.2 and it solved some issues I had with the selects. However now when I programmatically set the value of the select it doesn't update the selects input element to display the selected item. I used your material select and jquery to set the selected option after it is initialized.

{
<select id="my_select_id" class="mdb-select md-form mb-0 pb-0" searchable="Search here..."></select>
$('#my_select_id').val(my_value).trigger('change');
}

Using the above line will change the value of the select and when opened it shows the option highlighted, however the input field never updates the text to reflect it. I played around and found that if you add the multiple attribute it will work as intended. After more digging I found that when multiple is added, calling change will fire renderMaterialSelect in mdb.js (18119). In renderMaterialSelect the problem comes from the if statement on line 18141.

if (this.isMultiple) {
    this.$nativeSelect.find('option:selected:not(:disabled)').each(function (i, element)  {
        var index = element.index;

        _this._toggleSelectedValue(index);

       _this.$materialOptionsList.find('li:not(.optgroup):not(.select-toggle-all)').eq(index).find(':checkbox').prop('checked', true);
   });
} else {
    var index = this.$nativeSelect.find('option:selected').index();
    this.$materialOptionsList.find('li').eq(index).addClass('active');
}

For a quick fix I just copied what was in the isMultiple into the else and it is working again.

The DatePicker code should be an easy fix. The problem is when you set the maximum date on the DatePicker to the current day, for example:

$('#issue_date').pickadate({
    min: new Date(1920,1,1),
    max: new Date(),
    selectYears: 100,
    format: 'mmmm d, yyyy',
    formatSubmit: 'yyyy/mm/d',
    hiddenName: true
});

The DatePicker works perfectly except for when you attempt to click next month when the next month doesn't exist. When you click next it will reload the entire webpage, not sure if it was also happening in 4.7.6 but it is definitely happening in 4.8.2. I believe the issue is coming from line 20386 in mdb.js.

DatePicker.prototype.navigate = function (type, value, options) {}

If you have a quick temporary fix I would much appreciate it.