Your (re)validation efforts should be risk based (and risk justified). Evaluate (and document) the change in terms of risk (to product and to process) then make an argument (document) for what validation is required. Since you indicate new features, you probably can’t justify doing no validation. A good approach is to test updated features, new features, and features that are ‘touched’ by those features (regression testing). Did I mention you should document all this?